Hi.
In one of our projects, we got into the habit of using the USE-WIDGET-POOL qualifier on our CLASS statements. However, I never see this used much in OO ABL examples. I know why we did it, but I am now wondering if there is a "best practice" when it comes to using it.
Thoughts?
|
My initial thought is that the concept of needing USE-WIDGET-POOL in the first place is anti-OO but that's just me.
|
> A) it's not needed when the class is not creating dynamic widgets
Thanks for the clarification Mike. That is what I thought. It started out that way and then just bled over as a bad habit as other class files were created.
Factories for queries and buffers? You're going to upset the OO-purists. :)
|
I'm trying to remember, way back, there is also a problem with temp-table if the window class is instantiated and shown by a .p/.w and the .p/.w finishes its work while the window stays open. If USE-WIDGET-HANDLE is not used, temp-table is might be scoped to the .p/.w and not to the class, so temp-table defined inside the class goes away together with the .p/.w or whichever widget pool is currently active.