Hello, 1. I will firstly comment some of your previous comments. 2. I have looked onto your suggestions. - I would prefer the non-merged methods. - there are some problems with some of the methods, see new Test Case - all these methods are inferior for *non-filled objects*3. I will write an expanded comment when I get some free time, detailing a severe limitation of all selection methods (except the method using arrows), and will draw a flow diagram, how to implement the arrows selection
1. COMMENTS Armin Le Grand wrote:
... one selection type won't suffice. Implement at least 2, better 3. Do NOT try to guess what is best. Give the end user the choice and let him select the method he prefers best (and is most suitable for his usage).I have seen no good arguments up to now for multiple selection views, especially when we have suggestions which do not need it.
Up until now, all selections involved 2-3 objects from 3 objects. Real life work may involve substantially more, like 10-20 objects from 10-100 objects. Here it does make a difference and a big one.
There is one *BIG LIMITATION* of all current selection modes and I will detail it in a new post. The arrows selections will offer a very elegant solution, so I will have to expand that when I get a little bit more free time.
However, as I pointed out previously, I may want to accurately move and place a selection near some other object based on some colour characteristics. A border or an overlay, will hinder me in doing this accurately. If I just wanted to copy the selection into a writer document, than probably any method is right.
So You want an extra interaction to move the selection? Normally, a klick and move on the selection is the start of the object manipulation. Users will not remember (believe me) in which mode they are and be unable to manipulate objects.
SHIFT or CTRL+MOUSE CLICK+MOVE (works best in some other programs)
Actually, everything is quite simple. ...guessing :-)This is one of many exceptions required for the code when doing what all the stuff You intend. The visualisation of the selection is a single exception handling.
Really, no guessing. *ANY arbitrary* point will do it OK. When I will have a little free time, I will draw a flow diagram how the code should look like. And it does not involve any guessing. IF arbitrary sound like guessing, than rename it: take point most close to the upper left corner. If that point overlaps/ is overlapped by something else (I will detail it in flow diagram), move a little bit away, until NO overlap anymore. This is no guessing.
Do You really think there are users out there who make a selection, see it's not showing what they want (they will not be pleased, maybe it was their last usage of OOo) and are willing to 'edit' the selection before being able to use it?
YES. Consider working with > 10 objects. They are usually overlapping, that's my experience.
I want now to select some objects. What is the most *easy and fast* method of selecting the objects?Draw one big rectangle around them. But usually this selects *non-wanted* objects, too.
*How do you deselect these unwanted objects?* This is a problem.Having such a method will make things *much, much, much* more easier for Joe-user. [As a hint to my next post, it will deal specifically with this problem and with arrows.]
Kind regards, Leonard Mada
Test-Selection-Methods-4.odg
Description: application/vnd.oasis.opendocument.graphics
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
