On Apr 26, 2016, at 11:15 AM, Sannyasin Brahmanathaswami wrote: > Understood.. But even mouse release does not solve the core issue. > > Perhaps the anomaly is here: > > "You use the hilitedLine property to determine which line the user clicked.” > > Perhaps the bug is not that the mousedown and mouseup are ignored, but that > if the user clicks on empty space in the field, the hilitedline remains > highlighted. > > Since I am clicking on “no line” then one would expect the hilited line to be > unhilited. Because, by definition: if you need to “determine which line the > user clicked on” is should return 0 and set the hilted lines of the field to > none. > > At least, that was my “naïve” expectation”
Well, this kind of thing is why I prefer to use listBehavior = false and script it for myself. -- Peter Peter M. Brigham pmb...@gmail.com > On 4/26/16, 2:40 AM, "use-livecode on behalf of Peter M. Brigham" > <use-livecode-boun...@lists.runrev.com on behalf of pmb...@gmail.com> wrote: > >> Much of this is spelled out in the dictionary under "listBehavior": >> >> -------- >> If a field's listBehavior property is set to true, and the user clicks a >> line, the entire line is highlighted. The Up and Down arrow keys move the >> selection up or down. >> >> Normally, the mouseUp and mouseDown messages are sent to the field as usual. >> However, if the user clicks below the last line of text in the field, a >> mouseRelease message is sent instead of mouseUp. >> >> You use the hilitedLine property to determine which line the user clicked. >> The field's hilitedLine is set to the new line before the mouseDown message >> is sent, so there is no way to determine the previously-selected line. _______________________________________________ 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
