Re: Web socket connected event and onConfigure

2017-09-14 Thread Peter Henderson
n/MainPanel.html#L40 > > works as expected > Brilliant. Thanks > > > On Thu, Sep 14, 2017 at 4:24 PM, Peter Henderson > <peter.hender...@starjar.com> wrote: > > Hi All, > > > > I have a link on a panel which should only be enabled while there is a &

Re: Web socket connected event and onConfigure

2017-09-14 Thread Maxim Solodovnik
gt; > I have a link on a panel which should only be enabled while there is a > connected web socket. > > The link overrides onConfigure and calls setEnabled [1] > > When a web socket connected event is received I store the connected message > and add the link to the payload ha

Web socket connected event and onConfigure

2017-09-14 Thread Peter Henderson
Hi All, I have a link on a panel which should only be enabled while there is a connected web socket. The link overrides onConfigure and calls setEnabled [1] When a web socket connected event is received I store the connected message and add the link to the payload handler. [2] I expect

Re: Back button not calling onConfigure()

2013-11-06 Thread Artur Kronenberg
Hi, I would expect it to hit the container. Debuggin and testing on a test environment works and hits it. Unfortunatelly there is no way to definitely proove that the error in question hits it to. I do know that the onConfigure is not hit. I don't have access to the access logs

Re: Back button not calling onConfigure()

2013-11-06 Thread Martin Funk
schrieb Artur Kronenberg artur.kronenb...@openmarket.com: Hi, I would expect it to hit the container. Debuggin and testing on a test environment works and hits it. Unfortunatelly there is no way to definitely proove that the error in question hits it to. I do know that the onConfigure

Re: Back button not calling onConfigure()

2013-11-06 Thread Artur Kronenberg
proove that the error in question hits it to. I do know that the onConfigure is not hit. I don't have access to the access logs. Is there a way that the user uses a proxy that disables the response headers we set for caching? Thanks! On 05/11/13 14:22, Martin Grigorov wrote: Hi, It looks like

Re: Back button not calling onConfigure()

2013-11-06 Thread Martin Funk
there is no way to definitely proove that the error in question hits it to. I do know that the onConfigure is not hit. I don't have access to the access logs. Is there a way that the user uses a proxy that disables the response headers we set for caching? Thanks! On 05/11/13 14:22, Martin Grigorov

Back button not calling onConfigure()

2013-11-05 Thread Artur Kronenberg
, the model is still created and the page can't be used. I overwrote the onConfigure method to set up my model correctly and everything works just fine. However there seems to be cases where the onConfigure method is not called? Does anyone know of those cases? Can it have anything to do

Re: Back button not calling onConfigure()

2013-11-05 Thread Martin Grigorov
overwrote the onConfigure method to set up my model correctly and everything works just fine. However there seems to be cases where the onConfigure method is not called? Does anyone know of those cases? Can it have anything to do with the user using a proxy? A weird browser thing? We set

onConfigure()

2012-02-28 Thread Allen Gilbert
OK, one more question, then I'll stop pestering everyone...at least for now : ). Is it problematic to make changes to a Component's model in its onConfigure() method? -Allen

Re: onConfigure()

2012-02-28 Thread Igor Vaynberg
shouldnt be. -igor On Tue, Feb 28, 2012 at 2:58 PM, Allen Gilbert allen.gilb...@doane.edu wrote: OK, one more question, then I'll stop pestering everyone...at least for now : ). Is it problematic to make changes to a Component's model in its onConfigure() method? -Allen

Feature request: use predicates with onConfigure()

2011-06-07 Thread Russell Morrisey
Guys, I would like to see a standard implementation of onConfigure(), where the user can set a Predicate object for the component's visibility, and another Predicate for the enabled state. This is an idea that our team tossed around for a while; since I just discovered the onConfigure

Re: new feature in trunk and branch: Component#onConfigure()

2010-07-21 Thread Johan Compagner
can we now deprecate protected boolean callOnBeforeRenderIfNotVisible() ?? because you could do it now in onConfigure right? I hate multiply things do do the same thing :( On Wed, Jul 21, 2010 at 07:05, Igor Vaynberg igor.vaynb...@gmail.com wrote:  protected boolean

Re: new feature in trunk and branch: Component#onConfigure()

2010-07-21 Thread Igor Vaynberg
its already deprecated -igor On Tue, Jul 20, 2010 at 11:46 PM, Johan Compagner jcompag...@gmail.com wrote: can we now deprecate  protected boolean callOnBeforeRenderIfNotVisible() ?? because you could do it now in onConfigure right? I hate multiply things do do the same thing :( On Wed

Re: new feature in trunk and branch: Component#onConfigure()

2010-07-21 Thread vineet semwal
void onConfigure() * { * setVisible(Math.rand() gt; 0.5f); * super.onConfigure(); * } * } * /pre */ protected void onConfigure() { } /** * Triggers {...@link

Re: new feature in trunk and branch: Component#onConfigure()

2010-07-21 Thread Erik van Oosten
Excellent! Op 21-07-10 07:05, Igor Vaynberg wrote: another new callback added to 1.4/trunk that is aimed at making life easier when managing component states such as visibility, enabled, etc. -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/

new feature in trunk and branch: Component#onConfigure()

2010-07-20 Thread Igor Vaynberg
; * } * } * /pre * * VS * * pre * class MyComponent extends WebComponent * { * protected void onConfigure() * { * setVisible(Math.rand() gt; 0.5f); * super.onConfigure

Re: new feature in trunk and branch: Component#onConfigure()

2010-07-20 Thread Ernesto Reinaldo Barreiro
Igor, Thanks for the new feature!        /**         * Called once per request on components before they are about to be rendered. This method         * should be used to configure such things as visibility and enabled flags.         * p         * Overrides must call {...@code