1. dead buttons??
All my buttons work, however when I click the "Begin" button to start a
program, my "Cancel" button is now dead eventhough I've never disabled it.
Some, like updates need to have a dead Cancel button but stuff like reports
and non updates need this to work. Any Idea's why this is so? It seems the
"object" nature of the program objects is broken.
george
2. Re: dead buttons??
On Sat, 09 Aug 2003 15:17:15 -0400 (08/10/03 05:17:15)
, George Walters <gwalters at sc.rr.com> wrote:
>
>
> All my buttons work, however when I click the "Begin" button to start a
> program, my "Cancel" button is now dead eventhough I've never disabled
> it.
> Some, like updates need to have a dead Cancel button but stuff like
> reports
> and non updates need this to work. Any Idea's why this is so? It seems
> the
> "object" nature of the program objects is broken.
Hope I'm not out of line here, George, so please excuse my questions...
Are you talking about an app you wrote using Win32lib?
By the term "dead" do you meaning that the button is disabled (text greyed
out) or do you mean it just doesn't respond even though it looks like its
enabled?
Win32lib does not automatically disable buttons. You have to explictly
disable them yourself.
Can I see the handler code for the Click_Begin button?
--
Derek
3. Re: dead buttons??
- Posted by eugtk at yahoo.com
Aug 11, 2003
--- George Walters <gwalters at sc.rr.com> wrote:
>
> All my buttons work, however when I click the
> "Begin" button to start a
> program, my "Cancel" button is now dead eventhough
> I've never disabled it.
> Some, like updates need to have a dead Cancel button
> but stuff like reports
> and non updates need this to work. Any Idea's why
> this is so? It seems the
> "object" nature of the program objects is broken.
Just to clarify - are you talking about starting some
long process such as printing a report,
and then wanting to interrupt that process before it
is complete by hitting "cancel"?
AFAIK, since Eu doesn't do threads, it (and Winlib)
are not going to be checking for button presses while
doing something else. I think there's a peekEvents
call
or doEvents or similar you could add to your print
routine to periodically check for queued events like
button clicks. After each line is printed, for
example.
I don't do Windows, however. Someone else will have
to come up with the correct name.
Regards,
Irv
