A quick reply to Dan Barlow's email and then a reply to Pieter below: Dan: Good suggestions there, but there's not enough room to write that. Maybe I can put that in the tooltip or something. Good point about the "auto" thing too. :)
On 22-Oct-08, at 1:14 AM, Pieter Palmers wrote: > somewhat related: > > How difficult would it be to implement multiple queue points? If they > are saved/restored that can be very interesting, e.g. for set > preparation and/or looping. > > Greets, > > Pieter Having a custom number of cue points would be very hard, but having a max of like 4 cue points is more achievable. Changes that would need to be made: - Change TrackInfoObject to save the four cue points. - Change the GUI to allow the user to save and jump to multiple points in a non-confusing way. Figuring out a good UI for this is probably the hard part. - Change enginebuffercue.cpp to deal with multiple cue points. - Think about how MIDI controllers should deal with this. Most only have a single CUE button. How do CDJ's deal with multiple cue points? Multiple cue points isn't quite a slam dunk. There's a few issues that we'd need to put some thought into before trying to implement it, at least. Thanks, Albert ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
