Re: Control properties not included in the Property Inspector

[Bob Sneidar via use-livecode]

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 Milby via use-livecode 
>  wrote:
> 
> 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.


___
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

Re: Control properties not included in the Property Inspector

[Brian Milby via use-livecode]

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 few minutes I had today were
> not enough to do the fiddling with the files part + code changes to support
> changed file formats. I’m well behind this sprint ;-(
>
> https://github.com/livecode/livecode-ide/pull/1823 <
> https://github.com/livecode/livecode-ide/pull/1823>
>
> Cheers
>
> Monte
>
___
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

Re: Control properties not included in the Property Inspector

[Brian Milby via use-livecode]

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 <
> use-livecode@lists.runrev.com> 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 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 want to refer here for inspiration:
>
>
> https://github.com/livecode/livecode-ide/blob/develop/Toolset/resources/supporting_files/property_definitions/propertyInfo.txt
> <
> https://github.com/livecode/livecode-ide/blob/develop/Toolset/resources/supporting_files/property_definitions/propertyInfo.txt
> >
>
> Cheers
>
> Monte
> ___
> 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

Re: Control properties not included in the Property Inspector

[Monte Goulding via use-livecode]

> 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 
editor required etc

https://github.com/livecode/livecode-ide/blob/develop/Toolset/resources/supporting_files/property_definitions/propertyInfo.txt
 


Cheers

Monte
___
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

Re: Control properties not included in the Property Inspector

[Richard Gaskin via use-livecode]

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 subset-value props that
>> aren't needed for automating property assignment.
>
> Hmm.. I must have got lost along the way here. I thought we were
> discussing properties missing from the PI rather than from the
> properties property.

Might have been.  Easy enough to make a PI that it doesn't seem to be 
worth talking about much.


Provided the things one would want to set can be obtain from the 
properties function.


Doesn't the PI rely on that?

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
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

Re: Control properties not included in the Property Inspector

[Monte Goulding via use-livecode]

> 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 subset-value props that aren't needed for automating 
> property assignment.

Hmm.. I must have got lost along the way here. I thought we were discussing 
properties missing from the PI rather than from the properties property. 

Cheers

Monte
___
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

Re: Control properties not included in the Property Inspector

[Mark Wieder via use-livecode]

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 OP's point is that there are properties of 
objects that aren't obvious unless you already know to look for them. I 
believe Pete Haworth went through the exercise a while back of trying to 
identify all the properties (writable or not) of an object and it's not 
a straightforward thing.


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 subset-value props that aren't 
needed for automating property assignment.


Maybe "the full properties of..."?


Yeah, that was my thought as well, even before you brought up the 
one-step transformation thing. I'd support that, and it would be much 
easier than having to parse through the txt file. And keeping track of 
the properties of a given type of object is a maintenance nightmare in 
the legacy engine code.


--
 Mark Wieder
 ahsoftw...@gmail.com

___
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

Re: Control properties not included in the Property Inspector

[Richard Gaskin via use-livecode]

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 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.


It was not designed for learning or documentation.  It was designed 
solely for rapid development.


Hence things like htmlText being there but rtfText not.  The former is a 
tagged textual representation of everything a field can have, while 
rtfText is merely a subset of field elements suitable for certain types 
of import/export.


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 subset-value props that aren't 
needed for automating property assignment.


Maybe "the full properties of..."?

For the intended purpose, I've been quite happy with "the properties" as-is.

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
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

Re: Control properties not included in the Property Inspector

[Monte Goulding via use-livecode]

> 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. 

https://help.github.com/articles/rendering-csv-and-tsv-data/ 


I did the first bit then realised that the few minutes I had today were not 
enough to do the fiddling with the files part + code changes to support changed 
file formats. I’m well behind this sprint ;-(

https://github.com/livecode/livecode-ide/pull/1823 


> 
> But aside from that
> 
> 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.
> http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Control properties not included in the Property Inspector

[Mark Wieder via use-livecode]

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 want to refer here for inspiration:

https://github.com/livecode/livecode-ide/blob/develop/Toolset/resources/supporting_files/property_definitions/propertyInfo.txt
 



Wow. That's unreadable.

But aside from that

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.

http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Control properties not included in the Property Inspector

[Monte Goulding via use-livecode]

> 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 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 want to refer here for inspiration:

https://github.com/livecode/livecode-ide/blob/develop/Toolset/resources/supporting_files/property_definitions/propertyInfo.txt
 


Cheers

Monte
___
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

Re: Control properties not included in the Property Inspector

[Phil Davis via use-livecode]

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 themselves.


Phil Davis


On 11/6/17 1:14 PM, Alejandro Tejada via use-livecode wrote:

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 of control properties that
are not included within the Property Inspector?

For example:
clipstoRect (a Boolean (true or false) property of groups)
capsStyle (a property of graphics)
joinStyle (a property of graphics)
miterLimit (a property of graphics)
fillRule (a property of graphics)
and others...

Thanks in advance!

  Al

___
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





--
Phil Davis


___
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

Re: Control properties not included in the Property Inspector

[Phil Davis via use-livecode]

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 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 of control properties that
are not included within the Property Inspector?

For example:
clipstoRect (a Boolean (true or false) property of groups)
capsStyle (a property of graphics)
joinStyle (a property of graphics)
miterLimit (a property of graphics)
fillRule (a property of graphics)
and others...

Thanks in advance!

  Al

___
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



--
Phil Davis


___
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

Re: Control properties not included in the Property Inspector

[Alejandro Tejada via use-livecode]

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 of control properties that
> are not included within the Property Inspector?
>
> For example:
> clipstoRect (a Boolean (true or false) property of groups)
> capsStyle (a property of graphics)
> joinStyle (a property of graphics)
> miterLimit (a property of graphics)
> fillRule (a property of graphics)
> and others...
>
> Thanks in advance!
>
>  Al
___
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

Re: Control properties not included in the Property Inspector

[Bob Sneidar via use-livecode]

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 Inspector?
> 
> For example:
> clipstoRect (a Boolean (true or false) property of groups)
> capsStyle (a property of graphics)
> joinStyle (a property of graphics)
> miterLimit (a property of graphics)
> fillRule (a property of graphics)
> and others...
> 
> Thanks in advance!
> 
> Al
> ___
> 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