Dear LiveCoders, Ok, I’ve tried to put together a test bug stack that will illustrate the problem.
You can download the stack here from my dropbox account. http://tinyurl.com/kp4k6s5 If you play around with it for a little bit you’ll notice the strangeness I’m describing. I want to make sure this really is a bug before having it reported as one. I’m using OS X.9 Mavericks, LiveCode 6.5.2 (rc1), and Xcode 5.0.2 (Yes, I’ve tried this with 6.1.3 and 6.5.1 etc. This stuff used to work just fine under older versions of LC, but not anymore. The problem exists with the OS 7 Simulator and on an OS 7 iPad 2. Let me know what you discover. Thanks, Rick My previous message follows: > There is something really weird going wrong with mobileControlGet > for LiveCode in iOS. When I get the MaximumPixelLengthOfField it > first reports 15022. If I jump to that location to see the last line, I > discover that it really isn’t at the end of the field at all. After > physically scrolling down the rest of the field my pixel counter > tells me that the end is really at 18500 for the last line of text. > > That wouldn’t be so bad, but then when I tell the field to scroll > back up to the top of the field and do the same thing again, this > time it will tell me that the end of the field is at 30217, even though > I started back at zero. If I jump back pixel 30217, the field isn’t at the > end, and I have to physically scroll down to the last line of text again > which ends up at yet another larger number. > > Is this a know bug? > > It is really screwing up my scaling process so that I can't know where > I am in the list. > > put mobileControlGet("ListOfText", "contentRect") into VarContentRect > put item 4 of VarContentRect into VarMaximumPixelLengthOfField _______________________________________________ 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
