I think you may be going through more work than you need to. What you
should do to safely get parameters is to
override the open event, grab your parm and then call the open event. This
way, you get first crack at the parms.
e.g.
// Override the ancestor to ensure safe arrival of the
parameter.
is_parameterToWindow = message.stringParm // (or
whatever datatype)
return super::event open()
Daniel
----- Original Message -----
From: Marvin Young <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 22, 1999 9:57 AM
Subject: PFCSIG Will of_GetxxxParm() Solve My Message Clobbering Problem?
> I just realized that since I'm using n_msg as my message object, I can
make use of of_GetxxxParm() to retrieve openwithparm() parameters.
>
> I gave up on openwithparm() earlier because I found that my w_response
windows' message.doubleparm and message.stringparm variables were getting
overwritten by one of my PFC services (Linkage, as I recall. Or maybe it
was Resize.)
>
> Before I rip out my current "gnv_app.ia_parmkludge[]" solution, I'd like
to know whether I can truly use of_GetxxxParm() to reliably pass parameters
to my response windows? Anyone out there had experience with this?
>
> Thanks for any light you can shed,
>
>
> Marvin Young
> Washington State Department of Fish and Wildlife
> [EMAIL PROTECTED]
> (360) 902-2508
>
> > [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS,
ADDRESS
> > A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help
pfcsig
> > SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
>
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
