Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)
(Mac OS Mojave (current), Frescobaldi 3.1 from dmg) An anomaly noted: document conversion from 2.19.2 to 2.19.83 fails with the following error message reported: > ImportError: Bad magic number in > /Applications/Frescobaldi.app/Contents/Resources/site.pyc > > > The document has not been changed. > Stan
Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)
I confirm same behavior. J. On 12/28/19 13:11, Stanton Sanderson wrote: > (Mac OS Mojave (current), Frescobaldi 3.1 from dmg) > > An anomaly noted: document conversion from 2.19.2 to 2.19.83 fails with the > following error message reported: > >> ImportError: Bad magic number in >> /Applications/Frescobaldi.app/Contents/Resources/site.pyc >> >> >> The document has not been changed. >> > Stan -- University of Hawaii, Maui College / Mobile 760.840.8660
Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)
> On Dec 28, 2019, at 3:23 PM, John Helly wrote: > > I confirm same behavior. > J. > > On 12/28/19 13:11, Stanton Sanderson wrote: >> (Mac OS Mojave (current), Frescobaldi 3.1 from dmg) Another behavior noted (change from previous versions): the new pdf generated when editing an existing file does not replace the old pdf.
Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)
On 12/28/19 13:11, Stanton Sanderson wrote: > An anomaly noted: document conversion from 2.19.2 to 2.19.83 fails with the > following error message reported: >> ImportError: Bad magic number in >> /Applications/Frescobaldi.app/Contents/Resources/site.pyc Il giorno sab 28 dic 2019 alle ore 22:24 John Helly ha scritto: > I confirm same behavior. I can reproduce the issue. Issue opened at https://github.com/frescobaldi/frescobaldi/issues/1232. I will investigate it. Best wishes. Davide
Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)
Il giorno sab 28 dic 2019 alle ore 22:30 Stanton Sanderson ha scritto: > Another behavior noted (change from previous versions): the new pdf generated > when editing an existing file does not replace the old pdf. I cannot reproduce this. If I change an existing document, save it and compile it, the new PDF replaces the old one. If I change an existing document, DO NOT save it and compile it, the viewer shows the new PDF, which is saved in a temporary location, and the old PDF is not replaced. This is the usual behaviour of Frescobaldi. It would be a bug if after changing, saving and compiling an existing document the new PDF did not replace the old one. What is the behaviour you are observing?
Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)
Stan > On Dec 28, 2019, at 3:45 PM, Davide Liessi wrote: > > What is the behaviour you are observing? Away from my machine. Will report ASAP.
Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)
> On Dec 28, 2019, at 5:15 PM, Stanton Sanderson >> >> What is the behaviour you are observing? > > Away from my machine. Will report ASAP. Davide, As you stated, the edited file is temporary and must be saved first to replace an existing pdf. Sorry for the noise. Stan
