Mark, re Inspector and custom property names with commas:
> I agree its an annoyance - and is something which is resolvable
1. Great news! Because that code/data reality is hard to avoid:
- EVERY shipping LC app's stack has cRevStandaloneSettings ...
- If the IDE or app has build glitches, we
Indeed you can indirect through a variable - but you can’t do, e.g:
get the foo,bar,baz of me
Which was my point :)
Warmest Regards,
Mark.
P.S. Of course an obvious syntactic extension would be allowing quoting of the
property keyword: the “foo,bar,baz” of me.
Sent from my iPhone
> On 5
Mark:
> to access your custom properties with `the X of` syntax -
> it is *this* kind of access which is *not* possible
> if the custom property name is not an identifier
Discussion is perception - Code is reality:
put "I,love,commas*etc" into X
set the X of me to "Hi, Mark!"
answer
On 2023-11-03 20:21, Paul Dupuis via use-livecode wrote:
You do make a good point about the documentation regarding custom
properties. Assuming people read the documentation. At the same time,
you used to be able to use commas in custom property names. As Curry
noted, Livecode even used to use
Hi Paul,
I forgot to add handler
editorUpdate
to the list that needs a
"set the itemDelimiter to tab"
Kind regards
Bernd
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
Hi Paul,
I looked a bit further into the problem with commas in key names of custom
properties.
It turns out that the widget "treeview" has the option to choose a delimiter
for paths. Default is comma.
If you feel adventurous you could hack the properties inspector fairly easily
to work with
Hi Bernd,
You do make a good point about the documentation regarding custom
properties. Assuming people read the documentation. At the same time,
you used to be able to use commas in custom property names. As Curry
noted, Livecode even used to use them in the standalone setting
properties,
Bernd:
> "Livecode User Guide" 9.6.10 - Custom Property Names
> any combination of letters, digits, and underscores
> treeview could not expect a comma in a customproperty name.
Hi Y'all,
Anyone ever hear of the cRevStandaloneSettings?
Wonderful (official) prop set ... especially all
Hi Paul,
The problem with the comma in a customproperty name in the Properties Inspector
(PI) arises because the PI uses a treeview to display the customproperties.
More specifically the "hilitedElement" to retrieve the current selection and
"hilitedElement" has the form:
"A comma delimited
ok, let's see. you got me distracted from real work:
if you're following along at home, in real time, look in
toolset->palettes->inspector->editors->com.livecode.pi.customprops.behavior.livecodescript
On Thu, Nov 2, 2023 at 6:02 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com>
no, but, i started to write a wiki on the PI/PE, which might help you to
get started in your search:
https://github.com/macMikey/LC-HACK/wiki/Property-Inspector
On Thu, Nov 2, 2023 at 6:02 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:
> This bug
This bug (https://quality.livecode.com/show_bug.cgi?id=23512) where a
comma in the key name of an array prevents the Proerty Inspector from
being able to edit the property just bit me again.
I have a stack (for help) that extensively uses keys with commas (create
prior to the Project Browser
12 matches
Mail list logo
