I have fixed the LilyPond errors problem. I found that I could not launch a warning dialog though without a mutex locking up. Which brings me to notice that Denemo is now hogging the cpu. It does this even if you have never done anything - just started up the program. Does anyone know about this stuff?? Any tools for finding out where the time is going? As it is typesetting now takes twice as long as LilyPond only gets half the cpu, denemo hogs the rest.
Richard On Sun, 2012-02-12 at 18:21 +0000, Richard Shann wrote: > I don't think we are handling errors in the subprocesses correctly - I > have just seen a case where LilyPond stopped running, when I quit Denemo > it started up running again and completed successfully. > It will have been generating a lot of warnings about note columns > colliding, and I suspect these choked it until Denemo disappeared. > > Richard > _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
