Girder 3.1 beta 2

[Ron]

Girder 3.1 beta 2 has been released.

Lots of fixes and usability changes, please give it a spin. It feels pretty solid to me. I'm sure that one of you guys will break it :smile:

[Ron]

Ah btw, the AST plugin was updated. I remember some people complaining about it.

[Ron]

A fun fact is that Girder executes groups too :smile: oops, need to fix that.


F5 and Jumping ( via Goto, or links ) doesn't check if any of the parents is disabled. Should Girder check for this ?

[Ron]

Naah, lets not call it a feature :smile:

Okay the F5 now ignores the parent group enabled state, however if there is a jump inside the command that the F5 triggered the jump will only be done if the target and its parents are enabled. As one would expect!

thus jumps ( goto etc ) will not be triggered if any of the parent groups are disabled.

<font size=-1>[ This Message was edited by: RonB on 2002-03-07 00:18 ]</font>

[Ron]

Indeed this has always been there, you first need to hit apply so the plugin is actually loaded.

[Ron]

Ah installer error :wink:

[Ron]

Well its not really logical/userfriendly but hey it is girder that we are talking about :grin:

[Ron]

Okay just before i go to sleep here is beta 3. with the fixes that we talked about here.

[Ron]

Before I forget beta3 includes the "Explicit Return"

[Ron]

Checkreg: checking what is wrong with checkreg.

AST:yes the mouse doesn't move by default right now. I'm adding an option so users can choose if the mouse should move yes or no... hang on a little.

[Ron]

Checkreg is fixed ( in Beta 4 later today )

[Ingo]

testing (F5) a command in a disabled group executes it. executing it via an event doesn't (that's what I expected it to be).

[Ingo]

On 2002-03-06 23:46, RonB wrote:
A fun fact is that Girder executes groups too :smile: oops, need to fix that.


sounds nice... if you don't fix it.. call it a new feature :wink:



F5 and Jumping ( via Goto, or links ) doesn't check if any of the parents is disabled. Should Girder check for this ?


goto yes
F5/testing don't care very much... (but executing a goto when testing should)

[Ingo]

On the Hardware plugins tab, when you select a plugin you cannot configure it until you hit apply/ok.


that didn't change... I think it has always been that way ....

[Ingo]

On 2002-03-07 01:04, RonB wrote:
Before I forget beta3 includes the "Explicit Return"


hey ron, that's definitly unfair... I just wanted to go to bed too... :wink:

[Ingo]

using 3.1b2: can anyone chek if check Reg is ok?

my logarithmical accellerated volume thing seems to be broken. check reg. < 100 jumps to first link even for [reg25]>50000

so, now it's realy time to go to bed for me :wink:

[mattwire]

In my opinion it would be better if goto etc checked if the parent is disabled. I have a number of multigroups setup which have a list of ~5 goto commands. Controls for different apps are stored in separate groups, only one of which is enabled. Hence, I don't have to check which app is running - I can just call all 5 and only one will execute.

[mattwire]

I think F5/testing should execute independently of whether parent is enabled/disabled: since the user has specifically said 'test this command' it is obviously meant to be running!

[mattwire]

Cool.
I think I just found a bug in beta2...
On the Hardware plugins tab, when you select a plugin you cannot configure it until you hit apply/ok. Surely you should be able to configure it just by ticking it in the list? - or even just by highlighting it?

[mattwire]

Also, it looks for help in [girderdir]/help but your installer puts help in [girderdir]/help files

[mattwire]

I see, yes it would make sense when you think about it... maybe I should wake up...

[Nikolai]

Hey, very nice improvements. Testing the AST plugin, I appear to be having different problems...it's listening to the remote (showing the angle of the press in the status bar), but the pointer doesn't move by default. Do I have to make Girder commands for the mouse movements?

[GoldServe]

The check reg seems to be broken too. I've used the sendmessage 1.5 plugin to check the play status of winamp and save it in the reg. Condition check reg seems not to be working as it always executes the play even when the song is playing. Worked fine in 3.0.