thijs van severen wrote:
fair enough, but ...
afaik these functions can only be controlled in the pattern editor
with the rmb, right ?
No, you can control them with the left mouse button as well (just click
at some point below/above a note in the note properties view (the thing
that you called 'bottom window')).
btw : the bottom window function also changes to the function you
select in the 'note property' dropdown. this is also a bit confusing,
since you can change the bottom window function to something else
without the 'note property' also changing to that function ('one-way
sync' sort of thingy). so shouldnt the 'note property' and the bottom
window (dont know what it's called?) be 'disconnected' ?I see no real
use in the fact that they are linked, OR the fact that you can
overrule the 'note property' setting using the dropdown left of the
bottom window.
not a big deal, just wondering
There is a slight confusion here :) What i was referring to as the "note
property window" is the same as your "bottom window" (which gets
controlled with the combo box). Can you explain what you meant earlier?
I don't know how to set the lead lag values for example without setting
the combo box to "lead and lag" and then use one mouse button.
What about moving the Note properties icons to the space where the
combo box is at the moment?
do you want to do this because the users are used to the note property
location on the gui?
This might be one point, but not the complete idea.. For me the
separation of the elements is important.
The elements that are used to control the note properties are at the
bottom left, whereas the other control elements are under the pattern
editor. And this space in the bottom left is more or less unused at the
moment. The space in the middle is used
and i think that it is likely that more elements will go into there in
the future.
Then we don't use the space in the middle and we don't mess up the
separation of control elements (pattern editor / note properties
editor).
are you talking about the 'hear' and 'quant' button being moved all
the way to the right?
No no, they are ok.
i was also thinking that this is probably not a good idea and that we
should keep the 'size' and 'res' dropdowns
so the order would then be like this :
size - res - hear - quant - drum/note - note props ('rmb') - input
mode - destructive rec parameters
can you write down the order of the buttons you think is best ?
I pretty much like the current order in your last screenshot - apart
from the fact that the rmb values are appearing there.
The second thing is that it occurs to me that the recording parameters
should be placed at the top of the hydrogen screen, as they are global
parameters. They affect the whole thing, not only the pattern editor.
But no idea where to place them exactly.
one of the reasons why i started thinking about these buttons was to
get rid of the toggle buttons. they are very confusing (and that's
based on my experience with explaining H2 to newbies, it's not just me
being picky)
for example : the piano/drum toggle :
- in drum mode the button is inactive and has 'piano' on it
- when you click it the button is active and it has 'drum' on it, but
the editor is in piano mode
explain *that* to someone that is new to hydrogen !!
there is a similar problem with the stacked/single-pattern mode button
this should also be changed to a 'double toggle button' (or whatever
the correct name is)
Hm, i don't see this as a big problem. If you're totally new to
hydrogen, you could have a look at the tooltip.
I think it says "show piano roll" for the piano icon, which sounds
pretty understandable for me.
a button should have 1 function that is active when the button is
pressed down, inactive when it is not pressed.
just like it is done for the BPM, Mixer, metronome, J trans, J Master
... buttons : simple and absolutely no way to misinterpret the
function state.
For me it is fine to use those button where advanced functions come into
place. Otherwise you end up with a lot of "greyed out" buttons which are
just wasting screen space. And we're seeing that new features are added
with every release, so the number of buttons will increase over time.
But this is a classic user interface design problem.. People are
discussing since ages which way to go. In my opinion those features
(destructive recording, stacked pattern mode) are not self explaining
(IMHO they can't be self-explaining because of their complexity) and are
not understandable without reading some sort of documentation. All
basic functions are implemented as non-toggle buttons (okay, maybe apart
from the piano-roll button).
Regards,
Sebastian
------------------------------------------------------------------------------
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
