Ok, new BHE version available on server. Just use earlier BHE link.
Testing revealed an earlier bug, which was introduced when framerate option was introduced StartSlideShow command. I have reason to believe that this was the so called "Rika's bug" which caused animations to continue consume processing power even after theyve been stopped. Its now fixed.
I try to keep xPerT syntax forward compatible to extent possible, so users wont need to change their skins when new version is available, however this change for certain technical reasons, might need syntax change later when i introduce planned transitions to slideshows. That is reason why i wont document this feature in xPerT thread, lets keep it "unofficial" for now.
Ok lets get to it... U can add optional specifier of event, to be runned after animation completes, following the fps value, either to loadslideshow variable or StartSlideShow command. Format of event spefier is typical to xPerT:
- Code: Select all
EVENTGROUP>EVENT
so in real life situation it could be:
- Code: Select all
SKIN>overlays>show_fans
well it all depends how u named your events... Heres the whole variable:
- Code: Select all
plugin>xPerT>!instant!loadslideshow>ani>[skin:\buttons\test_f[11...30].png]>runonce>1/20>SKIN>overlays>show_fans
Same principle goes with StartSlideShow command, u add event specifier after fps rating.
Few more points:
* If u just added the command u want to run, restart xlobby cause xPerTs command interpreter refreshes its vocabulary on restart.
* u can use "NOP" as a event specifier, but only in StartSlideShow command. This is useful in rare situations where u have defined event to loadslideshow variable, but later want to re-run animation, without execution of the event defined in variable.
EDIT:
* Allthough framerate is optional in StartSlideShow command, event specifier can only be used within, when framerate is included.