So creating a new list field (with the same script as the old one) and deleting the old list field did the trick. I don't know what field property setting that I was unaware of caused this problem. AFAIK, there should be no field property that blocks a list field from getting arrowkey messages, but something was doing it…. Anyway, problem solved.
-- Peter Peter M. Brigham pmb...@gmail.com http://home.comcast.net/~pmbrig On Jul 21, 2015, at 11:26 AM, Dr. Hawkins wrote: > Foolish question, but have you tried creating a new field from scratch, > pasting the script, and seeing if that works? > > I've had to do that a couple for times when some exotic and non-displayed > property or another got set. > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > _______________________________________________ > 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 _______________________________________________ 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
