RE: Wings-2.0.4
I'm looking to speed up the testing of the newest connect cuts. I've got this in my prefs file ...
{{bindkey,99},{vertex,connect_cuts},user}.
{{bindkey,104},{edge,{hardness,hard}},user}.
But for whatever reason little c does not map to connect_cuts. I think I needed to recompile the 2.0.3 version of code to put connect_cuts as first (LMB) rather than CTRL+RMB. But to me ... that does not make a whole lot of sense since the keypress should just find the proper command tuple once it is in the prefs file. Why would it care a all about mouse buttons after it has been assigned ?
My asserstion is that once the bindkey has happened in the prefs file ... the menu system should be a moot point. Hotkey should bypass menus altogether.
So far connect cuts additional refinements seem OK ... but it takes a very large sample space to test this new command. I'll do more testing. Thanks for continuing work on this to make it better.
I'm looking to speed up the testing of the newest connect cuts. I've got this in my prefs file ...
{{bindkey,99},{vertex,connect_cuts},user}.
{{bindkey,104},{edge,{hardness,hard}},user}.
But for whatever reason little c does not map to connect_cuts. I think I needed to recompile the 2.0.3 version of code to put connect_cuts as first (LMB) rather than CTRL+RMB. But to me ... that does not make a whole lot of sense since the keypress should just find the proper command tuple once it is in the prefs file. Why would it care a all about mouse buttons after it has been assigned ?
My asserstion is that once the bindkey has happened in the prefs file ... the menu system should be a moot point. Hotkey should bypass menus altogether.
So far connect cuts additional refinements seem OK ... but it takes a very large sample space to test this new command. I'll do more testing. Thanks for continuing work on this to make it better.