Touchpanel page flips delays?
vegastech
Posts: 369
I am trying to perform page flips on my touchpanel via netlinx, so that I can properly introduce a please wait screen while the system is powering up. However, it seems that the codes don't always work - or at least don't all work. I am doing this:
DEFINE_FUNCTION fcnSAT() //Satellite Macro
{
IF (nSysOn = 0)
{
fcnROOMON()
SEND_COMMAND dvCV7Tp, "'@PPX'"
WAIT 20 'panel wait screen'
{
SEND_COMMAND dvCV7Tp, "'PPON-wait'"
}
WAIT 100 'Power On Delay'
{
PULSE[dvTV,131] // tv/video
WAIT 20 'tv input sat'
{
PULSE[dvTV,16] // #6
PULSE[dvRCVR,81] //TVDBS input
nCurrSource = 1
SEND_COMMAND dvCV7Tp, "'PPON-tv'" //flip to sat popup
}
}
}
when the function is run, kill all popups, then introduce the wait screen, and then show the tv popup.
ELSE
{
PULSE[dvTV,131] // tv/video
WAIT 20 'tv input sat'
{
PULSE[dvTV,16] // #6
PULSE[dvRCVR,81] //TVDBS input
nCurrSource = 1
SEND_COMMAND dvCV7Tp, "'@PPX'"
SEND_COMMAND dvCV7Tp, "'PAGE-main'" //flip to dvd popup
SEND_COMMAND dvCV7Tp, "'PPON-footer; main'"
}
}
}
It seems that the PPX (close all popups) works, but then nothing thereafter works. Do I need a delay between commands? 0
Comments
That said, I've never had a problem calling a page flip, then immediately calling a pop-up on the page. I also tend not to use the "pop-up; page" nomenclature, I just use the pop-up name. I can't imagine that has any bearing on it, but you never know. I also use the @PPN command instead of PPON, but again can't imagine that matters. My suspicions all fall on PPX.
I have used PPX in the past, never had an issue with it.
I DO use the "pop-up; page" nomenclature without issue. I always specify the page for the popup. My reason for doing this is because during commissioning I would often go into the TP's setup pages (for whatever reason) and occasionally one of my popups would show up. Something in the code would trigger the PPN command and then there was no way to get the popup OFF of the setup page other than manually sending a command or rebooting the TP.
+1 on that!
I actually use @PPX quite often (in every job for the past 5 years) and have never had a problem with it.
define_function fn_ui () { send_command dv_TP, '@PPX' send_command dv_TP, '@PPN-Source Nav' switch (i_source) { case DVD: send_command dv_TP, '@PPN-Source DVD' case VCR: send_command dv_TP, '@PPN-Source VCR' case SAT: send_command dv_TP, '@PPN-Source SAT' } }Of course there are ways around this (have the nav as part of the PAGE instead of the POPUP, etc.) but for flexibility (able to use the same TP file for different areas, etc.) using popups is a much better way to go. IMHO
I much prefer to "manually" track all my popups (like Dave mentioned) and either close individual popups as necessary, or use groups to automatically handle them.