03:10:58 PM
3GW0WJJZE
Another reason why just "init and params" is a significant effort to rewrite is that often we set properties of many objects on the form. Every time we call the form, now we have to code a bunch because the form is instantiated, and we cannot move previous this.xxx and this.xxx code to the Load, since the Load only fires once. On one form I had to write over 150 lines of code to do what I was doing with the old VFP .show way of doing things. Might be bad style, but it is prevalent
Not a complaint, just an answer to your wondering why people cared so much about this.
I think we need to revise how wForm_Shell() adn wFormNoShow() operate, especially regarding modal returns and call back.
May take a while to clarify all that and maybe enhance aw.vcx!awFrm::wForm*() code.
Could you give me an example of how you envision wform_shell being used? I am so bogged down changing form calls and how my forms talk to each other. I started adding js code to hide and show forms and to do a lot of things because between not having the "noshow" ability and not being able hide/show forms, my infrastructrure on this project has to be completely re-written.
wform_shell() is meant to do additional form settings between .Init() and .Show()
{Personaly I can't figure out why all settings could not be made in .init() based on parameters}
Whoops. Looks like I meant wform_shell, I see that wfornnoshow only runs in LAN mode (in the class notes).
Was just wondering if if you had a chance to follow up on this.
Let me prepare a detailed answer on this question
thanks
Repost:
Could somebody give me an example of properly using wformnoshow? When I use it the form instantiates visibly and I do not get a reference to it back.
TIA