07-24-2015, 06:21 PM
07-25-2015, 07:13 AM
hi! ptoing
Welcome to Wings3D forum!!
Thank for your report.
I tried too,and could not bind a hotkey to "Lift-command".
It is a wonder why this happens only Lift command...
This issue is reproducible.
my enviroment is...
OSX 10.10.4
Wings3D v1.5.3
Welcome to Wings3D forum!!
Thank for your report.
I tried too,and could not bind a hotkey to "Lift-command".
It is a wonder why this happens only Lift command...
This issue is reproducible.
my enviroment is...
OSX 10.10.4
Wings3D v1.5.3
07-26-2015, 01:50 PM
I am on 64bit Win7 SP1.
Also 1.5.3
Also 1.5.3
07-26-2015, 02:28 PM
I would guess it is because of the preceding and appended dots "."
These mean it is a special kind of menu. But since they are used all over ... I'd say yes ... you should call this a BUG. If you drill down maybe you can attach to a menu item that comes later ?
These mean it is a special kind of menu. But since they are used all over ... I'd say yes ... you should call this a BUG. If you drill down maybe you can attach to a menu item that comes later ?
07-26-2015, 05:40 PM
(07-26-2015, 02:28 PM)ggaliens Wrote: [ -> ]I would guess it is because of the preceding and appended dots "."No, that is not because of them. We can hotkey other commands like ".Move.", ".Scale." and ".Put On."
I checked it and it's related to the way the hotkey routine checks the menu info. Lift command uses a unexpected kind of value in the menu tuple.
I'm still not sure if my fix will cause any side effect.
07-27-2015, 02:19 PM
Here is the fix. It's for Wings3D 1.5.3!
The file for replacement can be download here:wings_menu.beam (usually in c:\Program Files (x86)\wings3d_1.5.3\lib\wings-1.5.3\ebin)
Please let me know if you get any problem binding hotkeys to other commands.
The file for replacement can be download here:wings_menu.beam (usually in c:\Program Files (x86)\wings3d_1.5.3\lib\wings-1.5.3\ebin)
Please let me know if you get any problem binding hotkeys to other commands.
07-27-2015, 07:12 PM
Cool, that works Thanks a bunch.