Ditto on the request for mousewheel controlling parameter dials! 

Quote - The only thing I would really like is to be able to have a rotate or move tool in the preview window itself. And maybe a mirror function in the hair room so my selections are symetrical.

Ooh and maybe sp1 can bring me a beer and rub my feet too?

Move and rotate the figure, parts, or Camera?

Quote -

Also I can't load Mimic files.

I suspect this is because of the bug with Poser 8 not recognizing Capitalized Poser Files (PZ2 is ignored, change to pz2 and it will load)

If not, let Support know.

I agree with the Scroll bar, that's something I noticed right off the bat. not that I couldn't see it, but because I missed it with my clicker 50% of the time. Sometimes it can disapear, as you mentioned. What I had done to be able to see better is expand the side panel out a little and it showed up much better, (but still small).

I also tried the render after rebooting at 84 to the remaining 105 frames. What I had discovered is it then started the first frame at 5:45 seconds as the animation began from that frame on. I timed a few frames later and they remaind the same rated.

I think what is happening is, It must be adding each accumulated past Keyframe that had been rendered, to each new keyframe in the process of being rendered. thus slowing the animation render process incramentally down. I was able to finish that animation clip. But now I have a clip of a 122 frames. there goes about 9 hours I bet.

As far as sending ideas to make poser better, it is best to send them in as suggestions. If you have a bug report, (scripts?) that is probably a bug. What I am doing at this point doesn't involve scripts. so I would report it to SM.

the image in this message is what I mean

After copious searches of the poser forums here at Rendo, I finally got my Poser 8 working with my old library.  From the cursory examination I've had, I like what I see and I'm no longer cursing myself for spending the money I spent.

Here's one change I'd love to see, and maybe P8 already does this and I haven't figured it out:

Like many people these days, I'm running Poser on a dual monitor setup.  I usually drag the library window over to the second monitor and it fills up the whole second screen.  When you do this in P7, the folders will fill up the entire screen going sideways and therefore, you have less scrolling.  P8 doesn't seem to do this, and no matter how big you make your library window, you just get a vertical of folders.  I would love to see the folder window operate in a similar fashion as P7's did, so I won't have to scroll up and down and all my folders are visible at the same time in a fully expanded window.   Like others, I would also like to see the folders get bigger...

EricJ - I'm rendering at the moment so I can't check, but if you use the "Show" dropdown list to pick the runtime you're interested in, does the Search function still display the results from all runtimes?

Whichway

