Notifications
Clear all

[Closed] Edit Spline and Keyboard Shortcut Issue

Hi,

I’m wondering whether anyone is having a problem with keyboard shortcuts not working as they should with Edit Splines when switching to subobject levels greater than 1?

The following is a basic version of the script

max modify mode
  if subobjectlevel == 0 then 
  	subobjectlevel = 2
  else subobjectlevel = 0

Scenario:

  • Spline object with Edit Spline modifier
  • Assign script to a keyboard shortcut
  • Select the spline and run the script through the keyboard shortcut (Should switch to segment subobject level)
  • Run the script through the keyboard shortcut again (Nothing happens. It should switch out of subobject level. In fact, ALL keyboard shortcuts do not respond).

Notes:

  • Problem doesn’t occur on Editable Splines or Lines. Only splines with the Edit Spline modifier
  • Problem doesn’t occur for mesh objects.
  • Problem doesn’t occur if I run the script manually
  • Problem doesn’t occur if I click on the viewport after running the script the first time.
  • Problem doesn’t occur if the code switches to subobject level 1 (vertex)

If anyone could try this out to see if they are experiencing the same problem, that would be greatly appreciated.

Thanks

3 Replies

No one has come across this problem at all?

This is some sort of very deep focus loss problem.
It does not occur with SO Level 1 (vertex) but does with segment and spline (2 and 3).
Pressing Tab and then the shortcut fixes it, so it looks like Max completely loses focus.
Right-clicking a viewport to activate a quad menu or clicking the Selection rollout brings the focus back and the shortcut starts working again.
No other action after the switch of SubObjectLevel appears to restore the focus (I could be wrong, but I even tried sending Win32API messages to Max to set its focus, but without success).

Good luck with getting this fixed. I suspect it has been there since the beginning or at least since Max 4 when the new keyboard shortcuts system was introduced.

Firstly, thanks so much Bobo for taking the time to read my private message and respond to my post! Your knowledge is staggering and you are always willing to share and help others in need.

Secondly thanks for confirming to me that it is indeed a bug in Max and the workarounds to overcome the problem.

Cheers!