clickText bug in 3.0

Anything beyond the basics in using the LiveCode language. Share your handlers, functions and magic here.

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
TEDennis
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 41
Joined: Tue Apr 11, 2006 12:36 am

clickText bug in 3.0

Post by TEDennis » Thu Sep 18, 2008 12:20 am

No response on the Beta forum, so I'll post a link to it here.

http://forums.runrev.com/phpBB2/viewtopic.php?t=2081

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10043
Joined: Sat Apr 08, 2006 7:05 am
Contact:

Post by FourthWorld » Thu Sep 18, 2008 8:36 pm

Looks like the Beta forum's gone. What was the question?
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn

TEDennis
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 41
Joined: Tue Apr 11, 2006 12:36 am

Post by TEDennis » Thu Sep 18, 2008 9:26 pm

The beta forum is still accessible to me. Whatever, here's the post:

I have an app that fails in 3.0, but worked fine in 2.9.

The returned value from "clickText" has changed.

According to the doc: A word, for purposes of the clickText, is any text delimited by spaces, tabs, returns, or punctuation. In the following example, "123,456" clickText returns the entire string. In the prior release, it returned either 123 or 456 depending on where in the string it was clicked. Add the following script to a button, click it, then click on each of the values in the field. The returned clickText is displayed in the Message Box.

Code: Select all

on mouseUp 
   if there is not a field "Test Field" then 
      create field "Test Field" 
      set the lockText of field "Test Field" to true 
      set the height of field "Test Field" to 50 
      put "123 456" & cr & "123, 456" & cr & "123,456" into field "Test Field" 
   end if 
   put the clickText 
end mouseUp 
I suspect it's treating the comma as a thousands separator for numerics. It works as "expected" with alpha characters.

A response in the Beta forum suggested I post this at the QA center, so I did. Frankly, the segregation of the two sites is a pain. How will anybody know what problems to be aware of unless they monitor two (or more?) sites?

Post Reply