newlispfanclub.alh.net

* Win32 back to non UTF-8 mode for binary installer

* Guiserver now switches automatically when running UTF-8 enabled newLISP

* new event registration with 'gs:window-moved' and 'gs:windows-resized' (see new move-resize-demo.lsp)


for files and changes notes: http://newlisp.org/downloads/development/

Lutz

Thanks !
Now it's running again on Win32 ... End of panic :-)

Fine and usefull, the new GUI-server functions gs:window-moved and gs:window-resized.

All is well on MacOS X Tiger here, Lutz. Thanks!

With the new resize event: - I added it to my slideshow script. It handled the continuous updating reasonably well for smaller images, when an image was being displayed at full screen... But for bigger images the resize actions started lagging behind a lot - so that the images inside the window were still changing size many seconds after the window had stopped being resized.

So - something to add to the list of possible future enhancements one day - would be a flag that suppresses (or controls) updating until the resize action has finished...

I suggest to change the library path for linux to
/usr/lib/libsqlite3.so.0 (at least Debian and Ubuntu)
instead of
/usr/local/lib/libsqlite3.so

I think there now distributions rests with the libsqlite in /usr/local

Does anyone have different paths?

For the first, window-resize works great!
Thanks, Lutz!

About get-bounds within check-event: my recent investigations shows that calling gs:get-bounds produces additional event like
( set 'gs:bounds '(0 0 535 746))
which, in turn, rises next check-event interruption. And situation is looping...

Unfortunately date-value gives time by seconds which is too long period. So this task became intrivial....

With exception of gs:get-selected-text, which specifies an event handler explicitly, all other gs:get-xxx wait for an event to update a variable gs:xxx using gs:check-event, in effect all these are blocking until the gs:xxx variable is updated:
Lutz

ps: you could use the 'time-of-day' function to get milliseconds resolution, but be careful that the number returned rolls over at midnight ;-)

Lutz wrote: ps: you could use the 'time-of-day' function to get milliseconds resolution, but be careful that the number returned rolls over at midnight ;-)

Oh! Thanks! That's quite for me!