Poser Dialog Mockup

[ghost]

I made a mockup of what could be put into the poser dialog. Some features are taken and proven from SpoilerAL, while others were made up in the spot.

[AA2Hackanon]

• noticeably missing are the rotation sliders for different bones/frames.
• i'm not sure if i will be able to find the dimmed eyes/tears stuff. but i guess we'll see
• i don't think a freeze checkbox will be necessary; its kinda hard to implement, but its easy to archive the same effect with just pose and frame selection
• also, what is a pose list?

apart from that, looks like a plan. specifically the rotation sliders really need a place though. or a new interface in general.

[ghost]

A pose list is a list of human readable pose names. For example, the current SpoilerAL release has the following format for naming poses:
#Pose Descriptive Pose Name

[ghost]

Something I'm working on.

[ghost]

Slider mods, loading and saving working. Yay.

[linkanon]

Good job.
For usability I suggest making several tabs for the bones like L/H hand, head/neck, legs and so on. Alternatively there could be a drop-down with all these categories and selecting it will populate the bones list. As it is in test8 scrolling through all the bones is a major pain

[ghost]

I want to keep the UI compact so I attempted to make one without too much cluttering (but mostly because tab handling in win32 is something that I still don't get).

The bones are abit unmanageable like this. I'm thinking of making a two-tab list for L/R bones. Picking the left or right tab will show and select bones of each side. Central/non-lateral bones would show on both tabs.

[ghost]

Work branch

[linkanon]

instead of two lists with mostly the same bones you could adapt the same idea with tabs to two lists.
It'll look like:
|Body part||Bone||Operation||Axis|
Body part will list items like neck, left arm, left hand, right arm, right hand, etc.
Bone will list items like shoulder, arm, elbow, forearm, all the finger bones, etc.
Operation and Axis are fine

Selecting an item in Body part would refresh the Bone list. This implementation is actually better than with tabs imo. Not sure how to go about the bone lists and their categories. Probably best to list them in poserframes.txt

[ghost]

I'm liking that. It makes good use of vertical and horizontal space. Let's see if we're seeing it the same way:

Each of
|Body part||Bone||Operation||Axis|
would be list boxes filled with different categories

For the poserframes.txt file I'm thinking of the following structure:

desc Friendly Frame Description
bone_category bone_name allowed_operations allowed_axis

where desc is optional. if omitted the bone name is used instead. bone_category groups bones and allowed_operations and allowed_axis list keywords that restrict bone modification.

[linkanon]

Yes, Bone list would have a subset of the list we have right now, Body part would have some more general categories(i.e. body parts) each set of bones belongs to.

For keywords I suggest something simple like SRT, SR for operations, XYZ, XZ for axes (Though I doubt limiting axes would ever come in handy)

Don't like having desc on a separate line. Ideally would be to keep a single line per entry. Maybe move it to the end of the entry like

bone_category bone_name allowed_operations allowed_axis desc

This way the optional field is the last one so there's no need for empty columns in front of the entry. Only issue I see with this is that the names won't be nicely lined up because of the frame names. Also i like calling it name in this case since it's not a full-blown description but a simple 1-3 word human-readable alias.

[linkanon]

Made a mock-up of hypothetical props controls. The idea is to be able to load an arbitrary .xx and control its SRT.

Props list could be saved as a list of filepaths and loaded together with the pose itself.
No physics/adjustments necessary in case the hair is loaded.

[ghost]

I'd keep the bones/frames list for props as well. You may make custom a custom poserframes.txt file for them too.

Also, it seems you are thinking of saving scenes as opposed to just a single pose. I thought of that too but that would need of more UI work. Maybe we could add "Save pose" & "load pose" buttons below the Categories list for single pose saving/restoring, a reset pose button as well in the row below. Then the Save, Load and Reset buttons at the bottom would work for scenes.

The Props UI needs a bit more spacing away from the Facial UI. I suggest to place the top (the static labels) at (Blush edit)(top) + (Blush edit)(height) + 12 and move everything else accordingly.

[linkanon]

Having the same list would work now that I think about it. We can have a Props category (instead of the Rooms we currently have. Rooms can be treated as props) which will contain all the props we load(we can't list them in poserframes.txt because we select them during runtime)

I'm not thinking of saving the whole scene but I suggest attaching the props to the pose as well. One example could be to add a cigarette prop to the smoking pose. If there's no cigarette model the character would just smoke air cigars. Another example is the vanilla evaluating condom pose.

If we make props a subset of posing(the Props category) we can keep the same exact UI we currently have(maybe with the additional Add .../Remove buttons for props). Save/Load would simply save/load the prop filepaths(can be relative to the overrides) and their SRTs as well.

A bit offtopic but all the unimplemented features controls should be disabled until implemented to pre-empt the questions in the thread. Reset, Pick from pose list and Freeze don't work now.

[ghost]

I tried to figure out a way to get the mouse cursor to appear when Always on top is checked without success.
geneishouko/AA2Unlimited@always_on_top...geneishouko:mouse_events