2011/12/30 thijs van severen <[email protected]>
> 2011/12/30 thijs van severen <[email protected]>
>
>>
>>
>> 2011/12/29 [email protected] <[email protected]>
>>
>> Am Wed, 28 Dec 2011 23:49:58 +0100
>>> schrieb Sebastian Moors <[email protected]>:
>>>
>>> he ho,
>>> btw, thx thijs for all the work you do and the way you
>>> interact with us in creating procedure.
>>>
>>
>> no probs, nice to see that we can brainstorm a bit about some of the gui
>> items
>>
>> i must say that i'm starting to doubt that these changes should be in the
>> 0.9.6
>> it seems like a 'simple gui change' is taking on bigger proportions and
>> has some serious consequences (not only to the gui)
>>
>> imo it's important to get a gui change exactly right since this is not
>> something you want to do with every release
>> all those in favor of moving this to the 0.9.7 ?
>>
>>
>>> some words to the buttons.
>>> the extra right click selector for velocity, pan and lead lag are only
>>> important if you
>>> use the piano instrument editor. so we can hide them all in normal
>>> pattern editor mode.
>>> this mean we only need the both buttons for default note length edit or
>>> advanced off-note
>>> functionality.
>>
>>
>> agree, but then we need to make sure that these functions are well
>> documented because frankly i had absolutely no idea that some for these
>> functions even existed !
>> that's why i'm in favor of grayed-out buttons (event if that function is
>> not available, at least you can see that it exists), but mauser's argument
>> that it's not possible to keep adding buttons to the gui makes sense i guess
>>
>>
>>> also i think this can be done with only one toggle button. in off
>>> position we edit note length and if toggled you can add off-notes. this
>>> save one button
>>> of space.
>>
>>
>> ok, but then we should have a button that always has 'piano' on it :
>> - when it is not pressed you are working in drum mode.
>> - when it is pressed the button text should still be 'piano' and the view
>> should switch to piano view
>> imo it makes much more sense! am i the only one that thinks this ??
>>
>> in piano editor mode we can show the three extra buttons for vel. lead-lag
>>> and pan. also we can reduce the play midi notes as drumkit or
>>> instrument-piano to one
>>> toggle button. this reduce also space.
>>>
>>
>> an idea :
>> how about removing the lead/lag, L-R and velocity buttons completely and
>> only keeping the dropdown that is located left of the note props window
>> (aka 'bottom window' ;-P)
>> currently this dropdown only has an impact on the notes props window, but
>> why not use this dropdown to also control the RMB function on the pattern
>> editor window ?
>>
>
> if we remove the 3 buttons (as described above) and nly keep the dropdown
> next to the note props window we gain quite a bit of space on the gui + we
> simplify the gui (there is only 1 way to select the note prop that you edit)
> maybe even replace the note props dropdown with buttons ?
> see screenshot in att
>
> grtz
>
guys ? how about this ?
could we just leave out the 'RMB options' completely and only use the
dropdown next to the note props editor ?
that would make sense IMO, i just dont quite know what the RMB function
would have to be when the note prop editor is set to 'notekey' ?
is 'notekey' even relevant ? doesnt the piano editor do what notekey does,
only better ?
grtz
Thijs
>
>
>>
>>
>>>
>>> the same with the destructive recording stuff. we only need the
>>> dropdowns if destructive
>>> record is active. and than at first only one dropdown where you can
>>> change the
>>> destructive recording mode. the second dropdown is only needed if you
>>> choose one of the
>>> latest recording modes called "One rec: 1/64 to One rec 1/1". only here
>>> it make sense to
>>> adjust a pre-delete time.
>>>
>>
>> ok, if we do it for the note props we should also do it for the destr rec
>> dropdowns
>> but Wolke, can you explain what these dropdowns do ? please, please,
>> please ? ;-)
>>
>>
>>> imo, to reduce the interface structure to only available function in
>>> corresponding
>>> editor modes make the interface more easy to understand.
>>>
>>> guess you are right
>> grtz
>> Thijs
>>
>> greetings wolke
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
>>> infrastructure or vast IT resources to deliver seamless, secure access to
>>> virtual desktops. With this all-in-one solution, easily deploy virtual
>>> desktops for less than the cost of PCs and save 60% on VDI infrastructure
>>> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
>>> _______________________________________________
>>> Hydrogen-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
>>>
>>
>>
>>
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Hydrogen-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
