You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, txt files have the model ID as their name. Maybe it's better if they have the keyboard name in the file name, too? Some people have 2 keyboards, having files with distinguishable name such as "655491117GK61 RGB.txt" would be far better in my opinion.
The text was updated successfully, but these errors were encountered:
To not be a breaking change this would need to be optional i.e. support both 655491117.txt and 655491117-GK61 RGB.txt. Code like the following would need to be changed to check multiple paths:
I forked a copy to play with it. I added command line args for gui mode and a filename option and prefix. This way I can play with multiple files for the same device at the same time. It was easier to do rollbacks this way. This seems to work pretty well.
Currently, txt files have the model ID as their name. Maybe it's better if they have the keyboard name in the file name, too? Some people have 2 keyboards, having files with distinguishable name such as "655491117GK61 RGB.txt" would be far better in my opinion.
The text was updated successfully, but these errors were encountered: