Inactivity event triggers

[lar282]

cool

Is it inactivity of computer or inactivity of xlobby as an application?


//Lasse

[dgemily]

It is the inactivity of computer...

[rbziggy]

This sounds like a great addition. If I understand right it might be especially useful when using a PPC client. First to check:

- Do I need to execute the inactivity event just once (e.g. on entering the menu screen)?
- Will it continue to work for repeat inactivities (i.e. will work after a second period of inactivity) or does it need to be reset each time (e.g. by reentering the menue screen again)?
- Will the resume event work even if the client PPC application is minimised (I'm hoping it will as it's run on the server)?

If this works as I think, I could get the PPC client to minimise after say 5 mins and then resume back to the menu when the screen is tapped. This would solve a problem of the ppc application crashing after an automatic powerdown and may also improve a situation of the ppc app hanging periodicaly (which may be a prob with my wireless network).

Thanks

[dgemily]

This sounds like a great addition. If I understand right it might be especially useful when using a PPC client. First to check:

- Do I need to execute the inactivity event just once (e.g. on entering the menu screen)?
- Will it continue to work for repeat inactivities (i.e. will work after a second period of inactivity) or does it need to be reset each time (e.g. by reentering the menue screen again)?

in fact you have the choice, just one time or repeat...
for a repeat: you have to execute an event with the command "Add Inactivity Event" each time, not just only one time. so in your event enter screen add 2 commands:

Add Inactivity Event
and
Add Revival Event ( for this command, it will execute an event when we go out of an inactivity period, so add in the event that it will be executed the same commands of your enter event. so you will get the repeat fonction).

- Will the resume event work even if the client PPC application is minimised (I'm hoping it will as it's run on the server)?

yep, it should work only on the server...

later,

[rbziggy]

Just tried testing the version 3 ofxevent. Has something changed in the event string syntax as my version 2 events now seem to crash or hang XL?

I notice that xevent now uses a database rather than the old config file. and that the time is split into hrs and mins in the database rather than the hh:mm format in the config file.

To explain, I have an event defined that writes the following to the config file in V2:

Every-year Every-month Every-day|06:20|music:wakeup

But it does this using a variable so the exact syntax in the XL event looks like:

Every-year Every-month Every-day|%variable>atime%|music:wakeup

Where 'atime' is a variable that contains the text 06:20 taken from a screen display variable.

I'm a bit worried that the new version cannot parse the 06 and 20 into the hours and minutes field in the new database format! This may be a big problem for me as my alarm times are held in a database in the 'hh:mm' text format and displayed as a list e.g:

06:00 06:10 06:20 06:30 06:40 06:50 etc (I have the full 24 hrs at 10 minute intervals).

Selecting one of these puts the text into 'atime' and then the event is used to write the xevent alarm as you see above. I'm not sure I could make it work with separate hour and minute variables very easily!

[dgemily]

Just tried testing the version 3 ofxevent. Has something changed in the event string syntax as my version 2 events now seem to crash or hang XL?

I notice that xevent now uses a database rather than the old config file. and that the time is split into hrs and mins in the database rather than the hh:mm format in the config file.

Info: now parameters are stocked in a xlobby database but the parameter to execute an event immediately is stocked in plugins/XEvent/XAlarmeNow.txt and the parameter must be like that : xxx|eventgroup:event

To explain, I have an event defined that writes the following to the config file in V2:

Every-year Every-month Every-day|06:20|music:wakeup

But it does this using a variable so the exact syntax in the XL event looks like:

Every-year Every-month Every-day|%variable>atime%|music:wakeup

Where 'atime' is a variable that contains the text 06:20 taken from a screen display variable.

I'm a bit worried that the new version cannot parse the 06 and 20 into the hours and minutes field in the new database format! This may be a big problem for me as my alarm times are held in a database in the 'hh:mm' text format and displayed as a list e.g:

06:00 06:10 06:20 06:30 06:40 06:50 etc (I have the full 24 hrs at 10 minute intervals).

Selecting one of these puts the text into 'atime' and then the event is used to write the xevent alarm as you see above. I'm not sure I could make it work with separate hour and minute variables very easily!

I use separate variables for hours and minute in my alarm function you can look at this in HeavyMetalXFR

Some screenshots are there

[rbziggy]

Thanks for the pointers. I've realised I can add a couple of fields to my alarm database one for the hours and one for minutes. I'll try this out and see if it works.

[tsjdesign]

Well, I wasn't able to work on my skin again until this weekend, and the new trigger events work perfectly, and are very flexable! I can't wait to have this all up and running!

Thank you so much for you work on this!

Todd