How should existing AppleScript conditions be handled in 7.4

How should deprecated AppleScript Conditions be evaulated in Indigo 7.4+?

Poll ended at Thu Sep 12, 2019 11:31 am




1
10

Posted on
Thu Aug 29, 2019 11:31 am
jay (support) offline
Site Admin
User avatar
Posts: 15693
Joined: Mar 19, 2008
Location: Austin, Texas

How should existing AppleScript conditions be handled in 7.4

We're deciding how best to handle the case where there is an AppleScript conditional (AppleScript conditionals will be deprecated as part of our migration to a 64-bit server for Catalina). There are two fundamental options about how to evaluate:

  1. Have the conditional automatically return True so that the actions will always execute.
  2. Have the conditional automatically return False so the actions will never execute.

Note that we're not discussing how to handle the field itself, or anything about Python conditions. We're just talking about how we evaluate existing AppleScript conditions. So, vote and we'll take the results under advisement.

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Fri Aug 30, 2019 12:25 am
howartp offline
Posts: 3668
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: How should existing AppleScript conditions be handled in

Is it possible to edit the Option value of your poll - Safari on iOS wont let me click the radio button.

Image

Possibly a wrapping issue? The label can remain full text, just wrap the value?


Sent from my iPhone using Tapatalk Pro

Posted on
Fri Aug 30, 2019 9:48 am
jay (support) offline
Site Admin
User avatar
Posts: 15693
Joined: Mar 19, 2008
Location: Austin, Texas

Re: How should existing AppleScript conditions be handled in

howartp wrote:
Possibly a wrapping issue? The label can remain full text, just wrap the value?


Yeah, phpbb styles are super hard to get fully/completely right. Just make your window bigger... :P

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Fri Aug 30, 2019 10:10 am
howartp offline
Posts: 3668
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: How should existing AppleScript conditions be handled in

Making window bigger doesn’t help the button start working!


Sent from my iPhone using Tapatalk Pro

Posted on
Fri Aug 30, 2019 10:24 am
jay (support) offline
Site Admin
User avatar
Posts: 15693
Joined: Mar 19, 2008
Location: Austin, Texas

Re: How should existing AppleScript conditions be handled in

howartp wrote:
Making window bigger doesn’t help the button start working!


I'm not seeing any issues with the button, and now I see the button doesn't show up. There's supposed to be a green Submit Vote button under the choices.

I suspect your issue is that you're not logged in...

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Fri Aug 30, 2019 11:06 am
howartp offline
Posts: 3668
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: How should existing AppleScript conditions be handled in

jay (support) wrote:
I suspect your issue is that you're not logged in...

Well you’re just fussy...!


Sent from my iPhone using Tapatalk Pro

Posted on
Fri Aug 30, 2019 5:49 pm
mundmc offline
User avatar
Posts: 556
Joined: Sep 14, 2012

Re: How should existing AppleScript conditions be handled in

Web view (leaving Tapatalk) and logging in let me vote.
#voterawareness

Posted on
Mon Sep 30, 2019 4:23 pm
matt (support) offline
Site Admin
User avatar
Posts: 19334
Joined: Jan 27, 2003
Location: Texas

Re: How should existing AppleScript conditions be handled in

Just wanted to wrap up this thread now that 7.4 is released and explain the implemented behavior: AppleScript conditionals are commented out and converted into Python (they have to be hand corrected/ported to Python) and will evaluate as False until that correction is made. That is, Trigger and Schedules that have embedded AppleScript conditional will by default not run in Indigo 7.4 until they are converted (by the user).

Image

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 0 guests

cron