Then Flashmode checks in regular intervals (default is 0.5 sec), the length of which is user definable, if its tex document has been modified, and if so, it initiates a save, a pdflatex run, and asks TeXniscope to refresh the front most pdf. Flashmode can be invoked even if a document isn't typeset yet, but beware that is first action will be a typesetting command.
An important feature is that tex syntax errors don't cause any error messages or disruptions of any kind, i.e., the pdf gets never corrupted, at least the pdf viewer is never aware of it, and the last refreshment is always visible; the pdf viewer will never complain.
Thus, the user never gets any error messages; the presence of errors can only be deduced from the pdf window which then doesn't change any more; of course the errors will be reported in the log file and can be looked up.
When the tex document is unmodified, Flashmode stays put in the background with very little CPU load: on my machine the total load would be 200% and the idle Flashmode has about 2.7%, i.e., Flashmode can stay open as long as one wishes without any bad side effects. Only when one wants to run a different tex document in Flashmode, then it has to quit first, or one of the copies has to be started.
While Flashmode is active, the source document can be typeset independently by other scripts or commands, especially other tex tools like bibtex can be run without any interference by Flashmode.
What's new in this version:
- The code of the Flashmode applications has been improved, so that BBEdit will be totally unaffected by the typesetting, regardless of the length of the tex file(s) - this applies only to the applications that are part of 'FlashmodeC', the development of the old Flashmode applications in 'Flashmode' has been stopped.
- The scripts 'sync', 'sync with include only', 'openlog' and 'rm sync' have been improved or a new. 'openlog' can now also be applied when a slave file is front most... See all new features »