Close topic without save prompt?

[Centauri27]

Is there a way to have Flare always save a topic when I close it? Sounds like a simple request, but I can't find this anywhere.

I know that if you enable Auto Save and the topic has been automatically saved, you will not be prompted again to save when you close. But I am making a large number of minor changes to many topics and I'm closing the topic before auto save has a chance to kick in. I'd like Flare to quit bugging me when I close the topic.

Ideas?

Thanks.
Carl

[GregStenhouse]

You can always just leave the file open after your change, open the next topic etc. Then after a while click File>Save All and then Window>Close All Documents. That might save a bit of time?

[KevinDAmery]

Is there a way to have Flare always save a topic when I close it? Sounds like a simple request, but I can't find this anywhere.

I know that if you enable Auto Save and the topic has been automatically saved, you will not be prompted again to save when you close. But I am making a large number of minor changes to many topics and I'm closing the topic before auto save has a chance to kick in. I'd like Flare to quit bugging me when I close the topic.

Ideas?

Thanks.
Carl

I'd be careful what you wish for: if you enabled something like that, what would you do if you realized you'd made the change in the wrong topic? Specifically, how could you exit without saving changes if you needed to?

[LTinker68]

Is there a way to have Flare always save a topic when I close it?... I'd like Flare to quit bugging me when I close the topic.

To be honest, I'm surprised you're not a compulsive saver like me. I've had too many occasions where a program has crashed (in general, not specifically Flare), or the computer has locked up, or we've lost power, all of which has resulted in work that was lost since the last save. So I do Ctrl + S every few minutes and just before I switch from one topic to another. That way any work lost is minimal or I haven't lost any work at all (assuming the crash/failure didn't corrupt the file).

[Centauri27]

Well, I am a bit of a compulsive saver...and I'm a bit of a compulsive resource-monitoring fanatic too. I realize that I can leave everything open, then do a mass save at the end, and I do have auto save turned on and I occasionally do a manual "save all" as well. But experience has taught me that it's never a great idea to have many files/topics open at once--Murphy's Law will get you eventually. Another reason I don't want to leave everything open: there are a handful of topics that I want to keep open because they are edited repeatedly, while there are others that I need to open, make one change, then close again. If I leave all these open, it just clutters up the Windows menu, making it harder to find my topics.

In the end, I just want Flare to do what RoboHelp has always done: save the topic when you close it. This should be a ideally be a Preferences setting where you can turn this automatic saving on/off. I'm surprised Flare doesn't have this. Perhaps I should submit an enhancement request?

Thanks.
Carl

[LTinker68]

In the end, I just want Flare to do what RoboHelp has always done: save the topic when you close it. This should be a ideally be a Preferences setting where you can turn this automatic saving on/off. I'm surprised Flare doesn't have this. Perhaps I should submit an enhancement request?

Yep. Submit one at http://www.madcapsoftware.com/bugs/submit.aspx.

I tend to leave the TOC and stylesheet tabs open all the time and just save them after I make modifications. First, because I tend to edit them a lot, and second, because it's annoying to be working on a topic and have to switch to the Project Organizer pane, expand the TOC, open the TOC, make the edits, save, close, then go back to the Content Explorer to select the next document. The stylesheet isn't much better since you have to go down three levels to get to it, although I tend to do that a lot anyway just because I often directly modify the stylesheet page, since the Stylesheet Editor still isn't as good as it could be.

[Centauri27]

The stylesheet isn't much better since you have to go down three levels to get to it, although I tend to do that a lot anyway just because I often directly modify the stylesheet page, since the Stylesheet Editor still isn't as good as it could be.

Couldn't you just use the "Open Master Stylesheet" button right on the main GUI?

I've submitted an enhancement request--let's hope this seemingly simple feature gets added soon!

Thanks for all your suggestions.

Carl

[LTinker68]

The stylesheet isn't much better since you have to go down three levels to get to it, although I tend to do that a lot anyway just because I often directly modify the stylesheet page, since the Stylesheet Editor still isn't as good as it could be.

Couldn't you just use the "Open Master Stylesheet" button right on the main GUI?

I don't think that button was always there, but even so I think it just opens the Stylesheet Editor for the main topic stylesheet. I'm talking about opening the stylesheet file in the Internal Text Editor so that I can edit the code directly instead of using the Stylesheet Editor. The Stylesheet Editor doesn't let you do things like create complex selectors or add tags to control tags or classes of tags that aren't normally available in the Stylesheet Editor.