timer event - w_slash screen

[Diane S. Burwen]

Has anyone had trouble with the timer() function in PB 6? Specifically,
I'm using PB 6.5 build 444.

I have the pfc splash screen opening from my appmanager pfc_open event
with

gnv_app.of_splash(2)
Do while isValid(w_splash)
yield()
Loop

This works great under pb 5.0.04.

The w_splash window is supposed to show for 2 seconds then close itself.
This is accomplished by executing the timer(2) function in the open
event of w_splash. The timer event of w_splash executes timer(0) and
close(this). Works fine under 5.0.04.

Under pb 6.5 the splash screen never closes and the app hangs because of
the loop. So, when I get rid of the Do Loop I get really strange
behavior. The splash screen remains open while then the next window in
my code opens. Then next window is a response window. Well the response
window opens, but instead of waiting for a response it closes itself. It
acts as if the code in the w_splash timer event is executed against my
response window. Both the splash screen and the response window close at
the same time.

I've regened everything after sucessfully migrating from pb 5.0.04.
I've tried changing the timer(2) function to timer(2, this) to tell it
specifically which window to start the timer on.
I've tried posting the timer function.
I've checked the timer event of the response window to make sure there's
no code there and added code that writes to a popup window so I know if
the event fired - it doesn't.

If I comment out gnv_app.of_splash(2) the response window waits for a
response.

So, I have to conclude that there is a bug in pb 6.5.

Any patch available???

Thanks,
Diane

[Tom Lauger]

I had the same problem. I finally put this script in rather than using the
yield() function.

n_cst_dateTime lnv_DateTime

lnv_DateTime.of_Wait( 2 )

2 is the same length as my splash screen. After 2 seconds, the logon window
pops and the splash screen closes shortly after that. Hope this helps.

Tom Lauger
TOPAZ Technologies, Inc.

[Eric Aling [TeamPS]]

Hi,

FYI,

I myself do not have problems with timers and I use a lot of them
concurrently ( using the timing object ).

--

- Eric Aling [TeamPS], Cypres Informatisering bv, The Netherlands
http://utopia.knoware.nl/users/cypr115

Diane S. Burwen wrote in message <35DA3476...@mediaone.net>...

[Diane S. Burwen]

More specifically, I have found that a close(this) executed from the timer
event of a popup window will close any open response window without waiting
for user response.

Anyone else having problems?

-Diane

[tow...@my-dejanews.com]

Diane,

We ran into exactly the same problem going from 5.0.04 to 6.0, and in 6.5.
We had included the code with the "yield" command, as indicated in some of
the documentation/infobase (I don't remember which) included with earlier
versions.

We removed the "yield" loop and added the following code just before the first
window of any kind came up:

if isvalid(w_splash) then close(w_splash)

Depending on your application, you may need to experiment with some sort of
"stall" routine in order to keep the splash window open for the proper amount
of time.

We, too, found that the problem seemed to lie with the timer of the splash
window. Using the debugger, as well as inserting various lines of code in
the splash window timer event (both in and outside the debugger), the splash
window timer event never triggered. We are not using timers anywhere else
right now, so I can't say whether it is the timer event in general (I suspect
not, or there would be many more messages), or something about the construct
of the splash window.

Todd

In article <35DC26C6...@mediaone.net>,

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum

[Doug Borresen]

I have tried a lot of different things with PB version 5.x to get the
PFC splash screen to work, and have read about others doing the same. I
could get it to work sometimes with the Yield() technique, but it just
wasn't consistent enough that I could count on it.

For my project, I finally decided the best way to get reliable behavior
was to go with a combination splash and login screen. It works very
well, and eliminates the timing questions keeps your login window open
when you need it. GoldMine 4.0 uses this visual method (not to imply it
is written in PowerBuilder) and it looks great.

Doug