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
Sometimes a folder will become unresponsive -- cannot be opened, or if open, cannot be closed. In the latter case it's also not possible to interact with the individual connections in the folder. The connections can still be used via the "All Connections" dialog.
This is "fixed" by exiting/restarting Antares, but the folders and un-foldered connections don't always reappear in the same top-to-bottom order that they had before exiting.
To Reproduce
Unable to reproduce by any particular sequence. Happens once in a very long while after leaving Antares open for several days.
It might be related to using the "Move To >" menu to put a new connection into a folder, because it seems as though the last folder that got into this state was one into which I had previously moved a couple of connections.
The text was updated successfully, but these errors were encountered:
Regarding the main topic of this issue, I am implementing an in-app console where to print all error messages from the application.
The goal is to make it easier to report problems and resolve them, even in cases like this where it is almost impossible to replicate the problem.
Antares 0.7.23 MacOS
Sometimes a folder will become unresponsive -- cannot be opened, or if open, cannot be closed. In the latter case it's also not possible to interact with the individual connections in the folder. The connections can still be used via the "All Connections" dialog.
This is "fixed" by exiting/restarting Antares, but the folders and un-foldered connections don't always reappear in the same top-to-bottom order that they had before exiting.
To Reproduce
Unable to reproduce by any particular sequence. Happens once in a very long while after leaving Antares open for several days.
It might be related to using the "Move To >" menu to put a new connection into a folder, because it seems as though the last folder that got into this state was one into which I had previously moved a couple of connections.
The text was updated successfully, but these errors were encountered: