layer ordering is not intuitive

Bug #176473 reported by Matt Jones
4
Affects Status Importance Assigned to Milestone
MeMaker
Confirmed
Wishlist
Unassigned
memaker (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

When you move features to different layers, you have to guess which number position you have moved a feature to.

The the UI should make is easy to determine which layer you are on. We can do this easily, by having the pages in the notebook sorted in the same order as the layers. So for example, if you move the beard to the bottom layer, it will also be on the bottom page in the notebook.

I've got a patch for it in the works. I need to tweak it a little before posting it, as moving the pages messes up a lot of other things.

Revision history for this message
encompass (encompass) wrote :

Yes, me and dennda were talking about that. Could you put that as a blueprint for us. Rather than a bug? Thanks for the idea.

Changed in memaker:
importance: Undecided → Wishlist
encompass (encompass)
Changed in memaker:
status: New → Confirmed
Revision history for this message
Hervé Cauwelier (hcauwelier-deactivatedaccount) wrote :

May I suggest layers be dropped at all. It seems disturbing and not serving an obvious purpose. What is the use case?

Revision history for this message
encompass (encompass) wrote :

It's required to have layers to we know where they need to go... one over the other. For example... layer one is covered partially by layer two. Move layer one over layer too and you sove teh problem. How can we not use layers when these things are considered.

Revision history for this message
wolfger (wolfger) wrote :

Is there a real need to be able to move layers?
For example: the only time I ever changed layers was when a mustache was on a higher layer than an overlapping nose. But I can't imagine anybody ever wanting their nose under their mustache, so that could be solved by permanently layering the nose higher than the facial hair, which should in turn be layered above the mouth, which should be layered above the face.
Is there some case I haven't encountered which requires we retain the ability to change layers (as opposed to having them hard coded)?

Revision history for this message
encompass (encompass) wrote :

I said the same thing myself. But I have found that there are times when you want to move layers. For example... what about some hair that you want to be infront of the glasses. There is a place for it... it's just not as common. Right now they are hard coded, with the option of moving the layers when needed. For example the ears are always to furthest to the back. But what if you want bunny ear's that come from the front.
I totally agree with you in the effect that is greatly simplifies avatar creation... something we want. But it also greatly limits the artistic standing of our theme sets.

Revision history for this message
wolfger (wolfger) wrote :

Adding this to the Ubuntu Memaker package as well, since we are now included with Hardy.

Revision history for this message
encompass (encompass) wrote :

We are going to try to implement this in the 2.0 release.

Changed in memaker:
status: New → Confirmed
Changed in memaker:
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.