You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The app does not recognise application instances. A macOS feature
Steps to reproduce
This is done using macOS feature for opening multiple instances.
Example to open next instance of the app:
open -n /Applications/FileMaker\ Pro\ 20.app
Expected behavior
I develop a lot in FileMaker databases. Using multiple instances allows me to keep two (or more) separate environments.
Actual behavior
When you open multiple instances of the app, the preview is only showing first main instance window image.
When you click on the preview it switches the focus to the main instance as well.
Screenshots
Attached 2.
Please notice in the dock each instance has separate app icon. My database has different colour depending which server it is running on. Red is Dev green is Live
Environment
macOS version: 14.6.1
App version: 1.2.9
Additional context
Once each instance is running there could be multiple unique windows for each.
The discontinued HyperDock as for example could easily recognise instances, so this should be possible to track.
The text was updated successfully, but these errors were encountered:
Describe the bug
The app does not recognise application instances. A macOS feature
Steps to reproduce
This is done using macOS feature for opening multiple instances.
Example to open next instance of the app:
open -n /Applications/FileMaker\ Pro\ 20.app
Expected behavior
I develop a lot in FileMaker databases. Using multiple instances allows me to keep two (or more) separate environments.
Actual behavior
When you open multiple instances of the app, the preview is only showing first main instance window image.
When you click on the preview it switches the focus to the main instance as well.
Screenshots
Attached 2.
Please notice in the dock each instance has separate app icon. My database has different colour depending which server it is running on. Red is Dev green is Live
Environment
Additional context
Once each instance is running there could be multiple unique windows for each.
The discontinued HyperDock as for example could easily recognise instances, so this should be possible to track.
The text was updated successfully, but these errors were encountered: