https://bugs.freedesktop.org/show_bug.cgi?id=69217
--- Comment #3 from Noel Power <nopo...@novell.com> --- (In reply to comment #2) > (In reply to comment #1) > > when you close what? the IDE? > > When I close the _only_ LibreOffice window, which is the IDE, > and thereby close (exit) the _whole_ of LibreOffice. > > > What to do regarding changes to application basic is somewhat unclear, if > > you have open document(s) ( with modifications ) and you dismiss the ide > > should you only mention that there are unsaved 'application/shared/user' > > macros? should you ignore document macros? or should you just ignore it > > entirely ( like it does now ) Maybe you should defer till you try and > > shutdown the application ( because with the document behaviour you can > > open/close the IDE while the document is opened and your modified but as yet > > unsaved basic is available? > > I don't have a very strong opinion about these alternatives. you need to if you want something sensible > I do have the strong opinion that there *must* be a nag at *some* point. > IMO, "at Application shutdown" is too late. The user's cognitive link > to the Basic code is gone, But.. that's what already happens with a document where you can already close the IDE ( or alternatively switch to application basic ) at any time ( and not get a nag ) > it may be hours later without any visual cue ditto with documents ( and even you might even be saving some unintended basic change(s) ) > My preference would be that the nag for application basic should happen > when closing the IDE, because that's the equivalent of closing a document. If you mean closing the IDE ( when no documents exist ) then it is similar, if you mean closing the IDE normally then... e.g. consider you have changes to application basic but then switch the IDE to view some document basic ( and perhaps even have some other documents open ) and *then* close the IDE, do you nag then ( and only point to application basic having chaged? or enumerate and prompt for each document or... should you perhaps nag when you switch the IDE view from application to document. Either way I think it gets annoying/confusing for the user, there needs to be some reasonable and consistent behaviour but... I have no clue :-) > > I'm nearly neutral about nag for document basic when closing the IDE, > and prefer no nag. > > >> Actual result: > >> Changes are silently saved > > > Well that seems plain wrong, I would expect the changes to be missing if the > > application is exited without saving. > > Yes, me too. But silently lost is also not good, it is a silent data loss. sure but this just a different facet of the same core issue > > > However ( my own expectation ) is that > > prior to exiting any changes made in basic are available ( even if the IDE > > is opened/closed ) and regardless of whether the save button has been > > pressed > > By "available", you mean that the modified version of the code is executed? > My understanding is that this is the case: it is "available" as soon as it > is typed. By available I mean whenever you open/close/open the IDE, the application basic ( complete with any unsaved changes ) is what you get -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
