OpenEuphoria

Re: setPrintJobProperty problem

• Posted by CChris <christian.cuvier at agr?culture.gouv.fr> Oct 29, 2007
• 637 views

Andy Drummond wrote:
> 
> CChris wrote:
> > 
> > <big snip/>
> > 
> > > CChris, I *had* modified w32Resources.ew as you said. The actual code is:
> > > 
> > > }}}
<eucode>
> > > global function getDefaultPrinter()
> > >     printerDC = w32Func(xCreateDC,{wsp,pname,0,0})
> > >     setPrinterPointers(1)
> > >     return printerDC
> > > end function
> > > </eucode>
{{{

> > > 
> > > That was copied direct from C:\Euphoria\Win32Lib\include\w32Resources.ew
> > > I did say that I had put it into Win32Lib - about line 1212 in
> > > w32Resources.
> > > So .... I carry on wondering what is going on! Or what I have done!!
> > > 
> > > AndyD
> > 
> > Ok, then I'll have to look at this more thoroughly. Tere's a long weekend
> > ahead
> > for Nov. 1st, so I'll probably find some time to set that right.
> > Does the keyboard handler faultlessly work now?
> > 
> > CChris
> 
> CChris,  I hardly dare say this - I was about to say the keyboard handler
> seems fine now, but I just bound the IDE into an executable, and though it
> seemed OK at first, I did manage to get the shift key effectively latched
> down as far as the arrow keys are concerned. I also managed to get out of
> that state, and I can't manage to do it again having been pretty unkind to
> the system; randomly hitting the shift and the arrow keys and with the odd
> enter key or delete key - I manage to wreck to text but the shift is still OK.
> 
> I think you had better call it OK until such time as I can really find a bug
> and not just a one-off oddity. Good work.
> 
> AndyD

Could you email me the bound IDE and the .prj file you were working on?
I assume you carefully checked that the bound executable included the right lib
version. Send this to cchris005 hat fastmail doubt fm ; I'll see whether I can
reproduce the oddity or not.

Since I have to consider including (part of) GrPrint.ew, and understand the
issue Bernie reported about getFontDialog(), the official next release isn't for
this weekend, so I can call it OK with a glimpse of a hideously elusive bug that
might still be lurking in the darkest alleys of the keyboard.

CChris