In detail:  I was using the keygraph to change the scale of the Sparkle object.  When I pulled the line below the boundary of the topmost window [the graph for Scale], the cursor jumped to  the underlying window [the main keygraph list] instead of continuing to pull the value downward as would have happened in previous Poser versions.  The underlying window also moved up to topmost.  (You can see the 'pulling' cursor in the middle of Play Range on the After screencap.)

The expected action in any drag-drop, like the action of a scrollbar, 
is to keep pulling the 'grabbed' item until you release the mouse,
even when you cross over HWND boundaries.  It appears that 
P7 is not doing the expected thing.  

The cursor also switched over to the 'rotate' symbol after crossing
the boundary, though this symbol doesn't show in the screencaps
for some reason.

I use this particular move quite often in animation, so I'm familiar 
with the way it behaved in previous versions.  The drag did in fact 
continue to pull the parameter value until you released the mouse.

Note also that the name of the Scale parameter doesn't show in
the pulldown box at upper right.  This may be related or not.....

Weird!  Thanks, ockham, for this heads up.  I'll watch for it, though I have been tending to avoid doing much animation work in P7 so far.  I'm doing my modeling and animation in P6 and using P7 only for rendering.  But I sometimes do some last minute adjustments within P7 so it's good to know about another issue to watch out for.  Cheers...

Another weird thing in that same keygraph: sometimes you can see
the parm values represented in text form as a row of numbers, before 
they show up in graph form.  Looks like a debugging statement accidentally
left in the code.  (Unlike the focus problem, this doesn't affect 
operation; I'm mainly recording it here for the benefit of any e-frontier 
programmers who might be reading!)

I haven't seen the particular problem you describe, though your "Before" screen-capture illustrates an issue that I have noticed in P7 SR1.1.

Notice that the text box in the upper right corner of the Graph window is empty, whereas it should list the currently-selected Parameter, as it did in previous versions of Poser. I can populate the textbox from the drop-down list, but it no longer auto-populates from selections made in the Parameter window. I have to click the right-arrow and select Graph...

Quote - I'm mainly recording it here for the benefit of any e-frontier 
programmers who might be reading!)

Please make sure you always submit such findings directly to e frontier as well.

You're right, stewer. However, my search of the e frontier Website has not found a way to report this kind of information. For example, I don't see it on their "Contact Us" page:
http://www.e-frontier.com/article/articleview/20/1/289?sbss=289.

Do you know how we should submit bug reports to e frontier?

You have to go thru  the Technical Support page. There you will find a button "contact tech support".

http://www.e-frontier.com/article/articleview/18?sbss=435

Don't know, why they don't have that one on the contact us page.

Just wanted to add my observations here, I've noticed similar problems with the graph editors, if you drag a key in the animation palette the window doesn't expand smoothly and just will not show the last couple of frames until you move the scroll bar, this was never a problem in P6 and did not seem to get addressed in SR1.
 
I concur with Ricky_Java 
 
"Notice that the text box in the upper right corner of the Graph window is empty, whereas it should list the currently-selected Parameter, as it did in previous versions of Poser. I can populate the textbox from the drop-down list, but it no longer auto-populates from selections made in the Parameter window. I have to click the right-arrow and select Graph..."
 
I've also noticed that the graphs suffer from a slight opacity, that is to say that clicking in one can sometimes select something in the window beneath, this is also true of the workspace window, I had my toolbar partly hidden beneath the main window and whilst selecting an item suddenly found the translate tool swapped for the break chains tool! Very nearly a disaster!

Incidentally and a little off topic but since Ockham started this thread I've had numerous problems trying to run python scripts in P7 so still use P6 when I want to run any of his great freebies, Jiggles, Smoother and the really useful 2 and 3 graph windows

www.youtube.com/vjflickeringlight

Thanks for the link, msg24_7: I've saved it as a favorite. It's a simple Web form, and I described the textbox issue for them.

@3Dave: 

Just yesterday somebody sent me a detailed report on P7
problems with Jiggles.  I'll be fixing that one, and will look also at
Smoother.   There are some mechanical version changes that can
be made easily on that family of scripts.

Those 3-screen keygraph things were never really solid
even in P4 ...  I used a 'back door' trick that isn't strictly legal in
Python.  I'll look at them, but no promises.

