Need a way to call tomo.Stop when all windows have closed #5

New Issue

2024-08-13T01:04:42-06:00

sashakoshka commented

2024-08-13 01:04:42 -06:00

Currently, the pattern is for the application to count how many windows are open. If not done exactly right we get zombie processes. Behaviors of the Application interfaces must return a Window that can be counted by Nasin, which will then call tomo.Stop once no windows are open.

sashakoshka commented

2024-08-16 14:27:51 -06:00

7da00e990e

7da00e990e2ca162c160730357d7fb380c21d0c7

sashakoshka closed this issue

2024-08-16 14:27:51 -06:00

sashakoshka reopened this issue

2024-08-19 01:56:42 -06:00

sashakoshka commented

2024-08-19 01:57:16 -06:00

The current solution is actually bad. What if the application wants to open another window (like middle clicking in a file manager)?

sashakoshka commented

2024-08-19 02:07:09 -06:00

There needs to be some sort of nasin.Manage function that takes in a window, and will return a cookie that unmanages it. The function will increment the window counter when called, and decrement it when the window is closed, then checking if it is zero to call tomo.Stop if need be.

Perhaps instead of accepting a window, it could accept a Manageable interface with an OnClose behavior. This would allow applications to do things like keep a background service running to receive notifications or something like that.

There needs to be some sort of nasin.Manage function that takes in a window, and will return a cookie that unmanages it. The function will increment the window counter when called, and decrement it when the window is closed, then checking if it is zero to call tomo.Stop if need be. Perhaps instead of accepting a window, it could accept a Manageable interface with an OnClose behavior. This would allow applications to do things like keep a background service running to receive notifications or something like that.

sashakoshka commented

2024-08-19 20:51:40 -06:00