From: Richard B. <bo...@bo...> - 2002-03-06 14:25:21
|
Chris Cannam wrote: > Richard Bown wrote: > > > we should probably get loop setting working > > in the clients as well > > I don't know why it doesn't work. It should, using the lower loop > ruler: I don't think there's any connection currently being made to > cause the loop to be displayed on the ruler, but you should be able > to set a loop (invisibly except on the main canvas) using it. It's most horrible that the looprulers are on the bottom on the clients and yet on the top on the segmentcanvas. BTW I reckon we should either get ghost copy and paste sorted nowish and forget the whole cut and paste pointer idea or work the pointer idea into something we all agree on and like. I do tend to think having two permanent rulers top and bottom is a trifle excessive. Perhaps the cut and paste ruler should just appear when you need to paste? Perhaps we just have both modes and allow the user to choose and hence don't implement ghost copying yet? > But then, it doesn't appear to work using the lower loop ruler on > the segment canvas either. No, you set the loop on the top ruler on the segment canvas using shift+drag no? > > - Non-snapped Segment moving is broken > > Works for me, holding shift while I drag with either the move or > the select tool. Oh yeah, it does work. > It's more or less a star topology, as I said: you want to move > something, ask the document to do it. Nobody should be emitting > setPositionPointer signals except the document and, as a special > case, the loop ruler. That sounds good. R |