Girder 3.2.0 Beta 9/10/11/12/13

[Ron]

I think that Girder is just about done. If no bug reports come in about beta 9/10/11/12 its going to stay there until the weekend and after that 3.2.0 final could be around the corner.

Changes

Fixed saving of iValue3
Added mouse acceleration
Added GetCaption
pld1 through pld10 are now always defined as strings, to prevent scripts for failing on this.
Minor stuff.
Sometimes the group enable/disable crashes Girder (beta10)
Fixed saving of sValue3 (beta11)
Added onresume onsuspend (beta11)
Fixed monitor APM failure (beta11)
Updated keyboard plugin to prevent stuck alt/shift and control (beta11)
Fixed crash on load file / new file if events came in (beta11)
Fixed OSD redraw problems. (beta11)
Added missing i18n stuff (beta12)
Fixed onresume/onsuspend when the computer closed to fast ( the are limitiation though, only 1 events will go through nothing more. (beta12)
Colors in the settings dialog to indicate status of the plugin (beta12)
Double click in plugin list on settings window now works (beta12)
Plugins are now automatically put into event sending mode when they are selected from the settings dialog ( no more F9-F9 sequences ) (beta12)
Hide girder setting to false by default. (beta12)
Better feedback about failed plugins when Girder window is open. (beta12)
Fixed a very visible crash that was introduced in beta 12 (beta 13)
More i18n tweaks. ( beta 13)

If there are any showstoppers in this version let me know.

[Scotchfox]

The Slink-e plugin included in 3.2b9 zip file can't be loaded at Girder start.
I noticed it's 149 ko, previous version (that works with beta 9) is only 45 ko!

[Ron]

Did i do it again ;-) I included the debug version... beta 10 contains the correct version.

[Ingo]

installer creates plugins\software and plugins\hardware
sntp.dll is put in one these...

do you have any news about an updated version of Mario's blocking keyboard plugin? I really would like to test 3.2 ;-)

[Ron]

Thanks, I'll correct the installer.

I took a look at that plugin, it is an MFC plugin, I'm not going to touch that ;-). But anyone can port it, the source is available.

[Icthus]

This may be a stupid question, but what is MFC?

[Ron]

MFC = Microsoft Foundation Classes, some people love it, others hate it. Guess in which group i go :-)

[Ingo]

MFC = Microsoft Foundation Classes, some people love it, others hate it. Guess in which group i go :-)

you love it? ;-)

porting: unfortunately my c/c++ knowledge isn't good enough..... just sent a message to mario, lets hope he's going to port it ;-)

[Ingo]

just sent a message to mario, lets hope he's going to port it ;-)

ok, already got an answer from him... he's out of windows, using linux now, so he's not going to do it...

[Ron]

Ah he went over to the good-guys ;-)

[Icthus]

Thanks for the explanation of MFC.

Speaking of Linux, I've got a dual boot machine with SuSE Linux 7.4 and Windows 98 SE. I've had both Linux and Windows on my machine for about 2 years now, and I use both off and on (mostly Windows for graphics, Linux for programming).

About a month ago, I was about to completely wipe out my Windows installation and just go with Linux. But then I got my IRMan and found out about Girder. Well, suffice it to say that I'm now using Windows all the time, and I'm quite happy now that I can do all this cool stuff with Windows. So, Girder has single-handedly kept me from dumping Windows for Linux. It's filled my need to write little scripts to do cool things. Well, plus I get my Unix fix at work :)

[SouthyPar]

(beta11) Hmmm, I am seeing the empty values for pld1 through pld10 on my F10 (show variables) window. They appear right when I start Girder.
Shouldn't these be hidden from this display?

[Ron]

Nope they are there on purpose. If you make a GVMS that depends on the pld# to be a string the script will fail if they have not been defined. So I decided to have them around all the time, allthough empty if there is no event.

[Ron]

Keyboardex (blocking) has been ported to Girder 3.2, be sure to get the updated convertor (1.5)

[anonim]

hmm maybe i am the only one who doesn't know this since nobody else has asked, but what is the significance of the string variables pld1 through pld10? i understand why it would crash if you tried to give them values without defining them, but i would assume that this would be true of any variable. why not define var1 through var10, or this_is_a_variable1 through ... you get my point. the only thing i can think of is some commands use pld1 through pld10 in a hidden way? can someone clear this up for me..

[Mark F]

pldX (where 1<= X <=10) are the names of special Girder string variables that contain the payload data strings that a plugin can pass with the event string.

Let me give a usage example to try to explain better:

The DVDSpy plugin generates events based on stuff going on in the currently playing DVD. One of those events is the current playing time. This event, by itself (current playing time changed) is pretty worthless. Add some extra data (the current playing time = 1:00:01) and you have an interesting event.

The problem is you want to pass this extra data but where do you put it? If you place it in a variable outside of the event processing stream, the data and events are not synchronized. If you add it to the event string itself, you have infinite events and the user has a hard time keying off the one they want.

The solution was to add extra (payload) data to the event processing mechanism. The first part of the payload data has a specific format to allow ASCII strings to be passed and these strings are assigned to pld1-10 before an event handler (command) is sent the event.

Does this help? :D

[anonim]

i think that i need to read it through slowly a few more times to grasp everything you said, but i think you explain it pretty clearly. thanks.