Australia
I haven't included a log or system info because it doesn't need it, as I will explain. All that might be of interest is that I'm using BlueTwo skin.
So, let's get down to it. The GUISpinControl has three "SpinType": Int, Float and Text.
When the type is either Int or Text you can press buttons on your remote to select a value for the control.
When the type is Int, you can hit your remote buttons to key in a value. That's fine, it works great, you can try it in the settings screen where you set the padding time for recordings (Pre-Record, Post-Record).
When the type is Text, you can press the numbers on your remote and it will jump to the list location that corresponds with those numbers.
So, for example. The spin control might have three options:
"Hello", "World", "Goodbye".
You press the number two, and the spin control changes to "Goodbye". Simple. Zero based indexing aside, it works. Starting at 1 would be more intuitive for the non-programmer types around though.
But this is where things get interesting, say you go to Settings->Screen->Scroll Speed
These look like they are numbers, so you punch in a number on your remote and it all turns to goo.
It's because these spin controls are actually text. So when you press 1, you don't get "1" you get the text at list index 1, which might be "11". This is pretty confusing.
These Text dressed as Int spin controls are also in the "My Pictures" setup and a few others (they aren't hard to find).
I don't like to raise an issue without presenting a solution, so I'll try to outline how it could be fixed...
1. If it looks like an Int it should spin like an Int. If those controls could be changed from Text type to Int type without error then that's probably best.
or
2. We introduce a "parsing instruction" to the control. Basically, you can have your Text spin control, but when you press a remote button it will either use that as an index, or try to locate a corresponding entry in the list of possible values depending on what "parsing instruction" that control has.
What's the general feeling on this?
I know it's not gunna change the world, but it's all part of the user experience.
So, let's get down to it. The GUISpinControl has three "SpinType": Int, Float and Text.
When the type is either Int or Text you can press buttons on your remote to select a value for the control.
When the type is Int, you can hit your remote buttons to key in a value. That's fine, it works great, you can try it in the settings screen where you set the padding time for recordings (Pre-Record, Post-Record).
When the type is Text, you can press the numbers on your remote and it will jump to the list location that corresponds with those numbers.
So, for example. The spin control might have three options:
"Hello", "World", "Goodbye".
You press the number two, and the spin control changes to "Goodbye". Simple. Zero based indexing aside, it works. Starting at 1 would be more intuitive for the non-programmer types around though.
But this is where things get interesting, say you go to Settings->Screen->Scroll Speed
These look like they are numbers, so you punch in a number on your remote and it all turns to goo.
It's because these spin controls are actually text. So when you press 1, you don't get "1" you get the text at list index 1, which might be "11". This is pretty confusing.
These Text dressed as Int spin controls are also in the "My Pictures" setup and a few others (they aren't hard to find).
I don't like to raise an issue without presenting a solution, so I'll try to outline how it could be fixed...
1. If it looks like an Int it should spin like an Int. If those controls could be changed from Text type to Int type without error then that's probably best.
or
2. We introduce a "parsing instruction" to the control. Basically, you can have your Text spin control, but when you press a remote button it will either use that as an index, or try to locate a corresponding entry in the list of possible values depending on what "parsing instruction" that control has.
What's the general feeling on this?
I know it's not gunna change the world, but it's all part of the user experience.