https://bugs.freedesktop.org/show_bug.cgi?id=69217
--- Comment #4 from Lionel Elie Mamane <[email protected]> --- (In reply to comment #3) > (In reply to comment #2) >> (In reply to comment #1) >>> What to do regarding changes to application basic is somewhat unclear (...) >> 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 ) Yes, but there is still a window that shows the document, so there is a continuous link. The basic code is not *shown*, but that's similar to a change to an unused Writer document style: no effect on screen, but still it is a change to the document and the document is on an existing window. >> 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 Yes. > ( and only point to application basic having chaged? or > enumerate and prompt for each document Enumerate and prompt for each. > or... should you perhaps nag when you > switch the IDE view from application to document. The Basic IDE has this "weakness" or let's say "difference to the rest of LibreOffice" that it uses a unique window, and thus this window switches one module to the other. For better consistency, we could change the IDE to have a window per opened module. By "window", I don't necessarily mean "full top-level OS-level window", but it could be a "subwindow", that is a window that is shown within the IDE top-level window. But that's a bigger work. In the meantime, we have to (imperfectly) map the concepts of the usual "one window per document unit" world to the IDE's unique window. It could make sense to nag for save when switching from one module (or dialog) to another, by mapping that action to "close window, open new window" in the one-window-per-unit world. But IMO, this would be too impractical for the user. > 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 think my preference is the most reasonable and consistent that can be achieved with the current "IDE is exactly one window". -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
