Strange behaviour from Grasshopper after expiringSolution of Object

Replies to This Discussion

Permalink Reply by David Rutten on April 24, 2017 at 8:15am

If you're changing more than one object, I wouldn't use ExpireSolution(true), but instead ExpireSolution(false). Then, only after you have expired all the objects in question, should you trigger a new solution on the document. Or, if you know exactly how many objects you are expiring, you can call ExpireSolution(true) on the last one.

As for the problem you're describing, it sounds like some object is eating all the mouse events because it was at some point activated and never deactivated itself. How is your code triggered? Via a menu? By clicking on some custom object? By clicking on a Button or Toggle?

Permalink Reply by Anton Szilasi on April 24, 2017 at 10:13am

David,

Thank you for your reply!

The code is trigged by a modifed form of the Grasshopper.Kernel.Special.GH_ButtonObject

The code is trigged by the line: ownerOfThisAttribute.createDesignSpace();

public override GH_ObjectResponse RespondToMouseDoubleClick(GH_Canvas sender, GH_CanvasMouseEvent e)
{
if (e.Button != MouseButtons.Left || sender.Viewport.Zoom < 0.5f || !this.m_button.Contains(e.CanvasLocation))
{
return base.RespondToMouseDown(sender, e);
}
this.Owner.ButtonDown = true;

this.Owner.ExpireSolution(true);

ownerOfThisAttribute.createDesignSpace();

return GH_ObjectResponse.Capture;

}

public override GH_ObjectResponse RespondToMouseUp(GH_Canvas sender, GH_CanvasMouseEvent e)
{
if (!this.Owner.ButtonDown)
{
return base.RespondToMouseUp(sender, e);
}
this.Owner.ButtonDown = false;

this.Owner.ExpireSolution(true);

return GH_ObjectResponse.Release;
}

Permalink Reply by David Rutten on April 24, 2017 at 10:25am

Yeah the button has problems. Try returning

return GH_ObjectResponse.Handled;

instead of Capture from the double click handler.

Permalink Reply by Anton Szilasi on April 24, 2017 at 10:47am

Thanks David that worked!