21 Character Limit on Descriptions too Small; Expand to 280 for Detailed Notes
I recently bought ReWASD to supplement what I couldn't accomplish through software like AHK (namely working with controllers and gamepads). I'm learning how to use the software and I'm finding a lot of useful features as I research how to do specific tasks.
One thing I found rather disappointing was the apparently 21 character limit on descriptions for controller bindings. Coming from AHK and a self-taught scripting background, I use comments in code all the time to explain why I did what I did and make notes on how the binding may be modified to achieve different results. But 21 characters is barely enough to make a reference ID to a note document let alone actually describe a single thought process or concept. I know the software is capable of storing that information because I opened one of the .rewasd files in a text editor, made one of my comments longer, saved it, and while the text was cut off in the software window, it did allow that information to be retained.
Having more space isn't just about me making personal notes on my own binding profiles; people who are sharing configurations to the community could help each other understand how and why their configurations are set up the way they are so that new people can learn by example and even advanced users can take these community configurations and better understand how to adjust them to fit their preferences more closely.
I think at least 280 characters would be reasonable; that should allow enough space to describe a function as well as add short notes on usage. I understand the UI limitations would make it so having a 280 character description would crowd out the binding windows, so I'm fine with the first line being displayed and to see the rest of the text you either hover your mouse cursor over the description OR click the description to open up the full text window. It would also be nice to allow for line breaks so you can put a brief description on the first line then break up the rest of the description using line breaks for clarity.
I just tested it and it looks like coding wise, it can handle newline characters just fine. This works as a "work around", but I think it would be reasonable to support it in the software UI so I don't have to edit a JSON file on a separate monitor.
One thing I found rather disappointing was the apparently 21 character limit on descriptions for controller bindings. Coming from AHK and a self-taught scripting background, I use comments in code all the time to explain why I did what I did and make notes on how the binding may be modified to achieve different results. But 21 characters is barely enough to make a reference ID to a note document let alone actually describe a single thought process or concept. I know the software is capable of storing that information because I opened one of the .rewasd files in a text editor, made one of my comments longer, saved it, and while the text was cut off in the software window, it did allow that information to be retained.
Having more space isn't just about me making personal notes on my own binding profiles; people who are sharing configurations to the community could help each other understand how and why their configurations are set up the way they are so that new people can learn by example and even advanced users can take these community configurations and better understand how to adjust them to fit their preferences more closely.
I think at least 280 characters would be reasonable; that should allow enough space to describe a function as well as add short notes on usage. I understand the UI limitations would make it so having a 280 character description would crowd out the binding windows, so I'm fine with the first line being displayed and to see the rest of the text you either hover your mouse cursor over the description OR click the description to open up the full text window. It would also be nice to allow for line breaks so you can put a brief description on the first line then break up the rest of the description using line breaks for clarity.
I just tested it and it looks like coding wise, it can handle newline characters just fine. This works as a "work around", but I think it would be reasonable to support it in the software UI so I don't have to edit a JSON file on a separate monitor.
Attached Files
Comment