The fact that front window actions (found image etc) no longer work either tells me there's a problem beyond user error.
Really? Interesting. Under what circumstances? I've checked for trailing whitespace in the past and it's always been there.
It does indeed and is similar to the method I was using to bring a window whose name doesn't match to the front. However, it's noticeably slower than cycling windows.
As I said before, I can already "do the thing" but what I don't understand is what might be causing these windows to become opaque to KM. I get that Chromium might have these issues, but this is an Apple app for gawd's sake.
Can't get %FrontWindowName% or use any in the front window functions for UA Console either.
Can anyone else confirm this behaviour? Maybe it's a Ventura thing? To be clear, these functions work for most apps, but not for Brave, Console or Logic.
--------------------------------------------------------------------------------
Window Name : Keyboard Maestro Editor — Report Window Properties v2.00
Application : Keyboard Maestro
--------------------------------------------------------------------------------
minimum value : missing value
orientation : missing value
position : {368, 1164}
class : window
accessibility description : missing value
role description : standard window
focused : false
custom title : Keyboard Maestro Editor — Report Window Properties v2.00
size : {1210, 941}
help : missing value
entire contents : {}
enabled : missing value
maximum value : missing value
role : AXWindow
value : missing value
subrole : AXStandardWindow
selected : missing value
name : Keyboard Maestro Editor — Report Window Properties v2.00
description : standard window
--------------------------------------------------------------------------------
Three apps with issues:
Brave Browser
--------------------------------------------------------------------------------
Window Name : Report Properties of the Front Window - Macro Library - Keyboard Maestro Discourse - Brave
Application : Brave Browser
--------------------------------------------------------------------------------
minimum value : missing value
orientation : missing value
position : {417, 111}
class : window
accessibility description : missing value
role description : standard window
focused : false
custom title : Report Properties of the Front Window - Macro Library - Keyboard Maestro Discourse - Brave
size : {1118, 833}
help : missing value
entire contents : {}
enabled : missing value
maximum value : missing value
role : AXWindow
value : missing value
subrole : AXStandardWindow
selected : missing value
name : Report Properties of the Front Window - Macro Library - Keyboard Maestro Discourse - Brave
description : standard window
--------------------------------------------------------------------------------
Logic Pro Plugin UI
--------------------------------------------------------------------------------
Window Name : Guitar
Application : Logic Pro X
--------------------------------------------------------------------------------
minimum value : missing value
orientation : missing value
position : {596, 270}
class : window
accessibility description : missing value
role description : dialog
focused : true
custom title : Guitar
size : {904, 667}
help : missing value
entire contents : {}
enabled : missing value
maximum value : missing value
role : AXWindow
value : missing value
subrole : AXDialog
selected : missing value
name : Guitar
description : dialog
--------------------------------------------------------------------------------
UA Console: Nothing happens when the macro runs; no PWL appears.
Brave is not about the windows – it's about how they've frelled-up the Scripting UI – probably.
I've given up on them (unfortunately), because they broke something utterly vital to my workflows (WhereFrom metadata in downloaded files).
The Logic window shows as a Dialog – Keyboard Maestro doesn't see those as windows.
As for UA Console...
Run this in Script Debugger and see if get a result – if so make sure you get the name right for the next script.
set appNameContains to "ua"
set AppleScript's text item delimiters to linefeed
tell application "System Events"
set nList to name of processes whose name contains appNameContains
if nList ≠ {} then
return nList as text
else
return "Not Found"
end if
end tell
If System Events sees UA Console then run this one, and find out if SEV sees UAC's windows.
tell application "System Events"
tell application process "UA Console"
properties of windows
end tell
end tell
So despite KM being able to get %FrontWindowFrame% and %FrontWindowName%, it can't use that info to act upon a Dialog in the same way as it can a Window?
This reminded me that the app name ("Console") differs from the process name "UA Mixer Engine". Good catch!
Bingo!
UA Mixer Engine
minimum value:missing value
orientation:missing value
position:0
25
class:window
accessibility description:missing value
role description:standard window
focused:true
title:Console: Default*
size:868
1055
help:missing value
entire contents:
enabled:missing value
maximum value:missing value
role:AXWindow
value:missing value
subrole:AXStandardWindow
selected:missing value
name:Console: Default*
description:standard window
