From: Tim E. R. <ter...@ro...> - 2011-06-06 00:01:13
|
On June 5, 2011 07:37:34 pm Tim E. Real wrote: > On June 5, 2011 06:16:43 pm Florian Jung wrote: > > Am 06.06.2011 00:14, schrieb Geoff Beasley: > > > On 06/06/2011 02:55 AM, Tim E. Real wrote: > > >> However I must say again, I am leaning towards*not* erasing the > > >> notes, keeping them and drawing the right edge jagged or whatever, so > > >> that the user*clearly* knows that there are notes beyond the end, and > > >> let*him* decide what to do with them. Trust me, this would be OK. > > > > > > this makes sense to me ;) > > > > hm, okay, agreed. > > you might want to implement the "jagged end" thingy in experimental > > i'll write the code for resizing all clone parts, and for not erasing > > notes when resizing a non-clone > > after that, i'll see if i can change the file loading; otherwise i'll > > ask for help > > Aw, I dunno, let's try it. Maybe I'm wrong, but it seems like a neat idea. > After all, somebody must have had a plan when they wrote the > original code - it didn't erase, until I told it to! > > How about let's at least for now try to draw the jagged edge > for any part which has notes past the end (since that condition > exists right now), get it looking nice. That's already challenging. > > At least then we'll have that in place first. > This /could/ go into the trunk right away - no harm done if so, right? > > Then, I figure it should be easy (?) to flip back and forth in the part > resizing code between erasing or not erasing while we decide what > works best? Is it not just one or two sections we are concerned with? > > Tim. > > > greetings > > flo Oh yeah... One question: Why do you still want to erase the notes for clones but not for non-clones? Am I missing a crucial point? Thanks. Tim. |