On Wed, 2014-08-20 at 11:07 -0500, Jeremiah Benham wrote: > I compiled again from the master branch with an upgraded Cairo. I > believe the problem is now gone. It has indeed :) I tested an hour or so ago, and it seems to be working just fine - with the latest tweaks to the palette shortcuts code in there and working. BTW I don't think I quite realized when I proposed the palettes activation from the keyboard idea that this allows you to define multi-key shortcuts, since you can create a set of labels on palette buttons that issue the commands you want to have shortcuts to, and then access them via p, label, <return>, where "p" is my short cut for the palette activation by keyboard command. As an improvement over ordinary shortcuts you get to see the short cut as you type it and you can edit it if you make a typo. (And - there is no need to have the palette actually visible - if you have it as the last palette in you palettes file, normal if it is a custom palette, then you will get it by default). This idea was motivated by a practical example, the Chord Charts have palette buttons for entering specific chords at the press of a button. But for quick access typing p,m,<return> for a minor chord is better. Where "m" is the label on the insert-minor-chord palette button.
Richard > > Jeremiah > > On Aug 17, 2014 12:08 PM, "Richard Shann" <[email protected]> > wrote: > On Sun, 2014-08-17 at 09:27 -0500, Jeremiah Benham wrote: > > I have rebuilt a snapshot with the mingw branch. If this > fixes the > > problem, I may just need to use a different Cairo version in > master. > This does fix the problem - I did quite a bit of testing with > the 17th > Aug version, no crashes. > Richard > > > > > Jeremiah > > > > On Aug 17, 2014 4:07 AM, "Richard Shann" > <[email protected]> > > wrote: > > On Sun, 2014-08-17 at 08:56 +0100, Richard Shann > wrote: > > > > After rebooting it crashed after hitting a > "m" (I believe > > it was) > > > on > > > > the chord chart pallete when the cursor was > above a note. > > > I suspect this is the > "random-crash-after-a-minute-or-two" > > which I > > > emailed about earlier. The program seems to work > fine, but > > when I > > > tested > > > an earlier build under gdb it spontaneously > crashed in some > > system > > > routine that was possibly connected with > threading. > > > > I've just run the mingw binary from 15th Aug under > gdb. After > > entering > > two or three notes it crashed in the draw routine. > > The where command showed that cairo was deleting a > context > > when a memory > > allocation error occurred. > > It had started up just fine, LilyPond had been run > to typeset > > the > > (empty) score. > > I tried leaving it running for 5 minutes or so after > startup > > and it > > didn't crash (even though the draw routine is being > run in > > order to > > flash the denemo cursor). > > Then I entered 4 notes and it crashed. > > Repeating this half-a-dozen times it always crashed > after 4 to > > 6 notes > > entered, and the crash was always in a cairo routine > called by > > the > > scorearea_draw(). It was nearly always at a > different routine > > in the > > system libraries that cairo calls. > > > > Richard > > > > > > > > > > _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
