Navaron Bracke

That was indeed what I was implying yes.

@greenrobot-team I could try to use `Store.attach()` in the handler that is run on the second FlutterEngine. However, since the second FlutterEngine is created by a background thread (started natively...

@greenrobot-team I had another shot at it and `Store.attach()` did not work. I used the following code: ``` Future _getDatabaseDirectoryPath() async { final dir = await getApplicationDocumentsDirectory(); // The default...

@greenrobot-team In relation to the other issue I had, I'll try to check if the store is open with that static method. Maybe that fixes this issue?

@greenrobot-team I got it working using `Store.isOpen()` and using attach if its already open. I have one more question though: Does the Store emit database updates to each connection? I.e....

@greenrobot-team This does indeed resolve my problem, thank you. And yes I managed to use `Store.isOpen()` to fix the connection issue. Closing as working as intended.

@madrojudi I did it like this: ``` if (Store.isOpen(dbPath)) { _store = Store.attach(getObjectBoxModel(), dbPath); return; } _store = await openStore(directory: dbPath); ``` `_store` is a variable of type `Store?` which...

> I see many sub-issues here for modules and packages, but don't we need a doc for Flutter apps too? Flutter apps are regular iOS/MacOS projects. You can add a...

Since that API is experimental, it is not exposed by `package:web`, per the note in https://github.com/dart-lang/web?tab=readme-ov-file#compatibility You might get away with using an extension / extension type? ```dart import 'dart:js_interop';...

Another one that is quite common in my opinion: `onLoad` events (and friends). In `dart:html` you could do `await element.onLoad.first`. But now you need a Completer + allowInterop on the...