Page 1 of 1

[EOS] How to advance pages and audio separately?

Posted: Tue May 18, 2021 2:24 am
by Corndogville
Hello!

I'm trying to build an estim tease where the viewer can flip through various pics of girls, AND flip through various stim audio files, independent of each other.

Ex: You like a pic and want to keep looking at it, but want to advance audio files until you find the one you like

Ex2: You like the audio file that's playing, but you want to continue to look at more girls.

You can see where I made a mess of trying to experiment with it here, where I ALMOST thought I had a workable solution:

https://milovana.com/eos/editor/50437/e ... e/action/1 (and epage-2)

Part of the problem is I can't get both sets of buttons to appear at the same time, but the even bigger problem, is that since I have it set to continue the audio file playing over multiple pages (which I want), when you decide to hit "Random Stimfile" (which I'd perfer to have Next, Back, and Random for audio as well, ideally) it plays the new stim file just fine, but also continues to play the old one, which is *not* fine. I was hoping it could only play one file at a time and would automatically stop the previous file, haha.

If someone could maybe take a look at what I did, and maybe tell me a better way to do it, that would be super helpful, and I would be very appreciative.

Thanks!!!!

Re: [EOS] How to advance pages and audio separately?

Posted: Tue May 18, 2021 1:45 pm
by fapnip
You can give your sounds an "identifier" (ID).

Say you enter "sound1" as the ID in the Audio play action. You can now access the sound via script and do something like this in an Eval action:

Code: Select all

var mySound = Sound.get('sound1')
if (mySound) {
  mySound.stop()
}
Also, if you use the same ID for multiple sounds, I'm pretty sure any Audio play action will then override a previous audio play action with the same ID.

For more thigs you can do with sounds, see:
https://milovana.com/eos/editor/help/ap ... ence#Sound


For buttons/choice, they are always cleared on every page change, and youcan only have one active Choice at a time. Notification buttons will stick around, but if you need more than a couple buttons, they can take up way too much space.

You'd probably need to use a single Choice action, put all your options in the one action, then use the per-option "visibility" expression (flip it on, and set you expression, like "showButton1 == true" or "showButton1 == false") plus some variables set in an eval to show/hide them ("var showButton1 = true", etc.) depending on what you want.