Le mercredi 13 juillet 2016, 09:02:14 Ted Felix a écrit : > I've been cleaning up TrackParameterBox and I'm looking right now at > the "Preset" field in the "Create segments with" section. This field is > enabled/disabled to indicate changes have been made. However, on my > system, the difference between enabled and disabled is very subtle. So, > I was thinking that we should do something different.
It's so subtle that I never noticed this field may be enabled or disabled. > > Here are my thoughts. > > 1. Rename this field from "Preset" to "Label". After all, it's used > to set the Segment label. > > 2. Let the user edit this field so they can pick whatever they want > for the Segment labels. I was taken this field as the name of the preset rather than the preset of the segment label. When there is no preset, the segment label comes from the instrument/program. Is a preset of the label really useful ? If there are several segments on the track, the user probably wants a different label for each segment. If there is only one segment, directly writing its label is as simple as writing a preset value first. > > 3. Save this field to the .rg file so the user can depend on it. > (Currently it is lost across loads.) Indeed this field is lost although the preset values are saved. It would be fine to save it to remember what these values are. > > 4. Replace it with the name of the preset when a preset is loaded with > the Load button. (This is what it does already, so no change.) > > 5. If the user changes any of the other fields (e.g. pitch), leave the > label field alone. It's up to the user to adjust as needed. > (Currently we disable the field to give it a different appearance. > Too subtle for me.) I don't see the point to change the name of an existing preset. This field might be editable only after the user changed some preset value. Moreover the original preset name should be automatically altered (postfixed ?) as soon as the change is done. > > This gives the user more control over the field and to me makes this > a more useful feature. Before I invest the time, is there anything I'm > missing? After a preset is loaded there is currently no easy way to remove it and come back to the default values. The Clef and transpose parameters are stored in the created segment and memorized with it. The lowest and highest pitches are stored in the segment, but not memorized (they are lost when the file is saved then restored). Currently these parameters are only usable in the session where the segment is created. If a segment is created on one track then moved on another track, its lowest and highest pitches are kept from its creation track, which is probably not that the users want (these pitches are related to the instrument which comes from the track). The lowest/highest playable pitch attributes might be removed from the segment and the same already existing attributes from the track used instead. I wonder about the transpose parameter which is frequently related to the instrument. Should not it be a track parameter rather a segment one ? Or maybe the final transpose should be the sum of two parameters, one from the track and one from the segment ? Yves ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
