Milovana.com

amythx wrote: Tue Jan 29, 2019 1:18 am I even tried to evaluate 1 === 1; in order to get the IF action to fire.

Don't place a ; at the end of the line where you need an expression like with the if action.
something; is a statement in javascript, so it does not result in a value.
If that does not solve your problem, export the script and link it here, and I'll take a look.

seraph0x wrote: Tue Jan 29, 2019 7:09 am

Polvish wrote: Fri Jan 25, 2019 2:39 amAlso if I could throw a suggestion out there, I would say add getPage to the interpreter as well such we could supply the goto function with whichever page we wish(mostly random pages based on dice rolls and such)!

Feature added.

Great feature, but it seems you broke random patterns in gotos in the validator implementing it.
For a pattern like "somepage*" I now get:

Does not match the regex pattern ^[a-zA-Z0-9-]+$
Does not match the regex pattern ^\$.*$
Failed to match at least one schema

Looks like the $ in the beginning is for javascript variables?
And the other pattern does not include the "*" anymore.

@seraph0x hey and thank you for your work ! I have a suggestion for eos, is it possible that when we click the eval button when we have selected a word it uses this word as the tag ? Since even if we put another word it replaces it with the tag anyway.

I am having an issue with all EOS teases, across all browsers, Chrome, Firefox, and Edge.
In order to see the text, I have to switch to full screen.

I know it was working last week, so I don't know if something has changed.

thongs911 wrote: Tue Jan 29, 2019 1:43 pm I am having an issue with all EOS teases, across all browsers, Chrome, Firefox, and Edge.
In order to see the text, I have to switch to full screen.

I know it was working last week, so I don't know if something has changed.

I'm having the same problem. They were working fine on 1/27 for me, but late evening (CST) 1/28 the need for full screen started. I'm using Firefox

thongs911 wrote: Tue Jan 29, 2019 1:43 pm I am having an issue with all EOS teases, across all browsers, Chrome, Firefox, and Edge.
In order to see the text, I have to switch to full screen.

I know it was working last week, so I don't know if something has changed.

Hm, works fine for me in Chrome 71.
But with Firefox I can confirm the issue. Looks like the size of the complete window or even screen is used, instead of the size of the visible area.

@seraph0x I checked the firefox "fullscreen bug", and it looks like a `max-height: 100%` on the `.eosContainer` and a `max-height: calc(100% - 48px);` on the css of `Viewport` module can solve the issue and it dos not seems to break anything in chrome either.

seraph0x wrote: Tue Jan 29, 2019 7:09 am

Polvish wrote: Fri Jan 25, 2019 2:39 amAlso if I could throw a suggestion out there, I would say add getPage to the interpreter as well such we could supply the goto function with whichever page we wish(mostly random pages based on dice rolls and such)!

Feature added. You can now use dynamically generated Goto targets. One caveat is that because the target pages are dynamically generated, the viewer cannot preload them. So the user may get a delay with this type of goto. Use sparingly.

I saw that it introduced issues, just let me know if you decide to bring it back! Also another request would be the ability to have gifs as a media type! Could a more to a tease!

Polvish wrote: Wed Jan 30, 2019 1:02 am

seraph0x wrote: Tue Jan 29, 2019 7:09 am

Polvish wrote: Fri Jan 25, 2019 2:39 amAlso if I could throw a suggestion out there, I would say add getPage to the interpreter as well such we could supply the goto function with whichever page we wish(mostly random pages based on dice rolls and such)!

Feature added. You can now use dynamically generated Goto targets. One caveat is that because the target pages are dynamically generated, the viewer cannot preload them. So the user may get a delay with this type of goto. Use sparingly.

I saw that it introduced issues, just let me know if you decide to bring it back! Also another request would be the ability to have gifs as a media type! Could add more to a tease!

kerkersklave wrote: Tue Jan 29, 2019 12:55 pm

amythx wrote: Tue Jan 29, 2019 1:18 am I even tried to evaluate 1 === 1; in order to get the IF action to fire.

Don't place a ; at the end of the line where you need an expression like with the if action.
something; is a statement in javascript, so it does not result in a value.
If that does not solve your problem, export the script and link it here, and I'll take a look.

Duh;

Question #2: How to have a button that doesn't wait for input? E.g. a basic edge button to stop in the middle of stroking to sound.

Thanks for the help Kerkerslave!

amythx wrote: Wed Jan 30, 2019 1:57 am Question #2: How to have a button that doesn't wait for input? E.g. a basic edge button to stop in the middle of stroking to sound.

Buttons come only with choice actions and they are part of the text flow, so one has to make a choice before the next say action can be executed.

What you can do, is, have an asynchronous timer (look at the options of timers).
They do not stop the main flow of the page but interrupt it once the time is up.
So what I have done is have a Say-Action with an command like "Edge!" followed by an asynchronous timer that goes to a new page, followed by a choice-action with an edge-button.

(There may actually still be a but that buttons stay live when a asynchronous timer triggers a say action, but I would not build on that, because I beleive it is a bug and will go away).

amythx wrote: Wed Jan 30, 2019 1:57 am Thanks for the help Kerkerslave!

I'm also getting validation errors.

pages.p4[11].goto.target Does not match the regex pattern ^[a-zA-Z0-9-]+$
pages.p4[11].goto.target Does not match the regex pattern ^\$.*$
pages.p4[11].goto.target Failed to match at least one schema

When I click on the error, it takes me to my goto action which is:

Goto: p*

My pages are named p1, p2, p3, etc. so that it will go to a random page. Everything works in preview.

Ghingis wrote: Tue Jan 29, 2019 9:11 pm @seraph0x I checked the firefox "fullscreen bug", and it looks like a `max-height: 100%` on the `.eosContainer` and a `max-height: calc(100% - 48px);` on the css of `Viewport` module can solve the issue and it dos not seems to break anything in chrome either.

Thanks for the tip and sorry everyone for the regression bug, it should be fixed again now!

Revuin wrote: Wed Jan 30, 2019 3:55 am I'm also getting validation errors.

pages.p4[11].goto.target Does not match the regex pattern ^[a-zA-Z0-9-]+$
pages.p4[11].goto.target Does not match the regex pattern ^\$.*$
pages.p4[11].goto.target Failed to match at least one schema

Fixed.

This looks awesome. I just want to add a feature request for future versions of EOS:
- Could we please have an option to set teases 'open source' or some such - meaning that other people would be able to view and/or copy the tease and use them as basis for modifications? I assume some people wouldn't mind sharing their teases in this way, while others prefer keeping their ideas their own. I think this could potentially lead to a lot more and better teases being made.

Is it possible to add a varaible into a goto ?