[progress Communities] [progress Openedge Abl] Forum Post: Re: Abl.net Basic Questions

  • Thread starter Thread starter Mike Fechner
  • Start date Start date
Status
Not open for further replies.
M

Mike Fechner

Guest
I would check from the outside – before you launch the Form – if this is o.k. to be started. Throwing an error from the constructor of a hybrid class – may prevent you from starting it later in the same session. Use the Validating event and set e:Cancel to TRUE. Look up for the Validate() method of the Form or UserControl. This will basically be raising the Validating events of the Controls to allow for validation. THIS-OBJECT:GetClass():TypeName (ABL). or THIS-OBJECT:GetType():FullName (.NET). Both works for hybrids. Von: Piotr Ryszkiewicz [mailto:bounce-piotrryszkiewicz@community.progress.com] Gesendet: Montag, 23. Oktober 2017 11:18 An: TU.OE.Development@community.progress.com Betreff: [Technical Users - OE Development] ABL.NET basic questions Update from Progress Community Piotr Ryszkiewicz Hi, I just started experimenting with ABL.NET GUI programming (and OOP as well), and now stumbling with few quite basic questions. 1. I have class constructor which draws my window. But before it does so, it should run some business controls to check if the window can be really started. If the result of such control is false, how can I prevent the window from starting ? I discovered that RETURN ERROR from constructor does the job, but is it the only and recommended option ? 2. How to simulate RETURN NO-APPLY in leave trigger of textbox to force user to enter correct value ? 3. How to implement business validation on pressing "Save" or "OK" button. Or specifically - how to stop window from write data if the result of validation is false ? 4. Is there something like {&SELF-NAME} which I can use inside the trigger ? Any help would be appreciated :) Piotr View online You received this notification because you subscribed to the forum. To stop receiving updates from only this thread, go here . Flag this post as spam/abuse.

Continue reading...
 
Status
Not open for further replies.
Back
Top