Hello Michael,
I'm okay with the disable of that dialog box.
But I still am experiencing a crash on several variations of a theme.
* create a segment
* put four or more of the same pitch in it (in notation editor) so that they
bump up against the end of the segment
* collapse the notes and then crash.
It is crashing when it reaches the last of the original candidates (if there
were 4 notes, [0-3 in the index]) it crashes when it performs:
if (s.findSingle(e) == s.end())
in CollapseNoteCommand::modifySegment()
I've traced this to the the call in Segment::findSingle(Event *e)
std::pair<iterator, iterator> interval = equal_range(e);
this STL command is breaking and breaking because our Event::operator<(const
Event &a, const Event &b) is accessing the reference to a pointer we already
deleted.
I know "e" is not going to be found at this typically behaves well in this
situation. In this case "e" was erased from the segment in
CollapseNoteAggressively. But this item is still in our list in
CollapseNoteCommand and needs to be checked.
....
I'll get back to this in a bit.
Sincerely,
Julie S.
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
