Page 1 of 1

Posted: Tue Nov 04, 2008 2:42 pm
by ggroess
Mike,
In the new build the highlight threshold is not responding.  When I set a shadow I can get the threshold masking and move my point around but in Highlight I can set the point but nothing works.  the curve does not respond to the highlight nor does the mask appear when I drag the point around.

Greg

Posted: Tue Nov 04, 2008 6:40 pm
by -default
Thanks, Greg.  This is a good one.

I've been chasing this one since wnick first reported it.  It finally happened after I just got your note.  I had to set three highlight points.  The first two were ordinary sample points, with no info, and the third became an actual highlight point.

Posted: Tue Nov 04, 2008 6:55 pm
by ggroess
It's even weirder than that...

I tried your three trys result and go the following:

first highlight normal point.
Second Highlight working highlight point.

Then went to the shadow....
first shadow point normal point.
Second Shadow working shadow point.

Further...
If you delete the highlight and try to set a new one; the process starts over 1st point fails second point results correctly
Same results for shadow...

XP system CS3 32 bit

It seems to be on both sides of the spectrum...
Greg


Posted: Tue Nov 04, 2008 7:02 pm
by -default
I can't imagine how I could have coded such a bug in the first place.  Must be a timing or mouse position issue....  More later.

BYW - I was able to get tje installer problem you found to happen on my [Vista64] system.  For CS4 the plugin just goes to the ozone without being installed.

Posted: Tue Nov 04, 2008 8:08 pm
by ggroess
See...Vista Hates me...and now because you know me....

It hates you!...

Greg

Posted: Wed Nov 19, 2008 3:09 am
by ggroess
Mike,
I noticed tonight that when you place the highlight pin...
The right click on the it..the non-functional one....right click...the disable pin is checked...

remove the check and all is normal....

Works every time so far...
Greg

Posted: Wed Nov 19, 2008 4:55 am
by -default
Hmmm - sounds like you might be crowding this bug into a corner, Greg.  Thanks!

Posted: Tue Nov 25, 2008 12:26 pm
by -default
I think I've fixed this one - it's an initialization bug, where the value was not set correctly, and had a random value.  It's amazing that this problem did not shop up in previous releases!

I hope to do a new release in the next couple of days - before I head for Hawaii!!