Hello I'm using ImageJ to analyse -czi and -zvi files. I'm using an automatic selection with "create selection" or "analyze particle"s. It's working well when openening/importing the files with ImageJ. But when I try to use the Bio-Format importer Plugin with the same pictures, it's not working. Not my intended ROIS are selected but the background or even nothing. With using the plugin something about the parameters of the picture changes and I don't know what it is or how to undo it. Does somebody has an idea?
One of the Solutions I realised is a Change of scale. My original files use pixels, whereas the BioFormat importer converts the scale into microns.
Analyze--> Set Scale... --> Click to remove scale or changing the scale solves one part of the problem.
For a macro following code restores the scale:
run("Set Scale...", "distance=0 known=0 pixel=1 unit=pixel");
Still somethng about the colour values changes, I can't find, create selection is still not working properly.
Related
I have a QGIS project that displays calculation results on a map. There are several vector layers, each with >100 calculated fields. The way the data should be visualised is very similar for all these layers/fields. I try to write a script that duplicates a template layer, and changes the expressions for the symbology according to the selected fieldname.
Below is a screenshot of the properties I try to access (if I were to change them using the UI).
How do I access/change the expressions of the line width and line offset of a graduated symbology in PyQGIS?
In case someone else runs into this issue.
I solved it using a workaround. I saved the style of the source layer to a qml-file, for the duplicated layers I create a temporary copy of the qml-file, do a search-and-replace on the qml-file and apply this to the new layer using
newLayer.loadNamedStyle(pathToTheTempQmlFile)
Hope this helps:
rule=layer.renderer().rootRule().children()[0]
rule.setFilterExpression('whatever')
see:
QgsRuleBasedRenderer.Rule
Recently i've been working on this repository https://github.com/xiaodongliang/forgeviewer_embed_in_powerbi_report to build a custom visual in Power BI to visualize the issues extracted from Bim track'S API.
The idea was visualizing them in associaton to the model's ROOMS.
In order to do that I worked with a NWC file, so i cuold export rooms as a geometry.
What i would like to do now is to highligt the rooms if a connected issue is selected from a table.
The problem is When i select an issue from a table, in the selection tree i can see highlighted the parent object name (ROOM) instead of the child (solid), and i think that is why i can't achieve my purpose (if not please correct me).
what i have
what i wold like to do
Does anyone know a way to do that?
If you would like to change your selection between (FIRST_OBJECT, LAST_OBJECT, LEAF_OBJECT) you can change viewer selection settings in order to test:
If you would like to achieve this programmatically :
Viewer.setSelectionMode();
could help you as well.
If I well understood, you want to highlight the child (which contain the mesh) instead of the parent.
The object highlight (isolate) is done in /forgePowerbiView/src/visual.ts with this code:
const dbIds = options.dataViews[0].table.rows.map(r =>
<number>r[0].valueOf());
console.log('dbIds: ' +dbIds)
this.forge_viewer.showAll();
this.forge_viewer.impl.setGhostingBrightness(true); //for isolate effect
this.forge_viewer.isolate(dbIds);
Take a look at this link Enumerating leaf nodes on Viewer. This will help you to get the dbIds you want to isolate.
When creating an audio plugin with Matlab's audio toolbox (either when I use the examples given by mathworks), the plugin parameters I add to the interface, always appear as sliders when loading the .dll in my DAWs (tried at Reaper and Cubase). It happens with all the kinds of mappings.
This is how I create the parameters:
properties (Constant)
PluginInterface = audioPluginInterface(...
'PluginName','Headphones Converter',...
'InputChannels',1,...
'OutputChannels',1,...
audioPluginParameter('cascos', ...
'DisplayName','Modelo de cascos', ...
'Mapping',{'enum','K44','Sennheiser','Otro'}));
end
This is how appears when testing it with audioTestBench(Convolver):
After validateAudioPlugin Convolver and generateAudioPlugin Convolver this is how appears when I load the Convolver.dll file into the reaper. Instead a dropdown, a slider is drawn:
Why is not appearing a dropdown?
Starting in R2019b, you can set the Style property of audioPluginParameter to one of hslider, vslider, rotaryknob, checkbox, vrocker, vtoggle, and dropdown.
You can also replace the default graphics of the widgets with your own custom images using the Filmstrip property (the custom graphics can be seen only in a DAW, audioTestBench does not pick this up).
See this doc page for more information on customizing the plugin UI: https://www.mathworks.com/help/audio/ug/plugin-gui-design.html
Sorry, I'm not familiar with typo3...
I have a typo3 6.2.14 installation (cannot be updated due to needed extensions) where the constants for click-enlarged images had to be adjusted.
I've cleared the cache, but nothing changed. What do I need to do?
plugin.tx_kjimagelightbox2.lightBoxMaxW = 1600 //(was 800)
plugin.tx_kjimagelightbox2.lightBoxMaxH = 1200 //(was 600)
Nothing changed. Thanks
Wow,
that's some very old TYPO3 with loads of security issues and outdatet PHP as well! Consider forking the extensions and make them work in at least 8.7.
Back to your question.
Where did you set this? Do you use files or do you just edit in the backend? You might need to gather some more information about the order your extensions are beeing loaded.
You might set your values too early and the extensions' defaults overwrite your "changes" (which have actually been declarations)
Maybae you could provide some more information of your setup.
the problem is:
the maximum sizes for images can be influenced in multiple places with multiple values.
Even if you have set the correct value, this value may be overwritten later with the smaller values.
1st:
are your original images at least big enough? normaly there is no enlargement of images.
2nd:
inspect the values in the TSOB. Are your values active in the setup?
your changes in constants may be overwritten in the setup easily and only setup is relevant for rendering.
3rd:
there are global maximum values about image rescaling in content elements. maybe these also influence your image rendering in that plugin
How to save the annotation marks in flexpaper annotation document viewer?
Thanks.
FlexPaper provides a JavaScript function called getMarkList:
marksArray = JSON.stringify($FlexPaper('documentViewer').getMarkList());
You can apply the annotations again using addMarks:
var initialMarks = JSON.parse(marksArray);
$FlexPaper('documentViewer').addMarks(initialMarks);
This works for the HTML5 version but I suspect it would also apply to the Flash and HTML versions.
Ok, so I think I've found a bug in Flexpaper that prevents this from being useful (bug is in the Flash version, have not tested HTML version). If anyone has actually got this to work on Flash, please let me know!
Basically, addMark() is performing an unnecessary coordinate transformation which makes it impossible to put back in a mark that you have extracted in the same spot (this only seems to be the case for notes, drawings don't seem to have this issue).
Here's how to reproduce:
Go to http://devaldi.com/annotations/UK_Investment_Fund.php?ro=flash,html and open Chrome JS console. Enter these commands:
>> note = $FlexPaper('documentViewer').getMarkList()[2]
Object {width: 200, pageIndex: 1, height: 180, note: "The annotations plug-in allows both highlighting a…created↵↵Notes can be resized, moved and deleted.", id: "3AFE17A3-4977-3ECA-C468-70F2C40B81E8"…}
>> // Now try to add back in the same annotation
>> $FlexPaper('documentViewer').addMark(note)
>> // Notice that on the screen the note is in the wrong spot
>> // (not the same spot as the original one). Lets check the positioning
>> added_note = $FlexPaper('documentViewer').getMarkList()[6]
>> added_note.positionX
356.718192627824
>> note.positionX
-5.945303210463702
The normalize/denormalization of positions should work fine as long as you set 'displayFormat' to 'html' as part of your object creation. The normalisation process basically adjusts X/Y/Width/Height so that the document is considered to be 1000 in height. The viewer then adjusts the positions when the annotations are being displayed if the document is different in height for flash or html. It also of course considers the proportions of the width/height of the document as part of this process.
All the best
Erik on the FlexPaper Team