bone
Member
Hello all,
I've written a routine that scrolls a bright green oval (positioned behind existing 'goto screen' buttons to create a 'halo' effect) in sequence through menu selections on my Panelview+ 700.
I am using a detented quadrature encoder with a pushbutton to select the desired screen that I want to switch to.
That all works fine, but the problem I'm having occurs whenever I return to the main menu. I am using logic to increment/decrement my menu selection value based on the 4 states of the quad encoder, and when I return to the subroutine that handles the highlight scroll, it automatically increments/decrements depending on the last state of the encoder direction senses, whereas I would like the last highlighted button to remain selected.
Is there any way to sense a 'generic' screen change (i.e. - pulse a bit from the Panelview on ANY screen change) to unlatch the 'count up' or 'count down' bits that I'm using to determine count direction?
Hopefully this makes sense????
Thanks,
Bone
I've written a routine that scrolls a bright green oval (positioned behind existing 'goto screen' buttons to create a 'halo' effect) in sequence through menu selections on my Panelview+ 700.
I am using a detented quadrature encoder with a pushbutton to select the desired screen that I want to switch to.
That all works fine, but the problem I'm having occurs whenever I return to the main menu. I am using logic to increment/decrement my menu selection value based on the 4 states of the quad encoder, and when I return to the subroutine that handles the highlight scroll, it automatically increments/decrements depending on the last state of the encoder direction senses, whereas I would like the last highlighted button to remain selected.
Is there any way to sense a 'generic' screen change (i.e. - pulse a bit from the Panelview on ANY screen change) to unlatch the 'count up' or 'count down' bits that I'm using to determine count direction?
Hopefully this makes sense????
Thanks,
Bone