Re: What we really need...
- Posted by Derek Parnell <ddparnell at bigpond.com> Nov 15, 2002
- 473 views
Excuse me gentlemen for breaking into this conversation, but I'm the person who places the documenation (in tagged form) into Win32lib. Is there a problem that I can help with? ---------------- cheers, Derek Parnell ----- Original Message ----- From: <petelomax at blueyonder.co.uk> Sent: Friday, November 15, 2002 9:36 PM Subject: Re: What we really need... On Thu, 14 Nov 2002 20:57:40 -0800, Dan Moyer <DANIELMOYER at prodigy.net> wrote: >Pete, > >I'm confused. I am currently displaying details taken directly from win32lib, eg: >global procedure returnValue( atom returns ) >--------------------------------------------------------------------------- >/topic Events >/proc returnValue( value ) >/desc Override default value returned by handler. > This allows you to override the value an event handler returns to Win32. > By default, when an event is processed, it goes through these steps: > > /li /onEvent: If there is an /onEvent handler for this control, it > is passed the event. > /li Event Trap: If there is a specific handler for this event, that > handler is triggered. For example, /b WM_SETFOCUS triggers > /onGotFocus, /b WM_SIZE triggers /onResize, etc. > /li Default Windows Handler: Finally, the default Window handler for > the control is called. In the case of subclassed /controls, > /i CallWindowProc calls the normal handler; for /windows, > /i DefWindowProc is called. > > Setting /returnValue causes processing to stop at the step that the > value was set in, and return that value to Windows. > > Example: (not tested yet!) > >/code > -- prevent Button1 from seeing any space bar keys > procedure Button1_KeyDown( /int keycode, /int shift ) > if keycode = VK_SPACE then > -- set return value > /returnValue( True ) > end if > end procedure > /onKeyDown[ Button1 ] = routine_id("Button1_KeyDown") >/endcode As you can see, things could be improved for on-screen display. I don't think it is terribly difficult to strip /i /b /code /endcode /li /n /topic /proc /desc and whatever else I might have missed to make the text a bit more legible when displayed in a window. > >A routine to strip the Win32Lib slash-tags *off* that I'm trying to *add*? >If you're talking about displaying the source code for a library of >routines, > why not just show the original source before I add the slash-tags? ^^^^^^^^^^^^^^^^^^^^^^ My turn to be confused. You mean you are *NOT* saving the slash-tags you are adding in the source file? Pete > >?? >Dan > > >----- Original Message ----- >From: <petelomax at blueyonder.co.uk> >Sent: Thursday, November 14, 2002 1:19 AM >Subject: Re: What we really need... > > >On Wed, 13 Nov 2002 19:32:07 -0800, Dan Moyer ><DANIELMOYER at prodigy.net> wrote: > >>As part of the "Libraries Manager", I'm working to create a utility that >>will make it easy to "retro-fit" the Win32Lib "slash-tags" into existing >>libraries. > >When you do that, can you provide me with a small routine to strip >most of these from the text for display on-screen, ie something I can >call just before setText() on each line. > >Pete > > >========================