Re: Control properties not included in the Property Inspector

There are no tabs or clear delimiters that I could tell, at least not when scraped from the web page. I tried to paste into a spreadsheet then do text to columns, but there are no clear delimiters. No biggie it's nice to have a list to look through. Bob S > On Nov 6, 2017, at 20:03 , Brian

Re: Control properties not included in the Property Inspector

Wow... almost looks like you will need to use a script to go through all of those files and ensure the lines each have the correct number of tabs. On Mon, Nov 6, 2017 at 5:33 PM Monte Goulding via use-livecode < use-livecode@lists.runrev.com> wrote: > > I did the first bit then realised that the

Re: Control properties not included in the Property Inspector

Funny that I was just looking at the code that loaded these files but had not gotten to look for them yet. On Mon, Nov 6, 2017 at 4:13 PM Monte Goulding via use-livecode < use-livecode@lists.runrev.com> wrote: > > > On 7 Nov 2017, at 8:47 am, Phil Davis via use-livecode < >

Re: Control properties not included in the Property Inspector

> On 7 Nov 2017, at 1:15 pm, Richard Gaskin via use-livecode > wrote: > > Doesn't the PI rely on that? No, the PI uses the file I linked to earlier which also tells it various other things like custom getter and setter handlers, default values, the type of

Re: Control properties not included in the Property Inspector

Monte Goulding wrote: >> On 7 Nov 2017, at 12:20 pm, Richard Gaskin via use-livecode wrote: >> >> If an enhancement request is filed I'd prefer it be for an optional >> modifier to the existing function syntax, rather than littering the >> current function results with synonyms or

Re: Control properties not included in the Property Inspector

> On 7 Nov 2017, at 12:20 pm, Richard Gaskin via use-livecode > wrote: > > If an enhancement request is filed I'd prefer it be for an optional modifier > to the existing function syntax, rather than littering the current function > results with synonyms or

Re: Control properties not included in the Property Inspector

On 11/06/2017 05:20 PM, Richard Gaskin via use-livecode wrote: The properties function was designed to allow one-step transformations of objects. Without it, the old-school way is "set the of something to " over and over for every property value being changed. OK. Point taken. But the

Re: Control properties not included in the Property Inspector

Mark Wieder wrote: > > I've never liked the idea of hiding things from users. > Ideally you might want to show groups of properties contextually, but > the idea that there are properties that exist but you can't get to > them just does.not.seem.right. > The properties function was designed to

Re: Control properties not included in the Property Inspector

> On 7 Nov 2017, at 10:27 am, Mark Wieder via use-livecode > wrote: > > Wow. That's unreadable. Yes… it turns out that GitHub will prettify it for us if we change the extension to .tsv and fiddle with the files a bit.

Re: Control properties not included in the Property Inspector

On 11/06/2017 02:12 PM, Monte Goulding via use-livecode wrote: Not all properties are in the properties array. The properties array is only read/write properties and not that duplicate info from other properties. For example it only includes htmlText not rtfText, text & styledText. You may

Re: Control properties not included in the Property Inspector

> On 7 Nov 2017, at 8:47 am, Phil Davis via use-livecode > wrote: > > That will give you all the keys of the properties array, but keep in mind > that a few of the properties may be arrays themselves. Not all properties are in the properties array. The

Re: Control properties not included in the Property Inspector

put the properties of into tProps On 11/6/17 1:47 PM, Phil Davis via use-livecode wrote: Try: put the properties of field "fldCustID" into tProps put the keys of tProps That will give you all the keys of the properties array, but keep in mind that a few of the properties may be arrays

Re: Control properties not included in the Property Inspector

Try: put the properties of field "fldCustID" into tProps put the keys of tProps That will give you all the keys of the properties array, but keep in mind that a few of the properties may be arrays themselves. Phil Davis On 11/6/17 1:14 PM, Alejandro Tejada via use-livecode wrote: Bob

Re: Control properties not included in the Property Inspector

Bob Sneidar wrote: > put the Properties of field "fldCustID" into tProps;put printKeys(tProps) The Message Box produces an error: Object does not exists Hint: fldCustID Al On Mon, Nov 6, 2017 at 3:31 PM, Alejandro Tejada wrote: > > Hi All, > > Where could I find a list

Re: Control properties not included in the Property Inspector

put the Properties of field "fldCustID" into tProps;put printKeys(tProps) Bob S > On Nov 6, 2017, at 12:31 , Alejandro Tejada via use-livecode > wrote: > > Hi All, > > Where could I find a list of control properties that > are not included within the Property