Max5: [hover] bug report + feature request
While trying to make a nice rollover effect on some numberboxes with
[hover], I realized it would be cool to have a "rollout" notification
(i.e. "scriptingName 1" and "scriptingName 0").
Then I thought a possible workaround was to put a panel in the
background so when the cursor is out of the numberboxes, it’s over the
panel and it triggers the rollout effect.
This doesn’t work with panel when patcher is locked (it does work with
ubutton for example).
I guess this one can wait but I thought it was worth mentioning it…
-[hover] doesn’t outputs anything when cursor is hovering a panel in a
Steps to reproduce:
-Lock the patch.
-Hover numberboxes with your cursor.
On "hovering out" numerboxes, [hover] should output "none" on right
outlet (because cursor is now hovering [panel] and numberbox background
color should reset. It doesn’t if the patcher is locked.
MaxMSP 5.0.1, Intel MacbookPro, OS10.4.1.
----------begin_max5_patcher---------- 634.3oc4WsriaBCEcM4qvxqoQ1f4Q5x4WnRylpQUlfahq.6HryLocz7uWrAR HcH.YHMIpUBYiubs88dNG+fWm4.Sj6XJH3yfuBbbdclii0jwfScaGXNc2xLp x5FLmoTzULna02zrcZq8jUKkYxB.Zdb3ghF2Dayka0YLscPv0V+tTnU7ewL1 VLGUasxQ8O2vphKHD7T8m1TvTLglp4Rw2JXK0UdDPL8FPBBLUn5hC8hpWtlK V0pGjPhwKLwyV4Y6HNnUm3o1zRl7iOg8gsBXAM2FXvG3ZktfQyAOxJnfuPEJ vCxrzV4LWzjxdFauMalovcjPsf8R4z+NjdyyzBP4f6coA22CS9UHJNLzTEV0 H5Dnj2zQI7G.kFRPhmWJFpdBtNxQBwBTDBYrxwFbtVNhB6UNhuqjiJVlQMh6 QR5ed.bBUrB5dnteIJ1t1GajktfE3dknn++jnmFwhiFgXawc4Ve3qFJ4gQCu 0WzsQVcBPZs7YVQ2.j2YBPibwWLp5TBRefT3MBj1lmb.NJ0O6m516WUuRrJq LWbw8nRbqTpaDMQVjxJNdPBhi8Htc9V6AbjjAWn2uoXebBlDaoAeeSU.pONg bGxI3+c4j33gojazsn1PErrSg7iDzNlEPSmE5BIQ1qHQpNzJBs+5ocgkACBO 1dAy3h+7mfrSsw9wXlRtsXYC627uAfCSdJSo4B6EBa4TzQ9rlmlxDsgnbd5F YoVpNFHQ9yCJO5AYOzw2KdeKvScRsWzf0bO9OPzhCs62P7pojNZ4Wd.QimSL SJOLAfGJQ7OuDYpfKZLwD95FS3+BD9DioEW9ELWBlanPZwUMjBGCuglPHU13 sY+Fp4eKIA -----------end_max5_patcher-----------
I can confirm this on both platforms and we have logged it to be fixed.
Thanks for the report.
Can I add that it seems Hover in Max5 updates a fair bit slower than before – is there any chance of increasing the polling time? (if indeed that’s how it works?)
Great that hover is part of Max now by the way.
I suppose it’s possible that hover may update a bit more slowly than it used to, but it should be updating at the same speed that hints are displayed and the rest of the UI is updated in response to mouse movement. The old version of hover was a giant CPU hog and needed to be completely rewritten for Max 5, otherwise it would have been voted off the island and not included as a standard object.
If you need faster mouse tracking you’ll need to do it explicitly with something like mousestate.
As for the patch you supplied, the problem is that hover does not know about objects who are set to ignore mouse clicks when a patcher is locked, so it does not report anything when the mouse is over the panel. In order to work around this problem, in the next update I have taken your suggestion and added two new outlets to hover so you can find out the name of the object the mouse has just left as well as the name of the object the mouse enters. We might ultimately fix the ignore click issue — we fixed it for the hint object — but I think you’ll find the exit trigger is a better approach.
David Zicarelli wrote:
> …in the next update I taken your suggestion and added two new outlets to hover so you can find out the name of the object the mouse has just left as well as the name of the object the mouse enters. We might ultimately fix the ignore click issue — we fixed it for the hint object — but I think you’ll find the exit trigger is a better approach.
Forums > MaxMSP