On Friday, February 04, 2011, Ian Gardner wrote: > linked segment functionality out there in the next release. I can be a > lazy fellow at times so I need to start kicking my own backside into > action on this one.
I'm planning the next release for April. > To which end I'd like to propose that by 2 weeks' time (bit optimistic? > maybe more like 3-4 weeks if hit difficulties) I'll have the branch at a > stage where: > > * quick link a segment; Ctrl+Alt+drag > * Paste as Links > * un-linking a segment (where? edit menu? context menu?) (to do) > * all bugs related fixed (to do) > * serialisation > * test (to do) For un-linking a segment... Well, why not just double click on the linked segment to turn them into independent copies? That already works on repeat segments, and the behavior has been around for ages. The one seems to flow naturally into the other. > I figure this will be the minimum but usefully functional linked segment > implementation. I'm considering things like linked segment transposition > are "phase 2" items. That seems quite reasonable. In the course of all that, I really need to root around with transposition more generally. I need to look back through my own tutorials and see what best practices I've recommended, and make sure everything works properly. > What else does this initial implementation need? Colour grouping for > different linked segment groups to give a visual cue as to which segs are > linked and to which others they are linked? That's kind of an interesting question. There are so many possibilities with color that any transformation you do to try to show that "this is related to that, but different" is going to wind up with problems holding onto its meaning. Perhaps use a different fill pattern, or play with opacity instead, depending on how expensive these drawing operations turn out to be. I used a fill pattern variation in the matrix to show tied notes, and that seemed to work out reasonably well, although I'm not generally fond of using fill patterns. > I found it hard to implement the idea of prompting for "copy as copy or > link?" on mouse up when dropping the copied segment, because the command > which either copies or links is already done at the start of the drag > command. You've said this before, but I don't understand how this could be so. I went on a little expedition through the code just now, and I still don't see it. I don't doubt you, but I need a guided tour to see what's going on here, so I can figure out where we are, and how to get there from here. -- D. Michael McIntyre ------------------------------------------------------------------------------ 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
