More keycommands trouble -Sound Forge - PC - MAGIX Community Forums Archive

Subject:More keycommands trouble Posted by: Sound Samurai Date:6/10/2005 2:12:53 AM Hello again! I am having a lot of trouble assigning and understanding what/how keycommands really work. For example the numeric top row (1,2,3,4,5) is not possible to assign to scripting, and even if the default commands (Cell operation) are REMOVED, they still fire instead of the new scripts. Is it probably safe to assume that it is really buggy in this 8.0a, and I should wait with building a workspace for an update? Kind regards The Wrong Button Pressing Samurai
Subject:RE: More keycommands trouble Reply by: _TJ Date:6/10/2005 11:07:57 PM What context are you tring to bind the number keys into? Global? Data Window? tj
Subject:RE: More keycommands trouble Reply by: Sound Samurai Date:6/11/2005 3:28:50 AM Data window. I know about the global limit.
Subject:RE: More keycommands trouble Reply by: _TJ Date:6/14/2005 9:35:29 PM You're bumping up against the same bug that I mentioned before. Script commands bound in the Data Window context don't work. The command routing just isn't there. If you remove the existing bindings for the number keys, you end up hitting a feature. It occurred to us that if the user removed ALL of his key bindings, then the app wouldn't work at all. So we have fallback code. If a key falls through without getting handled by a binding, and it's one of the basic navigation keys. (left arrow, page up, home, end, etc) then we go ahead and process it as if you still had the default key bindings in place. since the default behavior of the number keys in the Data Window context is navigation, they go ahead and do their default action even if you remove the bindings. And it just so happens, that if you bind a number key to a script, the code behaves at if you hadn't bound it to anything at all. (the routing bug that I mentioned before). tj

Subject:More keycommands trouble

Date:6/10/2005 2:12:53 AM

Hello again!

I am having a lot of trouble assigning and understanding what/how keycommands really work.

For example the numeric top row (1,2,3,4,5) is not possible to assign to scripting, and even if the default commands (Cell operation) are REMOVED, they still fire instead of the new scripts.

Is it probably safe to assume that it is really buggy in this 8.0a, and I should wait with building a workspace for an update?

Kind regards
The Wrong Button Pressing Samurai

Subject:RE: More keycommands trouble

Reply by: _TJ

Date:6/10/2005 11:07:57 PM

What context are you tring to bind the number keys into? Global? Data Window?

tj

Subject:RE: More keycommands trouble

Reply by: Sound Samurai

Date:6/11/2005 3:28:50 AM

Data window. I know about the global limit.

Subject:RE: More keycommands trouble

Reply by: _TJ

Date:6/14/2005 9:35:29 PM

You're bumping up against the same bug that I mentioned before. Script commands bound in the Data Window context don't work. The command routing just isn't there.

If you remove the existing bindings for the number keys, you end up hitting a feature. It occurred to us that if the user removed ALL of his key bindings, then the app wouldn't work at all.

So we have fallback code. If a key falls through without getting handled by a binding, and it's one of the basic navigation keys. (left arrow, page up, home, end, etc) then we go ahead and process it as if you still had the default key bindings in place.

since the default behavior of the number keys in the Data Window context is navigation, they go ahead and do their default action even if you remove the bindings.

And it just so happens, that if you bind a number key to a script, the code behaves at if you hadn't bound it to anything at all. (the routing bug that I mentioned before).

tj