next »

[Huy H.]

We'd like an ability to automatically clear the status bar message after a certain time has expired in GDC.  This is sort of like the way the current GBC handle messages -- it displays the message, then quietly hides it away.  With GDC the message stays on the status bar until another MESSAGE line is called.

Here's our use case scenario:
User enters some data, in the AFTER FIELD, we validate the data and might warn the user if the data fails validation of some kind.  In such situation, we display a warning message on the status bar.  We had thought about displaying a popup message, but we find that obnoxious and annoying to the user -- especially if they ALWAYS trigger this warning message.  The problem is after the warning message is displayed, it stays there forever.  We have to find a good spot to clear the warning message, but as you might expect -- there's no such place in the code, and it can get pretty messy just trying to clear the warning message.

Has anyone find any other way to elegantly handle this?

If not, our proposal is to add a new style to the Message style that attribute to specify how long the message should be displayed.  After the timeout expired, the front-end client should clear the message.

[Reuben B.]

I would expect you to use ERROR for this scenario.  So perhaps question is what does ERROR do that stops you using it in this scenario?

Also if you note in the AUI tree, ERROR and MESSAGE appear in different places.  ERROR is a child of the Interface as only one displayed at a time whilst MESSAGE is child of Window/Form.  That is why ERROR clears as you exit field whilst MESSAGE remains. To clear MESSAGE then MESSAGE ""

[.]

Hello Huy
Seems that you expect the exact oposite than everybody else. We were required for GBC (but also GMA and GMI) to behave as GDC. Messages and Error need to be persistent as a default for compatibility with 4GL legacy programs (see GBC-2341).
GBC-2341 will be fixed in GBC 1.00.43 but of course you will be able to keep your preferred behavior adding some customization settings.
Olivier.

[.]

Grr ! Fixed in GBC-2341 will be fixed in GBC 1.00.53 and not GBC 1.00.43.

[David H.]

I think there is definitely a need to display warning/status information without interrupting the user. I have previously suggested http://4js.com/fjs_forum/index.php?topic=403.msg1419#msg1419 I would not want to use ERROR as that is reserved for fatal error conditions. Having a history facility (last XXX records) accessed via a button (for missed messages) would be nice as well.