I use EF as a background bucket - I rarely open it, in fact, but use the ‘Send To’ quite frequently. If I do so, I always get the “No Library is Open” error message, which is often a source of friction - I have to stop what I’m doing, check EagleFiler, send the item again - and sometimes, I forget to do that.
Would it be possible to better handle this kind of situation? Like, have a background or terminal service that handles the ‘send to’ action separate from the main application (which would complete the ingest on startup, which might be a separate day entirely). I get the ambiguity of having multiple databases as destinations, but if there’s only one in use - or it determines some other kind of default or destaintion - it would make my life a little smoother.