intSlider bug

I was beginning to think I was nuts because I couldn't reproduce it. But I accidentally managed to trigger it again. The intslider is in the '1' position but displays (and renders) the '2' value. It corrects after I slide it forth and back.

The sliders do that in preview mode on me too, if I change one in the middle of it rendering a preview. I believe the normal sliders also do that if they are remapped. You = not nuts, at least not about that ha-ha.

jffe

It happened while finalizing this one.
But as I said, I don't exactly know how to reproduce it. I think it has to do with 'preset filters' and then increasing the max value of the intSlider.
I remember wanting to upload the filter. Then I got the message I had to use a checkbox for the 'Ball type' (I had only two ball types at that time). So I added the egg shape and increased the max value of the intSlider. Then I returned to the presets to turn some into eggs (don't remember if I actually closed the editor or not) and it happened.

It happens pretty much anytime the filter takes any real cpu power to process, like if the filter is going to take more than 5 seconds to apply, then you get that lag with the Int Sliders. Like Kraellin said, it never seemed worth reporting really, but now that someone has mentioned it, we should chime in and make it known I suppose.

jffe

That's not what I'm talking about. While the preview is rendering, if I move an Int Slider, often times it moves, but neither does it change the render in progress, nor the display value of the Int Slider position. It is not that "rare", it happens fairly often really.

jffe

does it happen in Filter Editor or in the main Filter Forge window or both?
and is it in the plugin or the standalone version?

----For me, it happens for sure in the main FF window, I don't look at the preview (or should say can't see the tiny preview) window in the editor that much, mostly use to to see if there's been a radical color or shape change while rewiring. I am only using the stand-alone version, never used the plug-in version.

please post the image on which it happens (or at least tell us the dimensions) and the filter (or just name it, if it's a library filter). Or does it reoccur on various images and filters?

----It happens on pretty much any/all filters that take any real amount of time to render a preview of, like anything that's going to take over say 30 seconds for the time elapsed bar to gray out. The size of the picture being processed does not seem to matter, although that could have to do with how long it takes to render the preview no ?

----Maybe I should add, that I use a Pc, a Pentium 4 2400 with a gig of DDR400 ram, running WinXP. My cpu usage other than FF, is usually maybe 3%-5%, perhaps Yahoo messager is on, and sometimes Winamp, other than that, it's a pretty stripped down system set up for audio production.

jffe

Last time it happened it was in the editor (but can't say for sure that it doesn't happen in the main FF window). I always work in standalone so...

I don't run in to it very often. I'll keep my eyes open and hit prntscrn and such as soon as it occurs.

Hi.

Did you find the problem with this control?

I have not had exactly the same problem but there is something wrong.

In the picture is a Int slider set to Value 2 and Max Value 4

Clicking Arrow 1 moves the slider from position 2 to position 1 as expected

But clicking on arrow 2 Does Nothing – This is not right, Is it?

You have to click on arrow 3 (ie past position 3) before the position will move from 2 to 3

Also.
There is no indication of how many positions are available on this control. It would be nice if the intervals were marked as in the lower picture.

Ken.

Quote
Ken wrote: There is no indication of how many positions are available on this control. It would be nice if the intervals were marked as in the lower picture.

I'd love to have this feature as well, but that would require a complete redesign, re-coding and re-testing of the slider control. This is already on our list, but I can't promise anything.

Ken, the behavior you are talking about is correct.

When you click the first arrow you are choosing a value somewhere between 1 and 2, and this value is truncated to get the nearest smaller integer value (which is 1 for this example).

So when you click the second arrow (which is between 2 and 3) the truncation result will be 2, that's why the actual slider position does not change.

Sounds like something that should be updated at V1.1 or whenever. I can see letting it slide (pun intended?) for now, but not forever.

jffe

Ken: Put it on my to-do list