@ockham

thankyou for the info, I look forward to hearing when Jiggles etc are updated, sorry I wasn't able to give more details of the problem I had, but my poser machine and internet connection are some miles apart. Sounds like I was lucky with the 3 screen graphs as they worked for me in P6. i found them really useful when modifying .bvh (something I often have to do) shame they weren't taken up by e-frontier.

www.youtube.com/vjflickeringlight

Sorry, I've been rather distracted lately by real-life stuff.

http://ockhamsbungalow.com/Python/Jiggles5.zip

Here's a modified Jiggles, with the P7 poser.ini location included.
See if it works any better.  This may not be based on the same version
of Jiggles you're using .... I recall running up a number of alternates
that were posted directly in the forum but never made it to the website.
Some of those alternates were rather specialized.

This is based on the version in Jiggles4.zip.

As for Smoother, I tried it in P7 and it works fine on my machine.
Can you remember or paste the error message you're seeing?

On the  Double and Triple-graph:

Thanks for reminding me of those!  I'd forgotten how useful they are, and
was confusing them with another timeline script.  The other one was the
'dubious' or 'back-door' trick.  These two are solid, and just needed a simple
modification for the new Python version in P7. 

(Python 2.4 is fussier about integers and floating-point numbers.)

The updated versions are here:

http://ockhamsbungalow.com/Python/TripleGraph.zip

Very much appreciated Ockham.  Thanks!

Cheers,
Masha

Quote - .... I recall running up a number of alternates
that were posted directly in the forum but never made it to the website.
Some of those alternates were rather specialized.

This is based on the version in Jiggles4.zip.

 

Hiya ockham--

Just fyi, I still have, and extensively use, the specialized version of Jiggles you so kindly made for me.  The specialized version allows hardwiring the input parameters to avoid the need to specify inputs with each run (since I use the same input parameters each time, so this saves steps).  Anyway, I just ran this "older" specialized version of jiggles in P7 yesterday and it worked like a charm.  I made some other custom mods to meet my needs, but if you ever need a copy of this specialized version back just let me know!

So... Thanks again for making such a great script!

cheers...

@Tguyus: Yes, that's the one I was thinking of. 

@Anyone:  In case you do run into an error in P7 that says something
about 'deprecated cast to float', don't look for rejected orthotic devices
tossed in the river.  Instead, check the line number and you'll probably
find a range statement like this:

for n in range(0, Width):

where Width or some other variable seems to be a floating-point
number.  The solution is to make the variable an explicit integer:

for n in range(0, int(Width)):

Python 2.4 is (unfortunately, I think) becoming more
like C in requiring explicit types on variables.

I just finished using the new Jiggles script to add a bit of Jell-O effects to V3 in a Poser 7 animation. It worked like a million bucks.

I ended up setting the Min Limit and Max Limit on the Parameters to -1 and 1 respectively, since otherwise Jiggles creates excursions beyond these reasonable limits during her most extreme movements. I saw the same excursions with the Kozaburo Short Bob hair that I jigglized last week, and fixed them by hand.

Also, using Jiggles with a figure's Body is not supported, but that's understandable due to the issues with Full Body Morphs.

So the net net is that Jiggles is now P7-compatible. Thank you very, very much, Ockham.

Rick

Thanks for the Pythons Ockham!  I've been meaning to download some of your fine useables everytime I see you post them.  I just wanted you to know your generosity and work is appreciated.

Yes, Ockham... much apreciated. Will try new Jiggles later this week.

I second the reporting of missing actor atop the pull down -- it is not related to what you are reporting here....I want it back!

::::: Opera :::::

 Hi Ockham
Many thanks, will try the new jiggles later today

Hi,

I received an email reply from e frontier concerning my bug report of the missing parameter value in the graph window:

"First off please let me apologize for the delay in getting back to you; we're
trying to get caught up with our backlog.

Thanks for letting us know about this! It should be fixed in our SR2 updater,
which is due out soon. For the moment as you've noticed it's easy enough to
select the parameter you'd like to edit, which will cause its name to draw in
the menu."
So, I'm glad I reported the bug at http://www.e-frontier.com/article/articleview/18?sbss=435 and hopeful that this problem will be fixed in SR2.

Rick