Report both ideas and issues.... Same location.. (It would be best to place each one as a separate incident, but is not needed.. Support can split them up if needed for better tracking.

Quote - I would like a better color contol/picker. The one provided now (in the materials room) is very barebones. I am color blind (I see some colors, but not all of them). The sepia gradient at the bottom of the first picker really does not produce browns, and I cannot pick out the different colors from the swatches on the secondary color control.

LMK

I totally agree. I don't have any problems seeing, but that color picker is just plain stupid and I can't believe after all these years it's still being used.

The Windows color picker is bad enough, but it's a lot better than what you get in Poser when you click on a color. You get that stupid gradient picker first and then have to click another button to get to the real color picker.
Now why is that stupid? Because the first level is completely inaccurate, no way to get an exact color, just slide your little cursor along and select something. Do you want black? Well, you can get black if you get the cursor just right, but you migth end up with RGB 0,3,7. How about pure yellow? Will you settle for RGB 255,251,6? That's close enough, right?

I don't mind the gradient thing, but for God's sake, make that the option, not the default in future Poser versions.

Better yet, they really ought to create a new color picker entirely. Just pick an app out there to model it on; since every 3D and 2D app in the world has a better color picker, whatever you settle on will be better.

I would like to add a few usability items to the list:

1. When a scene is saved, a small thumbnail is automatically saved along side of it to take the guess work out of what "V4_scene 1a" is. (I do export the image but why not have Poser generate a thumb automatically)

2. Add a field to the properties window to display exactly what something is pointed to. Or maybe some indicator in the Hierarchy window. Something.

3. Be able to look thru light (not shadow cam) to see exactly what is being lit and be able to rotate/adjust light thru that view.

4. Be able to load a figure/prop @ user supplied x,y,z coordinates vice always default 0,0,0.

PhilC has a Python script in his forum here, http://www.philc.net/forum/viewtopic.php?t=2572  which when you run it saves the scene with a thumbnail.

Quote - PhilC has a Python script in his forum here, http://www.philc.net/forum/viewtopic.php?t=2572  which when you run it saves the scene with a thumbnail.

Awesome raven! Missed that...thanks. And to you as well PhilC!

Thinking of what samhal suggests, it would be nice if, when saving a figure, hair, prop, etc., we could have a choice to let Poser make a thumbnail as it usually does, render a thumbnail, or brouse to the thumbnail of our choice.

LMK

I would like the option of saving to the library without overwriting the thumbnail.

as a user, i sometimes have to fix older content and would like to save it back without loosing the thumbnail.

as a content creator, i often have to fix and resave my items and would like to keep my thumbnail.

I just received a response from Smith Micro in relation to a few problems and suggestions to improve Poser 8.  I don't know if anyone is interested, but thought I'd post them anyway in case others are having similar issues.  It also shows they are listening and responding if sent directly to them.  My questions and their response:

MY QUESTION:  When changing the background color from the menu, it doesn't work (Display>Background Color). It started off a darker shade of gray. I tried to change it to white and the entire background turned black. It works if you select one of the four circles (the second I think) to the right underneath the posing window.

RESPONSE:  This issue has been reported. The current workaround is as discovered, the dots at the bottom right.

MY QUESTION:  Python issues: Python tool from DAZ3D (RoomCreator2 QuickPose by Maclean) disables the parameter dials. I never had this problem in Poser7 especially with the parameter dials. Sometimes an open Python window caused other issues, but not this one.

RESPONSE:  Please provide the URL of the Product Page for the Room Creator Product.

MY QUESTION:  A few cosmetic changes I'd like to add:

The Library: Put the vertical scroll bar on the left instead of the right. I have to use the horizontal scroll bar to get to the veritcal. The vertical scroll bar button should be larger. It has a tendency to get too small when there are a lot of items in the folder. Also a collapsible button like in earlier versions. I know I can close it or undock it, but reopening it is more steps than necessary.

RESPONSE:  You can collapse down the space the Dots and Tools take up when Docked. When Docked the smallest width is limited by the other Docked items in the section. If you remove the Lights and Camera Controls, the Editting Tools get down to a single Column. (UI Dots stay 3 by 3 since they still display that width at the narrowest Column Width.) If you are referring to when they are floating, you should be able to resize the window so they are displayed in a Vertical Column, Horizontal Row, or a block of various Rows and Colums. The Dots do stay at the 3 by 3.

MY QUESTION:  Memory Dots: Take up too much space by still being a row of three. Why can't these all be on one line? There are only nine of them.

RESPONSE:  The Memory Dots are locked at 3 by 3. I have passed on this suggestion as an Enhancement request. I am not sure any space could be saved, since the Dots narrowest width is the same as the that of the Editting Tools when placed as a Vertical Column and only slightly larger when in a Horizontal Row. I think that is the narrowest Column and Row width allowed.

MY QUESTION:  Editing Tools: Also take up too much space. A way to make them vertical.

RESPONSE:  You should be able to make these Vertical or Horizontal by resizing the Window or Dock Section when Docked.

MY QUESTION:  Docking: Ability to dock items side by side such as the Memory Dots, Editing Tools, and Lighting Tools which are smaller items.

RESPONSE:  You can have Dock next to Docks.   (My Note:  How???)

MY QUESTION:  Room Tabs: All that space after the "room" tabs. Why can't we put things up there like the library and other tools that could be available in other rooms?

RESPONSE:  Not sure what you are asking here... Do you want to have the Library be able to be a Tab at the top?

ME:  He wasn't aware that the tabs used to be called rooms several versions back.  I was suggesting that since there was space after the Content tab that some tools could be put up there.  I think I'm asking too much.

samhal - Why do the shadow cams not work for you?

Whichway

Quote - MY QUESTION:  Python issues: Python tool from DAZ3D (RoomCreator2 QuickPose by Maclean) disables the parameter dials. I never had this problem in Poser7 especially with the parameter dials. Sometimes an open Python window caused other issues, but not this one.

RESPONSE:  Please provide the URL of the Product Page for the Room Creator Product.

That script use a tkinter GUI, which would appear to not be getting along too well (not really a surprise) with the new P8 GUI.
It doesn't look as though it would a difficult job to update to make it compatible with P8, but ockham (and probably Maclean) would have to give permission to distribute a modified version if someone other than ockham produced an update.

Please forgive me if this has already been mentioned (I read through the thread and didn't see it).

I would dearly like to see the frame count displayed for animated pose files (as was the case in prior versions). As it stands, P8 gives the user no clue whether a pose file is a single frame or an animated sequence... or, at least, I haven't found the clue, yet...

Frankly, the library display may be faster but I find it FAR less functional if I can't easily browse or see what items are (and I find the thumbs too small). It's annoying as hell to have to click on each to see detail -- and quite useless if the detail isn't there to begin with (i.e., frame count).

There's a lot of good in P8... but I find myself working in Poser Pro or P7, mainly because of the library interface.

Quote - samhal - Why do the shadow cams not work for you?

Whichway

Howdy Whichway!

Well because unless I'm doing something very wrong, they're nothing but cameras. Let me explain.

I can switch to Shadow Cam 1,  and I don't see where you are looking thu the light. I can rotate around until I find the light, any light, but that's looking thru it unless I come up on it. Matter of fact, if you rotate the Shadow Cam 1, and switch to the Main Camera, it's exactly the same...unless like I said, I'm missing something somewhere.

What I'd like is something akin to C4D. It's called Link Active Object. When you look thru a light, you look thru the light. Any movement affect the lights position directly, totally independent of anything else in the scene.

Hope I explained that right.

samhal - Hmm. Well I'm rendering at the moment so I can't check, but...[That is becoming my all-purpose excuse these days.]

My understanding was that each Shadow Cam was linked to a particular light; that camera is used to render the shadows from that light, so they have to match. There is al least one problem figuring out which Shadow Cam goes with which Light. (Poser 8 may help there, or it's just been that I'm using a scene where the vendor nicely named the Shadow Cams to match the Lights.] Also, while looking through the Shadow Cam, you probably want to set the Dials Panel to show the controls of the corresponding Light. Then, I think, things should work as you expect. Maybe.

Whichway

P.S. - I suppose it's possible that if the light has Shadows turned off, there is no corresponding Shadow Cam.

A request of my own:

How about the Render Status panel showing the time the render was started?

Whichway

Quote - > Quote - I'm not sure what you're speaking of.  The lower right of the Library header?  The Library is just too wide.  All of the important tools should be on the left, not the right.  That is just common sense.  Not everyone has two monitors or a wall-size monitor.  I would love to get a second monitor just to put all the tool items on and have a descent workspace.

the image in this message is what I mean

That bit of weirdness came about because the UI design team wanted that little content menu flyout triangle on the right side, just like in Poser 7.

But when I opened the menu there, everything became bunched up on the right side immediately. So I moved the first menu to open on the left side, in order to at least get some cascading of submenus across the panel.

I agree, the triangle widget should be on the left, even though that isn't where it was in Poser 7.

Quote - [

I agree, the triangle widget should be on the left, even though that isn't where it was in Poser 7.

BB it doesn't matter where the triangle widget is to me. Just would like to click on the triangle widget and cascade out from that in one click on the widget if possible. Whether it cascades to the right or to the left, people will adapt and it will become the norm over time. Granted I am one of those people with two monitors and my lib pallet is on my left monitor. However I would make it work if it was docked to the right of the main preview panel (for the right handed single monitor people)

PS: BB you need a new nick. Either "Flash BB" or "The Flasher!" :scared:

I don't know if many her do animation, but I have a few bugs that I reported.
1). if I try to add a mimic file to an animation. It doesn't take. meaning. no the audio files are placed into the animation, but the lips do not take the mouth and head movements. Basicly the animation just sits there unless I have other movements already hand animated, or BVH files added.
My painful workaround is to go back to Poser 7 and then add the Mimic files. save them, then reopen Poser 8. Then eveything works great. The problem with that is I can't see the good detail with the type of lighting I like to use in poser 8 when I'm in poser 7 because the scene is to dark. Which when in Poser 8 the scene show up nice and brightly.

Here is something that I think I might understand, maybe someone can tell me if I'm right or not. I can animate a scene of 180 frames say. The big change is if I am using Raytracing. Sometimes the animation per will be 7:15 min. per frame. and at the end will drop down all the way to 4:30 per frame.

I can animate that same scene at a different angle and same charactures and the animation will range frome 2:35 to 5:00 per fame. The only thing that I can think to cause such radical time differences is possibly Raytracing. I have two mirrors in both animations along with the charactures and interior scene.

My guess sometimes the mirrors might be closer to the camera, or mabe if the mirror is more, this maybe what is causing a longer render. As I have 2 people reflecting in the mirror, and the walls are shiny with a reflextion of the people also, As Amos & Andy might say. Their is a whole lots of reflextions goin on here. 

Also in the animation Palette. It's scroll bar doen't show. It works, but I have to guess where it is. This only applies when doing animations. along with that also in the animation palette, when I click on the play button. it plays when I click on it to stop, it stops for a second and begins a second later with out me clicking to get it to go again.

When they get all the bugs out. Poser 8 will be a great program.

The ABILITY TO SAVE AFTER MAKING A CHANGE IN THE MATERIAL ROOM. Blech. Coming home strong to me right now with P8's instability in the material room. Kept losing work. It's a real hassle to just switch a camera or something all the time just to save my work. (I gave up doing major work in the P8 material room now; I'm back in Poser Pro for that task.)

I've rearranged the rhs so that the parameters are docked above the library; this suits me better. I still prefer the side-by-side arrangement of Poser 7 though; a lot less scrolling!

NB
Scroll wheel works with parameter palette but not with library palette. Have to use the bar on rhs of library palette and it's difficult to (a) see and (b) use. Someone suggested using up and down keys to move through the icons but it doesn't work on my machine. (Mac G5 ppc OSX Leopard)

Not only that the P8 women are butt ugly (not a thing -there are allready nice morphs around),but worse : the arm length / body height relationship is completly wrong. Her arms are much to short.This should be fixed in a figure service release .

sunbeam, please send bug report to SM on the up-down keys in library, as they are working for some OS X user(s).  see if they work in tiger version of poser 8.

May be the scrool bars a bit more large ...

Quote - sunbeam, please send bug report to SM on the up-down keys in library, as they are working for some OS X user(s).  see if they work in tiger version of poser 8.

Ok. Yes, they worked in Tiger version.

second the request by vilters to change colours of active morphs, and expand on that idea by having the option to hide unused morphs in the list.

the 4 IK options to be in the title bar of the main window, so i dont have to faff about with the pulldown menu one at a time

mouse control of main window camera, ala maya etc, at the very least scroll wheel zooming

and lastly a button to make renders come out how i intended :P

 I'd like a link to  the page with a list and link to all the free Python scripts that work in Poser and what they're supposed to do.

Quote - MY QUESTION:  Docking: Ability to dock items side by side such as the Memory Dots, Editing Tools, and Lighting Tools which are smaller items.

RESPONSE:  You can have Dock next to Docks.   (My Note:  How???)

Yes, you can dock next to docks but it can be tricky.  It looks like the UI "guesses" at how you want the docks placed but I have been able to get docks next to each other.

Try moving a dock into place, say a horizontal tools palette, and then move the display styles palette just to the left of it so that the tools palette glows.  You should be able to release and have it connect where you have the display palette right next to the tools palette.

If you drag a palette slowly, when the mouse pointer is over a potential docking zone, you'll see a hint strip where it will dock should you release the mouse button.

Quote - > Quote - samhal - Why do the shadow cams not work for you?

Whichway

Howdy Whichway!

Well because unless I'm doing something very wrong, they're nothing but cameras. Let me explain.

I can switch to Shadow Cam 1,  and I don't see where you are looking thu the light. I can rotate around until I find the light, any light, but that's looking thru it unless I come up on it. Matter of fact, if you rotate the Shadow Cam 1, and switch to the Main Camera, it's exactly the same...unless like I said, I'm missing something somewhere.

What I'd like is something akin to C4D. It's called Link Active Object. When you look thru a light, you look thru the light. Any movement affect the lights position directly, totally independent of anything else in the scene.

Hope I explained that right.

I know exactly what you mean. I've had the same problem, since I use Shadow Cams, but only now and then so I tend to forget how to display the cam view.

Here's the trick: You have to select the Shadow cam from the viewport. Right-click in the upper left corner of the viewport, on the name of the view (e.g. "Main Camera"). From the drop down menu that appears, just select the light that you want to view through.

Believe it or not, this is actually a good thing since it allows you to have the light selected while viewing though the shadow light cam. You'll need this because it's the lights' parameters that control the position and direction of the light, not the Shadow Lite Cam parameter's. (Those mainly control the near and far clipping of the shadows, but that's another story.)

I typically use the Shadow Lite Cam to help position spotlights on figures, say to highlight a face, or to help see how a shadow will fall.

Quote - > Quote - > Quote - > Quote - Request for SP1: allow linking of runtime folders which are named something other than "runtime."

Did you try to make a shortcut of "P6 runtime", named just "runtime", and mount this shortcut in P8?

Thanks for the suggestion.  I'm afraid I don't see a way to make that work though.  Poser wants to link to a folder.  It doesn't recognize shortcuts.

It just seems really odd that the acceptability of a runtime link would be dependent on the name of the folder.

You don't select the "Runtime" you select the folder that contains it. I'm confused by what you're saying. For example, to attach all the content in

c:FooBarRuntime...

You select c:FooBar and the GUI says this is Bar. If you're saying you have:

...P6 RuntimeRuntime

and you're choosing to add P6 Runtime, then it should work. However, if P6 Runtime does not contain a RuntimeLibraries folder it should not work.

Thanks for the message, BB.  I've always kept my main runtime folder as e:P6 Runtime.  All previous releases of Poser have allowed me to link to that runtime even though there are no levels in the path which just say "runtime." 

So to access my main runtime in P8, I had to add another directory level, so it now reads E:P6 Runtimeruntime... (libraries, etc). 

This has caused me to have to relink all my textures and geometries which used relative references which, in turn, has caused several days worth of headaches. 

An earlier poster also suggested that the widespread use of relative references requires that "runtime" be one of the named levels in the path, but I just don't see why that is necessary.  It always worked in previous releases without that hard constraint.

OTOH, maybe I'm the only one without "runtime" at some level of the path in each of my runtimes, so I'll just have to adjust.  Then the headaches wil go away.

Regards...

It worked in P6 because P6 had a whole bunch of extra lines of code to try different combinations with and without "runtime" as the first folder in the tree.

This was discarded as of Poser 7. Had you upgraded earlier, you would have run into this already. It's not going to come back.

I think the issue was that if you don't have that single portable root, it's more trouble to install things. Given some product package, you'd have top level folders for Geometries, Textures, components under Libraries, and potentially a Python folder. With the anchored way, all packages begin with Runtime and can be merged with other packages easily.

addendum to previous post...

Just saw the subsequent post mentioning that the requirement to have a "runtime" level in the path was added with SR3 of P7.  I don't think I ever installed SR3 of P7, so happily missed this loss of flexibility... until now with P8. 

Still can't think of a single good reason this restriction was added.  I was happily managing my separate "P6 Runtime" and "P7 Runtime"  without this "runtime" layer... until abandoning P7 entirely due especially to its lousy cloth room.

Once I get CorrectReferenceProII working so I can fix all the references P8 is looking for I should be set.  So far P8 seems like a worthwhile move up from P6, despite some of the hassles or reconfiguration of runtimes.

Quote - It worked in P6 because P6 had a whole bunch of extra lines of code to try different combinations with and without "runtime" as the first folder in the tree.

This was discarded as of Poser 7. Had you upgraded earlier, you would have run into this already. It's not going to come back.

I think the issue was that if you don't have that single portable root, it's more trouble to install things. Given some product package, you'd have top level folders for Geometries, Textures, components under Libraries, and potentially a Python folder. With the anchored way, all packages begin with Runtime and can be merged with other packages easily.

Hiya BB... here we are cross-posting.

I understand what you're saying about installation of addons and products.  I've often objected to the directory structures imposed by merchants (adding tildes to raise their products to the top of my libraries and such, or adding subdirectories I don't want in my runtime tree).  So I've tended to manually install then move textures and geometries and such where I want them in MY structure so I can keep track of them, including purging them if I decide I don't like something.  This has always required manual relinking or use of CRPro.  I've also tended to use absolute referencing so it made no difference whether my runtime was named "P6 Runtime" or whatever.  But I imagine my situation and approach are different from most others, so I'm certainly willing to recognize the need to adapt my approach to conform to P8.  It just would have been nice to avoid the hassle, but so be it.

And as a side note, thanks for all you do to help people out and work to improve the Poser product line.

Regards...

The "single good reason" I can think of is that I open a zip file and drag the Runtime folder wherever, and it merges everything automatically.

Otherwise I'd have to drag Geometries, Textures, and Libraries, and sometimes Python - four drags instead of one.

Or, if the zip file had a top-level folder with some arbitrary name, like V4CoolStuff, and I wanted to install it in my V4 external runtime called V4 Runtime, I'd have to drag V4CoolStuff to some temporary place, change the name to V4 Runtime, and then drag it onto my existing V4 Runtime.

Either way, it's extra work. I know people say you shouldn't just drag a zip contents somewhere without examining it, but I have no trouble examining it while it is still in the zip. Then I drag it.

Quote - The "single good reason" I can think of is that I open a zip file and drag the Runtime folder wherever, and it merges everything automatically.

Otherwise I'd have to drag Geometries, Textures, and Libraries, and sometimes Python - four drags instead of one.

Or, if the zip file had a top-level folder with some arbitrary name, like V4CoolStuff, and I wanted to install it in my V4 external runtime called V4 Runtime, I'd have to drag V4CoolStuff to some temporary place, change the name to V4 Runtime, and then drag it onto my existing V4 Runtime.

Either way, it's extra work. I know people say you shouldn't just drag a zip contents somewhere without examining it, but I have no trouble examining it while it is still in the zip. Then I drag it.

My main runtime is the product of six or seven years of accumulating stuff.  It would be entirely unmanageable if I let merchants choose how their geometries and textures and poses and lights and such get embedded in my runtime... so I always drag stuff where I want it and relink.  It is more work, but I can keep all textures and geometries and poses and such organized in "file cabinets" through an intervening directory level (e.g., textureseye textures...etc).  This approach includes using a "to be tested" cabinet where products can be tested before being promoted to my main runtime.  But again, I know my situation is probably unique, especially since these habits and workflows were formed way back when you could only have a single runtime (having started with Poser 4).  In any case, I like to keep as tidy and lean a runtime as possible, dumping unused geometries and textures and such to external holding bins.  This approach would itself be unworkable if not for CRPro, which not everyone has. 

But that leads to a thought... maybe P9 could have a CRPro type utility built-in to help people manage their inevitably bloating runtimes.

Getting way OT, but.... Here's what I REALLY wish content creators (and I'm thinking of hair, character and clothing creators, in particular) would do: Organize their files so that it was obvious what figure their set was for. In the case of expansions to something existing, nesting the folders for their product inside of the folder for the orginal product.

Here's an example.

Artist 1 creates hairstyle X.

Artist 2 creates an expansion pack for hairstyle X. What this usually means is that the expansion pack is God knows where - perhaps in a folder under Artist 2's name. Anyone with a decent sized runtime has a good chance of forgetting that there are extra textures/morphs/whatever for hairstyle X, because they're nowhere in the vicinity of hairstyle X in the runtime. Much better that when I go to /libraries/pose/Artist 1/hairstyle X, nested inside that I see a directory called Artist 2/hairstyleXpansion or whatever.

That's exactly how I set my runtimes up. I put all texture packs (mat pose) in a folder that matches the product name. Plus I rename a lot of stuff to exactly match the name of the product purchased, which a lot of times is not the same of the folder names inside the zip. A little extra time during install, but saves a ton of time trying to find something when creating a scene.

Quote - Getting way OT, but.... Here's what I REALLY wish content creators (and I'm thinking of hair, character and clothing creators, in particular) would do: Organize their files so that it was obvious what figure their set was for. In the case of expansions to something existing, nesting the folders for their product inside of the folder for the orginal product.

Here's an example.

Artist 1 creates hairstyle X.

Artist 2 creates an expansion pack for hairstyle X. What this usually means is that the expansion pack is God knows where - perhaps in a folder under Artist 2's name. Anyone with a decent sized runtime has a good chance of forgetting that there are extra textures/morphs/whatever for hairstyle X, because they're nowhere in the vicinity of hairstyle X in the runtime. Much better that when I go to /libraries/pose/Artist 1/hairstyle X, nested inside that I see a directory called Artist 2/hairstyleXpansion or whatever.

The future plans for Poser content and the next-gen library GUI will be taking care of that, along with a few other common problems. Where things are or what they are called will become totally irrelevant.

Quote - NB
Scroll wheel works with parameter palette but not with library palette. Have to use the bar on rhs of library palette and it's difficult to (a) see and (b) use. Someone suggested using up and down keys to move through the icons but it doesn't work on my machine. (Mac G5 ppc OSX Leopard)

I'm using Windows XP and, I have no difficulty using the scroll wheel in the library. I find the whole GUI acts exactly like Windows. Each section is it's own separate window(even when docked), only one can be active at a time. So if I want the scroll in the library, I have to select something there and then scrolling works like normal. Same with anything else in the GUI.

I can't speak for the Mac, since I've never used one - but I would hope it works the same.

My SR1/SR2 requests;

• bigger thumbnails in the library.
• better stability, I will admit that I've had very few crashes but the more bug fixes the better.
• the ability to alter the color of the GUI, I don't really mind the gray but I do miss that beige from previous versions.
• a way to set permanent python buttons from inside Poser without having to edit text files.
• When trying to dock two windows next to each other having a selection box that gives you the choice of horizontal or vertical docking.
• Allow me to adjust to size of the docked preview window. I don't mind having some empty space around it.
• fix the sluggish-ness in the material room.
• fix the sensitivity on the camera controls, it's almost impossible to cycle through cameras using on the icons now.
• allow saved PZ3s with specific preview dimensions to undock the preview window and match saved window dimensions.

That's all I can think of for now.

There were some problems with scroll wheel and keyboard focus. I believe/hope they are fixed now. Please be aware that on the Mac, scroll wheel is simply not supported by Adobe, so I had to do some weird Javascripting to make it work. Also note that on the Mac, the scroll wheel data is not so standard as on the PC. We found some Macs sending completely different numbers for each click than other Macs. Imagine you're expecting +3, -3 and you get +.01743. Heheheh.

User defined thumbnail size is in Beta SR1 now. Actually two sizes - you pick a size for all thumbs, and optionally you can pick a bigger size for the selected item. They are configured using sliders that update the screen in real time. In fact, there are now 8 configurable things in the Library GUI to let you tailor its appearance and (to a limited extent) behavior to your personal wishes. More will be coming in SR2. Much more.

Quote - More will be coming in SR2. Much more.

metadata?