Page 1 of 1

Mouse prims reliability

Posted: Wed Sep 24, 2014 1:18 pm
by tulamide
While I was working on the sophisticated spline example, I was told that LUp and similar prims don't work correctly when the view is not on the top level.
I would like to get explicit information of what exactly doesn't work right. So I've set up a simple schematic. It has 3 views, the top one hosting another view which uses LUp. And this view also hosts another view which again makes use of LUp. I couldn't see any problems. It seems to work.

Could someone change the schematic in a way that it doesn't work correctly anymore? It would help me to understand what exactly I have to avoid.

Re: Mouse prims reliability

Posted: Wed Sep 24, 2014 9:34 pm
by billv
I think your bypasing the issue you had before
cause your design now has an inner/outer module set up.

Re: Mouse prims reliability

Posted: Wed Sep 24, 2014 10:14 pm
by tulamide
billv wrote:I think your bypasing the issue you had before
cause your design now has an inner/outer module set up.

Don't worry. This is not intended as a try to recreate an already solved issue. This is, what I can't comprehend:

KG_is_back wrote:You provide the MouseArea primitive with view and area. You may input also areas that are outside the view.
It is quite inconsistent with mouse Ldown and Lup primitives. they work correctly when you interact with the module directly, but once the module is inside other module gui, it doesn't work any more. Mouse drag is the only way to go - sample and hold the coordinates on drag start and sample and hold on release.


And having an explicit example of when this happens, would (as I said further above) help me to understand what exactly I have to avoid.

Re: Mouse prims reliability

Posted: Wed Sep 24, 2014 10:34 pm
by KG_is_back
tulamide wrote:And having an explicit example of when this happens, would (as I said further above) help me to understand what exactly I have to avoid.


Here, this schematic should be as simple as possible. The module mouse interaction seems to be clipped to its front panel rectangle once the module is a submodule of other module with gui.

Re: Mouse prims reliability

Posted: Thu Sep 25, 2014 12:16 am
by tulamide
KG_is_back wrote:Here, this schematic should be as simple as possible. The module mouse interaction seems to be clipped to its front panel rectangle once the module is a submodule of other module with gui.
Thank you very much, KG! I knew I was missing something. But thanks to your example, I now know what to take care of.

I extended your example (see attachment). Am I right, that this is a possible way of overcoming with the issue?

EDIT: Yes, billv, I hope to have understood it and thus made a green version of what you offered in ruby :mrgreen:

Re: Mouse prims reliability

Posted: Sat Sep 27, 2014 7:42 am
by tulamide
tulamide wrote:I extended your example (see attachment). Am I right, that this is a possible way of overcoming with the issue?
Could someone please confirm?