putting the entire macro call 'with-busy' in a future solved the
issue...I have been bitten by this sort of thing before...I'll have tos
top being so forgetful. Thanks for reminding me Dave and also a massive
RESPECT for seesaw :)
Jim
On 14/11/13 20:26, Dave Ray wrote:
As noted over on the S
On Thu, 14 Nov 2013, Jim - FooBar(); wrote:
> I have a (seesaw) GUI with a swingx.busy-label which I want
> activated when certain tasks are performed. The code that i've
> written so fat works perfectly at the repl but for some bizarre
> reason it won't work when attached as a handler to a butto
oops! I am not receiving regular updates from the seesaw mailing list so
I did not see that..sincere apologies.
I will try what you suggest immediately :)
thanks again
Jim
On 14/11/13 20:26, Dave Ray wrote:
As noted over on the Seesaw list, your pdf loading code is blocking
the UI thread. W
As noted over on the Seesaw list, your pdf loading code is blocking the UI
thread. When you call it from the REPL, it's a separate thread so the
button has a chance to update itself. You'll need to put the pdf loading on
a separate thread if you want to the UI to update and stay responsive.
Cheers
Try to create a simple app that just demonstrate the issue. Then send the
sample to the mailing list. Most likely you won't have to send because you
will discover the problem in the process.
Josh
On 14 Nov 2013 23:08, "Jim - FooBar();" wrote:
> Hi people,
>
> I 'll have to apologise in advance
Hi people,
I 'll have to apologise in advance for the potential vagueness of my
question but I am utterly baffled by the behaviour I am seeing and I'd
like to share & ask.
I have a (seesaw) GUI with a swingx.busy-label which I want activated
when certain tasks are performed. The code that i'
