Page flip and button events
mighe
Posts: 39
Hi all, I've found a little problem with page flips and button events.
The following program explains that:
The touchpanel has 2 pages:
- Page1 with 1 soft button (channel 1) and 1 hard button (channel 1)
- Page2 with 1 soft button (channel 2) and 1 hard button (channel 2)
Using the soft buttons I've got the following output, where everything works as expected:
But using the hard button I get:
In other word, after a page flip the release event is lost until we return into the previous page.
I've found this problem both on R4s and 5200s
The following program explains that:
DEFINE_EVENT button_event[dvTp, 1] { push: { send_string 0:0:0, "'PUSHED 1 -> flip to PAGE2'" send_command dvTp, "'PAGE-Page2'" } release: { send_string 0:0:0, "'RELEASED 1'" } } button_event[dvTp, 2] { push: { send_string 0:0:0, "'PUSHED 2 -> flip to PAGE1'" send_command dvTp, "'PAGE-Page1'" } release: { send_string 0:0:0, "'RELEASED 2'" } }
The touchpanel has 2 pages:
- Page1 with 1 soft button (channel 1) and 1 hard button (channel 1)
- Page2 with 1 soft button (channel 2) and 1 hard button (channel 2)
Using the soft buttons I've got the following output, where everything works as expected:
(0000437317) PUSHED 1 -> flip to PAGE2 (0000437384) RELEASED 1 (0000924080) PUSHED 2 -> flip to PAGE1 (0000924387) RELEASED 2
But using the hard button I get:
(0001009755) PUSHED 1 -> flip to PAGE2 (0001011282) PUSHED 2 -> flip to PAGE1 (0001012106) RELEASED 1 (0001014960) PUSHED 1 -> flip to PAGE2 (0001015946) RELEASED 2
In other word, after a page flip the release event is lost until we return into the previous page.
I've found this problem both on R4s and 5200s
0
Comments
The solution is to put the stuff you want to happen on the release. It doesn't really mess up the users experience that much.