That is a really silly problem which meant that I had to set 12 custom
props 4 times before I worked
out how to do something that should be rather more intuitive.
Richmond.
On 17/7/2018 5:51 pm, Bob Sneidar via use-livecode wrote:
You may be referring to the issue when setting the value of a custom prop, if
you click away, like to another stack or tool after editing in the value field,
the prop will not retain the value you entered. Also clicking on another
property will not retain the value. You have to tab out or click some other
object in the property inspector. I've gotten into the habit of always tabbing
out of the value field. This is the same for creating datagrid columns, which
suffers from many of the same anomalies.
Bob S
On Jul 17, 2018, at 03:59 , Curry Kenworthy via use-livecode
<use-livecode@lists.runrev.com> wrote:
There's another custom prop editor bug (an actual bug that makes it easy to
lose the edited text) but I forget the trigger until I work with it again.
Best wishes,
Curry Kenworthy
_______________________________________________
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
