On 2-Feb-09, at 7:17 AM, Nick Guenther wrote: > On Mon, Feb 2, 2009 at 10:03 AM, Sean M. Pappalardo > <[email protected]> wrote: >> >> >> Nick Guenther wrote: >>> Why? What's wrong with a user having to go load a different >>> mapping if >>> it's not working for them? >> >> Where will they do that? >> > > The same place they do now? There's a Load From XML button in trunk > right now, right? > Perhaps I've missed out what the overall plan for mappings is. Are we > killing explicitly choosing a mapping from a file?
The overall plan is to get away with as few buttons as possible, especially because that dialog could get cramped from space pretty easily. I'm not sure exactly which buttons will stay/go right now, so I'm just going to continue coding and make simplifications when the opportunity pops up. Rather than having save/load buttons, the XML will save automatically when you hit OK. Perhaps I should make a QTextEdit box for the mapping name or something so you can rename what the mapping is going to be called. I don't think we want to let users overwrite the stock XML mapping files either. Yeah, so there's a bunch of smaller design issues here, but we'll hopefully be able to address them once we get more functionality laid down. (... but let's not forget about these.) :) Thanks, Albert ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
