Apple

Le 23 juin 2016 à 11:07, Yvan KOENIG <email@hidden> a écrit :

Le 22 juin 2016 à 22:10, Deivy Petrescu <email@hidden> a écrit :

On Jun 22, 2016, at 14:48 , Yvan KOENIG <email@hidden> wrote:

Le 22 juin 2016 à 20:25, Christopher Stone <email@hidden> a écrit :

System Events produces the same text as the Finder and is a better option, because you don't disrupt the user's visual-space – and you can easily return him/her to the app they were working in:

---------------------------------------------------
tell application "System Events"
set frontApp to first process whose frontmost is true
activate
display dialog "1212"
set frontmost of frontApp to true
end tell
---------------------------------------------------

--
Best Regards,
Chris

Hello Christopher

Did you look at the events log ?

Here I get :

tell application "System Events"
get process 1 whose frontmost = true
activate
display dialog "1212"
«event ascrgdut»
display dialog "1212"
set frontmost of application process "Script Editor" to true
end tell

which seems to be odd.

Yvan KOENIG running El Capitan 10.11.5 in French (VALLAURIS, France) mercredi 22 juin 2016 20:46:18

Yvan,
not odd, this has been caged a while ago.
This will not give any errors

tell application "System Events"
set frontApp to first process whose frontmost is true
tell me to display dialog "1212"
set frontmost of frontApp to true
end tell

display dialog is an scripting addition, any SA command will give you that error if it is not called by SE.
There was a discussion a very long time ago why this would be good.
Well wasn’t a discussion, it was Apple telling was that this was better.

Deivy Petrescu
email@hidden

Hello

Maybe my memory fails. I remembered that I got a non fatal error with a number when calling an OSAX function in a tell application block but that this feature wasn't striking upon display dialog and other dialog functions.

Yvan KOENIG running El Capitan 10.11.5 in French (VALLAURIS, France) jeudi 23 juin 2016 11:07:51