I can imagine a scenario where you could produce floating point values in the scrollbar output. Suppose your screen is a retina display. The LC point is much coarser than the retina pixel, so one LC point might be 8.72654 *actual* pixels, because the scrollbar has to be smooth visually, so it scrolls by retina pixels (so to speak).
Bob S > On Jul 31, 2018, at 08:16 , tbodine via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Panos' test and Mark's insight have me on the right path. > > I am not using "numberFormat" anywhere, but I am setting the value of > gTSsettings["teamcount] from a mouseup script on a scrollbar. Since my > scrollbar output is apparently coming out as a floating point value, I need > to add rounding to it. > > Not sure how the scrollbar was able to generate floating point values, as > Start/End/Current values are all integers. Is "scroll distance on bar click" > actually used in the result calculation? That was set to .9ish. I thought > the scroll distance setting was more of a UI setting that allowed the user > to not have to hit the exact tick on the scrollbar. > > Thanks to all for your help on this. > Tom B. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
