01-13-2009 07:52 PM
01-14-2009 11:50 AM - edited 01-14-2009 11:54 AM
Hi PJM,
I think I finally understand this post as it is different from the complaint that you linked to. Just to confirm, the vi that is non frontmost will not register an event waved over the frontmost vi that also covers part of the vi that is behind it. This does not seem at all a bug to me, even though frontmost does not mean that the front most vi takes priority, it however it does mean that the vi take priority of that specific space on the front panel and therefore the vi behind it should not register anything because its not looking at that part of the front panel. The non front most vi does register the mouse over event for the parts that are not overlapping and thats what it appears that was the problem you linked to was complaining about, with the vi registering the event regardless if it was foremost or not.
It almost appears that you are concerned about both sides of the spectrum here, with the vi registering the event both regardless of foremost and also saying that it does not register if non front most. Am I correct about this?
01-14-2009 12:05 PM - edited 01-14-2009 12:13 PM
Andrew,
I am the person who posted on LAVA.
I think there is a misunderstanding in here. The fact that one VI is partially behind another one has nothing to do with the bug. The issue is as follow:
I hope this clarify the issue.
PJM
01-14-2009 01:50 PM
Hi PJM,
Thanks for clarifying the issue. I have gone ahead and tested it on one of our mac's and I can verify what you say. I will make a bug report for it. Thanks for bringing this to our attention.
01-14-2009 03:58 PM - edited 01-14-2009 03:58 PM
01-15-2009 02:02 PM
01-15-2009 02:45 PM
01-15-2009 04:26 PM