"max showcursor" message fails to show cursor when triggered via the patch

    May 17 2016 | 10:13 pm
    It appears that all flavors of Max 7 on Windoze fail to show the cursor when trying to hide and then show the cursor via scripting (e.g. when a cursor enters and leaves a particular window). The problem is sporadic and is exacerbated by increased workload (e.g. more things happening in the jitter land). One solution that appears to solve this problem is to have [deferlow] placed prior to the receiving message. Clicking on the message [; max showcursor] works every time as it appears that message is handled in the appropriate interrupt. If deferlow approach for scripted cursor control is necessary, it would be great to include this in the documentation. Alternately, the enabling of the cursor may have to be handled differently and may suggest there is a potential bug. Hope this helps!

    • Nov 08 2018 | 3:26 pm
      Thanks thanks thanks, it's 3 hours I'm tring to fix this problem !!!!