Bug or Feature?
Posted: Sat Aug 21, 2021 1:28 pm
Hi Colin,
I've discovered that if you click, for example, the right mouse button and then very quickly click the left, the Langstone acts as if it's received a scroll button click i.e. the lock indicator comes on and the frequency cannot be adjusted. Doing a rapid right/left (or left/right), click turns lock off again. I wonder if this is deliberate or some sort of bug somewhere?
The reason I ask is that I've implemented a 12.5kHz step option on my version of Arduino mouse emulator which is controlled both by a rotary encoder and also a Nextion display. This works as follows...
1) generate 9 right clicks to shift the cursor to the far right digit
2) generate one left click to shift the cursor to the 100Hz digit
3) generate 125 up or down scrolls to shift the frequency up or down 12.5kHz when the rotary encoder is moved one step
Due to the bug-or-feature, the Langstone goes into Lock mode after step 2.
I've fixed my firmware by inserting a 250mS delay between steps 1 and 2. (Anything much less is not enough).
It's obviously not an issue but I'm just interested.
73, Martin - G4FKK
I've discovered that if you click, for example, the right mouse button and then very quickly click the left, the Langstone acts as if it's received a scroll button click i.e. the lock indicator comes on and the frequency cannot be adjusted. Doing a rapid right/left (or left/right), click turns lock off again. I wonder if this is deliberate or some sort of bug somewhere?
The reason I ask is that I've implemented a 12.5kHz step option on my version of Arduino mouse emulator which is controlled both by a rotary encoder and also a Nextion display. This works as follows...
1) generate 9 right clicks to shift the cursor to the far right digit
2) generate one left click to shift the cursor to the 100Hz digit
3) generate 125 up or down scrolls to shift the frequency up or down 12.5kHz when the rotary encoder is moved one step
Due to the bug-or-feature, the Langstone goes into Lock mode after step 2.
I've fixed my firmware by inserting a 250mS delay between steps 1 and 2. (Anything much less is not enough).
It's obviously not an issue but I'm just interested.
73, Martin - G4FKK