![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
| Oppps! found a BIG bug |
|
|
#1 (permalink) |
|
Creator
Join Date: May 2006
Location: Cambridge, UK
Posts: 1,612
![]() |
While adding code for the "tab macros", I discovered a fairly large bug in the button macro sending code. On "touch" and "hold" button types, you can define select and deselect macro lists, but until I found this bug, TB would only send the same number of deselect macros as there were select macros:
Example Code:
macro_select = line 1 macro_select = line 2 macro_deselect = line 3 macro_deselect = line 4 Code:
macro_select = line 1 macro_deselect = line 2 macro_deselect = line 3 This would cause macro lines to be not sent if there was a mismatch in the number of select and deselect entries. I may have to back port the fix to v1.0.2 and release a fix later today.
__________________
![]() ![]() (Setup: XP Pro, classic mode, LinITX 8" touchscreen (Client/Server), 19" touchscreen (Local), latest development version of TouchBuddy) |
|
|
|
|
|
#2 (permalink) |
|
Toolkit Creator
Join Date: May 2006
Location: On your Six!
Posts: 1,870
![]() |
That's weird because after our discussion about the hold button yesterday, I made one of my buttons a hold button with just the macro_select line and no macro_deselect. But it sounds like that should still work? I haven't tested it yet in Lockon though....
__________________
(a.k.a. Snacko) Touchscreen: Innovatek TM-868 8"; Running Local Mode on XP Pro ![]() |
|
|
|
|
|
#3 (permalink) |
|
Creator
Join Date: May 2006
Location: Cambridge, UK
Posts: 1,612
![]() |
having select but no deslect macros wont trigger this bug... only if you have more deselect macros than select macros on a button.
__________________
![]() ![]() (Setup: XP Pro, classic mode, LinITX 8" touchscreen (Client/Server), 19" touchscreen (Local), latest development version of TouchBuddy) |
|
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|