1. RE: IDE stand-alone Editor bug
Will this be added?
CoJaBo wrote:
>
>
> The warning errors still appear on the stand-alone editor. Adding:
> setWarning(0)
> will correct this, IDE no longer displays those warnings.
>
2. RE: IDE stand-alone Editor bug
"drawRectangle:Rectangle failed" and
"bitBlt:BitBlt failed"
are the 2 errors that come up in huge numbers during standby or logoff,
if these can be fixed in Win32Lib, "setWarning(0)" will not be
necessary.
Derek Parnell wrote:
>
>
> ----- Original Message -----
> From: "CoJaBo" <cojabo at suscom.net>
> To: <EUforum at topica.com>
> Subject: RE: IDE stand-alone Editor bug
>
>
> > Will this be added?
> >
> > CoJaBo wrote:
> > >
> > >
> > > The warning errors still appear on the stand-alone editor. Adding:
> > > setWarning(0)
> > > will correct this, IDE no longer displays those warnings.
> > >
> >
> Hopefully never. This will only mask some potential bugs. I'd rather the
> bugs were fixed instead.
>
> --
> Derek
>
>
3. RE: IDE stand-alone Editor bug
> -----Original Message-----
> From: CoJaBo [mailto:cojabo at suscom.net]
> Subject: RE: IDE stand-alone Editor bug
>
>
>
> "drawRectangle:Rectangle failed" and
> "bitBlt:BitBlt failed"
> are the 2 errors that come up in huge numbers during standby
> or logoff,
> if these can be fixed in Win32Lib, "setWarning(0)" will not be
> necessary.
>
These have been 'fixed' in the soon-to-be-released library. I never actually
get these messages on my systems so it might be an XP thing.
I'm also going to upgrade the setWarning() call so that specific warnings
can be turned off and on.
--
Derek
4. RE: IDE stand-alone Editor bug
Derek Parnell wrote:
>
>
> > -----Original Message-----
> > From: CoJaBo [mailto:cojabo at suscom.net]
> > Sent: Monday, 23 February 2004 10:33 AM
> > To: EUforum at topica.com
> > Subject: RE: IDE stand-alone Editor bug
> >
> >
> > "drawRectangle:Rectangle failed" and
> > "bitBlt:BitBlt failed"
> > are the 2 errors that come up in huge numbers during standby
> > or logoff,
> > if these can be fixed in Win32Lib, "setWarning(0)" will not be
> > necessary.
> >
>
> These have been 'fixed' in the soon-to-be-released library. I never
> actually
> get these messages on my systems so it might be an XP thing.
Pre Win XP OSes do not support what causes the problems, so you may not
have gotten them.
Are you saying that these warnings will not be displayed now?
>
> I'm also going to upgrade the setWarning() call so that specific
> warnings
> can be turned off and on.
>
> --
> Derek
>
>
5. RE: IDE stand-alone Editor bug
> -----Original Message-----
> From: CoJaBo [mailto:cojabo at suscom.net]
> Subject: RE: IDE stand-alone Editor bug
>
>
>
> Derek Parnell wrote:
> >
> >
> > > -----Original Message-----
> > > From: CoJaBo [mailto:cojabo at suscom.net]
> > > Sent: Monday, 23 February 2004 10:33 AM
> > > To: EUforum at topica.com
> > > Subject: RE: IDE stand-alone Editor bug
> > >
> > >
> > > "drawRectangle:Rectangle failed" and
> > > "bitBlt:BitBlt failed"
> > > are the 2 errors that come up in huge numbers during standby
> > > or logoff,
> > > if these can be fixed in Win32Lib, "setWarning(0)" will not be
> > > necessary.
> > >
> >
> > These have been 'fixed' in the soon-to-be-released library. I never
> > actually
> > get these messages on my systems so it might be an XP thing.
> Pre Win XP OSes do not support what causes the problems, so
> you may not
> have gotten them.
These are failing with an invalid handle error code. It may be true that the
handle (a Device Context) is invalid at the time, but I'm wondering why the
IDE is bothering to call these functions if the window they are using is in
hibination or shutdown. I remember when coding in VB, that I'd often need to
check if a window was minimized before working with the controls in that
window - so maybe there is an XP API call to test if the machine is in
hibination mode or similar.
> Are you saying that these warnings will not be displayed now?
Yes, those two specific warnings (and a few similar ones) will not be
displayed now. If they fail, there will be no indication that that have done
so. I *do not* like this approach, and I'm coming up with an alternative,
but its not ready yet.
--
Derek
6. RE: IDE stand-alone Editor bug
Derek Parnell wrote:
>
>
> > -----Original Message-----
> > From: CoJaBo [mailto:cojabo at suscom.net]
> > Sent: Monday, 23 February 2004 11:07 AM
> > To: EUforum at topica.com
> > Subject: RE: IDE stand-alone Editor bug
> >
> >
> > Derek Parnell wrote:
> > >
> > >
> > > > -----Original Message-----
> > > > From: CoJaBo [mailto:cojabo at suscom.net]
> > > > Sent: Monday, 23 February 2004 10:33 AM
> > > > To: EUforum at topica.com
> > > > Subject: RE: IDE stand-alone Editor bug
> > > >
> > > >
> > > > "drawRectangle:Rectangle failed" and
> > > > "bitBlt:BitBlt failed"
> > > > are the 2 errors that come up in huge numbers during standby
> > > > or logoff,
> > > > if these can be fixed in Win32Lib, "setWarning(0)" will not be
> > > > necessary.
> > > >
> > >
> > > These have been 'fixed' in the soon-to-be-released library. I never
> > > actually
> > > get these messages on my systems so it might be an XP thing.
> > Pre Win XP OSes do not support what causes the problems, so
> > you may not
> > have gotten them.
>
> These are failing with an invalid handle error code. It may be true that
> the
> handle (a Device Context) is invalid at the time, but I'm wondering why
> the
> IDE is bothering to call these functions if the window they are using is
> in
> hibination or shutdown. I remember when coding in VB, that I'd often
> need to
> check if a window was minimized before working with the controls in that
> window - so maybe there is an XP API call to test if the machine is in
> hibination mode or similar.
It actually happens only when the computer is going into, or comeing out
of, standbt/ hibernat mode.
>
> > Are you saying that these warnings will not be displayed now?
>
> Yes, those two specific warnings (and a few similar ones) will not be
> displayed now. If they fail, there will be no indication that that have
> done
> so. I *do not* like this approach, and I'm coming up with an
> alternative,
> but its not ready yet.
That will do for now.
>
> --
> Derek
>
>
