when calling Folder.selectDialog("my header") for the first time - the dialog is opened not in front of other windows (minimized in task bar). but from the second time - it opened as expected.
is there any "focus" command or something that i can use in order to fix this issue ?
Thanks in advance
I think you are calling it the right way.
We are having the same issue.
Seams to be something with Premiere 2021 only.
Still works fine in Premiere 2020.
Our extension runs the same code in PR, AE and PS.
Only in Premiere 2021 this happens.
And like you mentioned only on the first call, the next calls
focuses the dialog properly.
@Bruce Bullis is this a known issue?
Henrique \\ TMMW
Clips Exporter | Thumbs Up | Selector for Premiere Pro
I see it only on Windows, for the first such dialog popped in a given PPro session; after that, they show up in front.
I have the exact same issue - on Windows, the first time after starting Premiere Pro, Folder.selectDialog() displays the dialog behing the Adobe Premiere window, thus not visible to the user.
I have this issue in both Adobe Premier Pro 2021 and 2022. This bug very significantly reduces the user experience, so it would be great to have the bug acknowledged and fixed.
Hi, how did you solve it?
I didn't actually solve this... I changed the logic in the extension a little bit, which meant I didn't have to use Folder.selectDialog() anymore, and hence, I didn't pursue this further.
hm, interesting solution. Via which interface did you replace selectDialog?
No interface at all, I'm afraid. It would of course be nice to come up with a folder picker that doesn't use Folder.selectDialdog, but in this case, we decided it made more sense to write to the currently open prproj file rather to a new one.
Fixed in PPro 23.x.
Thanks, that is great to know!
Hi, I use PPRO build 23.0.0 build 63
Bug still there
yes it still still not working for me either.
Drat! Sorry, perhaps I'm operating in the not-too-distant future.
I've just confirmed that it is double-darn fixed in 23.2 beta, and I'm reasonably sure the fix is in the soon-to-be-released 23.1...