![]() ![]() I also very much like the idea of re-implementing it in Canvas, as I had to make some design decisions purely on the basis of what was possible through the XML GUI code. I'm very happy if someone wants to expand the Joystick GUI to include advanced features such as modifier keys, and support for arbritary Nasal snippets. Is there are a particular reason for not using the repeatable flag, or is it purely for people who have mode-switches and might have another (non-repeatable) function assigned to the button? On a different note, I'm interested to see what bindings people are using on joysticks, to check that the set of button bindings that are supported in the configuration dialog are sufficient.Īt present the dialog supports trim settings, but sets the button to be repeatable. IMO anyone who knows enough to write Nasal joystick bindings will have enough knowledge to edit the joystick XML files directly and use the Nasal Console. The joystick configuration dialog is really targeted at new users who don't have any XML or Nasal experience. Partly this was due to time constraints, but it was also because I didn't think there was a use-case for it. Stuart being the developer and maintainer of the latest Joystick GUI, here's his feedback:Īdding the ability to write Nasal for a given button was something I considered, but didn't implement. At the end of the day, it's all XML, Nasal and the property tree, and some fgcommands to reinit stuff - so if people still think, that'd be useful, please speak-up and share your feature requests / ideas here.Īlso see User:Philosopher/Advanced Input Programming. UI-wise, we could simply reuse/integrate the existing Nasal console, so that bindings can be dynamically added and edited. And it would indeed not require many customizations to allow bindings to become fully runtime-configurable, including Nasal bindings and a standard library of general-purpose Nasal/JS APIs. We once talked about integrating the various Nasal capabilities added by Macnab and Philosopher right into Stuart's new JS config dialog - back then, Stuart & Zakalawe actually seemed supportive of the idea. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |