Enterprise Client Community

Hi Björn,

the statusbar is cleared very quickly after I displayed a message.
I saw in the source code that a thread is executed somehow after the render phase.
This is a problem in our case since we refresh our workspace after some action (i.e. save data) automatically and the server callback is done immediately afterwards.
So the user barely has time to read the message.

If you don't understand what I mean, I invite you to a yuuguu session!

Frauke

...yes, I understand what you mean. The statusbar always shows the message "one response long". If now the ACTIVEX call back is done, then the message is removed when the resposne of the callback is received on client side.

There is only one chance...: you need to tell us within a request that the (previous) status message should be kept. I.e. we can provide an interface (Statusbar.showPreviousMessage or so) that you can call in these situations in which you are doing the callback processing.

OK with this?

Björn

Yes, that's ok.

And then I call Statusbar.clear() manually when I want to clear the message?

Thanks
Frauke

I would prefer that still the clearing is done automatically. Otherwise messages will never-ever be cleared...

Via the API you can preserve the message for the current roundtrip - because you know that the current roundtrip is one which is not initiated by a user event...

DURING WRITING: what's about the following idea: the client side knows that the request created by the AcitveX callback is a non-user-action request. The client as consequence can know on its own that the current status bar should not be cleared with the next request. In this case you do not have to do anything... - That's the way to do it!

Sould be available quite fast...

Björn

But careful, not everything coming from me has to to something with ActiveX.

In this case its just invoking a new search in our GenSearchBean. And this redisplays the result list.

So I don't think your solution would be that easy.

Frauke

...but again the activity is triggered by an automated event (MESSAGELISTENER). In this case the same mechanism would be active.

OK from your opinion?

Björn

YES!
As far as I understand the matter.....

...OK, is implemented + available with next update...
Björn

No,
new anti clear function does not work yet (version 20080606)