Replies Created


    bug ROI number

    HI Stephane,

    does this work for all timepoints?

    I have the following script (I guess from you before  you made it as a protocol) – it works, but only at the first time point.

    Any way to make it work at all timepoints ? cheers


    // Click on the button
    // to edit in a frame.

    bounds = input0.getBounds2D()
    output0 = []
    ind = 0;

    for(i = 0; i < input1.length; i++)
    r = input1[i]

    rbounds = r.getBounds5D().toRectangle2D();
    if ((rbounds.getMinX() == bounds.getMinX()) ||
    (rbounds.getMinY() == bounds.getMinY()) ||
    (rbounds.getMaxX() == bounds.getMaxX()) ||
    (rbounds.getMaxY() == bounds.getMaxY()))

    output0[ind++] = r;

    This happened on multiple cells and with multiple parameters.. and even after fresh Icy installation


    he following error is reported only on first occurence :
    org.pushingpixels.substance.api.UiThreadingViolationException: State tracking must be done on Event Dispatch Thread
    at org.pushingpixels.substance.internal.utils.SubstanceCoreUtilities.testThreadingViolation(
    at org.pushingpixels.substance.internal.animation.StateTransitionTracker$ModelStateInfo.clear(
    at org.pushingpixels.substance.internal.animation.StateTransitionTracker.onModelStateChanged(
    at org.pushingpixels.substance.internal.animation.StateTransitionTracker$4.stateChanged(
    at javax.swing.DefaultButtonModel.fireStateChanged(
    at javax.swing.JToggleButton$ToggleButtonModel.setSelected(
    at javax.swing.AbstractButton.setSelected(
    at plugins.adufour.roi.ROIMeasures$MeasureSelector.loadParameters(
    at plugins.adufour.roi.ROIMeasures$MeasureSelector.valueChanged(
    at plugins.adufour.roi.ROIMeasures$MeasureSelector.valueChanged(
    at plugins.adufour.vars.lang.Var.fireVariableChanged(
    at plugins.adufour.vars.lang.Var.setValue(
    at plugins.adufour.vars.lang.Var.loadFromXML(
    at plugins.adufour.blocks.util.BlocksML.loadWorkFlow_V4(
    at plugins.adufour.blocks.util.BlocksML.loadWorkFlow_V4(
    at plugins.adufour.blocks.util.BlocksML.loadWorkFlow(
    at plugins.adufour.protocols.gui.ProtocolPanel.loadWorkFlow(
    at plugins.adufour.protocols.gui.MainFrame$
    at java.util.concurrent.Executors$
    at java.util.concurrent.ThreadPoolExecutor.runWorker(
    at java.util.concurrent.ThreadPoolExecutor$

    obviously you can clean up afterwards but it’d be good if it can be done before it generates additional areas..

    maybe it’s a feature request: restrict size of entering objects and min and/or max intensity