The app should have a single instance to access db. - BoostNote.next

Users can open multiple windows of BoostNote.next app. This behavior is not intended so it could cause several problems because there are no communication measures between the windows.

Is it like the app.requestSingleInstanceLock() implemented on the old BoostNote app?

https://github.com/BoostIO/Boostnote/commit/3c0f20f364a41e651fce168224fb77820fa6d7be

1

Answered Apr 26 '20 at 13:59

jhdcruz

@jhdcruz Yes it is. If you want to try it, please check here for more information! https://www.electronjs.org/docs/api/app#event-second-instance

1

Answered Apr 26 '20 at 16:27

Rokt33r

To apply fix for the web version, we can implement something simple such as saving a instance counter in localStorage, when user close tab or window, the counter should be updated therefore when a new tab or window load the app, we check the counter first before connecting the app. However, I don't think JS can force tab focus so there are 4 solutions that I think we can use:

1

Answered May 01 '20 at 09:22

ZeroX-DG

@ZeroX-DG Good start! I think closing any tabs is too aggressive. Rather than closing the tab, we should just suspend the app.

So I think when a user opens another tab, we should suspend the app in the old screen and show a dialog

Activate App

BoostNote.next is activated in other window(or tab). Once the app is activated in this window, the one in the other window(or tab) will be suspended.

1

Answered May 02 '20 at 18:33

Rokt33r

This issue is not valid anymore since we've discarded the legacy cloud storage from this app. You can open multiple tabs and windows. All data will be synced via WebSocket and server-side events.

1

Answered Aug 24 '21 at 00:55

Rokt33r