https://bugs.documentfoundation.org/show_bug.cgi?id=89612
--- Comment #2 from Zarko Zivanov <zza...@gmail.com> --- > I think I've seen that change too, but I think already quite some time?? > What is your 'reference version' Sorry, I don't know, it was about a year ago. > > I don't know if this is a "blocker" category generally, but for sure is a > > blocker if someone is programming in LibreOffice BASIC. > > It does not block me, but if you're doing piles of just rough stuff that has > lots of errors, it will be annoying indeed.. OK, maybe I was unclear in my bug repport, sorry. You don't need a lots of errors, just one. As I said, if I save (or autosave starts) in the middle of coding, when I just didn't finish all the structures (or if I forgot something as simple as End If), my whole work is lost (since the last successful save), no way to save it, no way to copy it somwhere else, nothing. Recovery after that won't work because saving recovery copy triggers the same behaviour. I'm really not a sloppy programmer, I'm using Calc and its BASIC for work at faculty for 6-7 years, I even contributed to Andrew Pitonyak's macro collection. I just don't understand the logic behind BASIC check while saving. If I'm in the middle of writing some code, when it is still unfinished, it MUST contain syntax errors, until all the structures are written. My instinct is to save often, even unfinished code, and I don't expect that saving my code trigers behaviour that effectively destroys it. The main problem is that "BASIC syntax error" dialog keeps poping up endlessly. It would be OK if LO just checks once, lets me know that there were errors, and saves the current work. I hope that I have explained the problem more accurately. -- 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
