Re: Custom property retrieval incorrect

On 2023-04-27 23:32, J. Landman Gay via use-livecode wrote: Those are exactly the two values I get too. The earliest version of LC I currently have installed is 9.6.7 and it happens there and in three newer versions after that. A custom property named "cVers" works okay. But I've

Re: Custom property retrieval incorrect

Well... ;-) Thanks for tracking it down, Mark. I'm not crazy after all. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com

Re: Custom property retrieval incorrect

Those are exactly the two values I get too. The earliest version of LC I currently have installed is 9.6.7 and it happens there and in three newer versions after that. A custom property named "cVers" works okay. But I've been using "cVersion" for years and years, so not

Re: Custom property retrieval incorrect

there's no workaround other than not using the cVersion custom property. -- 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

Re: Custom property retrieval incorrect

s shown in an About stack. In LC 9.6.7, 9.6.9, and > 10.0.0 dp 5 the custom property is returned incorrectly. > > I set the cVersion of the stack to 3.0.0 in the property inspector and also > tried from the message box and from a handler. In both the message box and in > a sc

Re: Custom property retrieval incorrect

set cVersion. > Am 27.04.2023 um 21:50 schrieb J. Landman Gay via use-livecode > : > > I have a custom stack property called "cVersion" that is used to determine > update availability and is shown in an About stack. In LC 9.6.7, 9.6.9, and > 10.0.0 dp 5 the

Re: Custom property retrieval incorrect

On 4/27/23 12:50, J. Landman Gay via use-livecode wrote: Anyone seen this? Is there something special about a custom prop named "cVersion"? This used to work fine, but that was about 2 years ago. Verified here. cVersion is weird. I get 1.0.4 on all stacks. I put all the properties for update

Re: Custom property retrieval incorrect

stack. In LC 9.6.7, 9.6.9, and > 10.0.0 dp 5 the custom property is returned incorrectly. > > I set the cVersion of the stack to 3.0.0 in the property inspector and also > tried from the message box and from a handler. In both the message box and in > a script it returns 3.0.9. I saved t

Custom property retrieval incorrect

I have a custom stack property called "cVersion" that is used to determine update availability and is shown in an About stack. In LC 9.6.7, 9.6.9, and 10.0.0 dp 5 the custom property is returned incorrectly. I set the cVersion of the stack to 3.0.0 in the property inspector and also

Re: [LCB]custom property editor

dle widgets have custom property editors bundled with them in > their /editors folder. unfortunately, i cannot find any documentation on > how to do this. i'm assuming we would use a metadata variant, but of course > there does not seem to be any documentation on how to do that. i have tried

[LCB]custom property editor

the megabundle widgets have custom property editors bundled with them in their /editors folder. unfortunately, i cannot find any documentation on how to do this. i'm assuming we would use a metadata variant, but of course there does not seem to be any documentation on how to do that. i have tried

RE: Finding out what changes a custom property

...@evergreeninfo.net -Original Message- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Bob Sneidar via use-livecode Sent: Monday, June 07, 2021 11:12 AM To: How to use LiveCode Cc: Bob Sneidar Subject: Re: Finding out what changes a custom property Oooh never thought

Re: Finding out what changes a custom property

Oooh never thought of that... so setprops get called before a property gets set? Bob S > On Jun 6, 2021, at 14:10 , Curry Kenworthy via use-livecode > wrote: > > > Paul: > > > Is there an debugger feature or tip or trick anyone has > > that can do the equivalent of set a break point when

Re: Finding out what changes a custom property

Hi Paul, In the development menu, open 'message watcher'. That's helped me with exactly what you are looking for too. Fantastic tool. Sean On Sun, 6 Jun 2021 at 21:21, Paul Dupuis via use-livecode < use-livecode@lists.runrev.com> wrote: > I have a stack with a custom property

Re: Finding out what changes a custom property

Paul: > Is there an debugger feature or tip or trick anyone has > that can do the equivalent of set a break point when a property > is changed and let me see the executionContexts > to tell what the heck is changing it! Add a setprop with either a breakpoint and/or the executionContexts?

Finding out what changes a custom property

I have a stack with a custom property, hrStart. Somewhere is miles of code and messages flying everywhere, something is changing it that shouldn't. Is there an debugger feature or tip or trick anyone has that can do teh equivalent of set a break point when a property is changed and let me

Re: "template" stack in custom property

Hi guys, > Am 03.08.2019 um 17:19 schrieb Paul Dupuis via use-livecode > : > On 8/2/2019 10:33 PM, ambassador--- via use-livecode wrote: >> What are the advantage of instantiating the new stack from data in a prop >> rather than by cloning a substack? > That was my question too. well the first

Re: "template" stack in custom property

On 8/2/2019 10:33 PM, ambassador--- via use-livecode wrote: What are the advantage of instantiating the new stack from data in a prop rather than by cloning a substack? That was my question too. It is a very different way of storing a stack. I imagine that an: open invisible stack (the

Re: "template" stack in custom property

What are the advantage of instantiating the new stack from data in a prop rather than by cloning a substack? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription

Re: "template" stack in custom property

> no, I don't think so, because LC obviously neglects the rest of the script > but ONLY if the stack-to-be-opened has a pre-/openstack handler. > > Works if I add -> lock messages! > > And this only happens when I open a stack from within a custom property. > If I do the same with

Re: "template" stack in custom property

only happens when I open a stack from within a custom property. If I do the same with a stack from my HD, everything works as exspected, so it does not sound like LC is not finding "the defaultstack". > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActi

Re: "template" stack in custom property

major-k via use-livecode : Hi friends, I have done this a lot in the past, but currently got stuck with this in LC 9.5 I store a stack in a custom property and open it via script like: ... put "NewJob_" & the seconds into tName lock messages ## Now every line in the handler is

Re: "template" stack in custom property

a use-livecode >> : >> >> Hi friends, >> >> I have done this a lot in the past, but currently got stuck with this in LC >> 9.5 >> I store a stack in a custom property and open it via script like: >> ... >> put "NewJob_" & the seco

Re: "template" stack in custom property

Hi all, I found a workaround by creating two handlers and use them with a little dealy. > Am 02.08.2019 um 14:59 schrieb Klaus major-k via use-livecode > : > > Hi friends, > > I have done this a lot in the past, but currently got stuck with this in LC > 9.5 > I s

"template" stack in custom property

Hi friends, I have done this a lot in the past, but currently got stuck with this in LC 9.5 I store a stack in a custom property and open it via script like: ... put "NewJob_" & the seconds into tName go invisible stack (the cTemplateStack of this stack) ## Works so

Re: Never, ever use the name of a built-in property as a custom property

On Mon, Jan 28, 2019 at 11:49 AM Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > Yet even there you did a great job of rethinking the thing that handles > the data, leaving the data free to be as free as data often is. > Thanks! It was a pain to format, but my

Re: Never, ever use the name of a built-in property as a custom property

Geoff Canyon wrote: > Sure, I'm not arguing for custom property sets -- just saying that if > you *are* going to use them, don't bork the naming convention. Names of prop sets, or the names of keys within a set? On the latter I have mixed feelings. As you know, I have rather a fetish

Re: Never, ever use the name of a built-in property as a custom property

I mean to say the first (and only I am sorry to say) Revolution conference I attended. That sounded like I put on a conference myself. :-) Bob S > On Jan 28, 2019, at 08:02 , Bob Sneidar via use-livecode > wrote: > > This was addressed in my first Revolution conference.

Re: Never, ever use the name of a built-in property as a custom property

This was addressed in my first Revolution conference. One of the classes was about naming conventions. Not only do you have to be careful about your names clashing with built-in names, but also reserved words, and the names used by OTHER developers (think plugins). Other languages partially

Re: Never, ever use the name of a built-in property as a custom property

, 27 Jan 2019 at 17:01, Geoff Canyon via use-livecode < use-livecode@lists.runrev.com> wrote: > Sure, I'm not arguing for custom property sets -- just saying that if you > *are* going to use them, don't bork the naming convention. > ___

Re: Never, ever use the name of a built-in property as a custom property

Sure, I'm not arguing for custom property sets -- just saying that if you *are* going to use them, don't bork the naming convention. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage

Re: Never, ever use the name of a built-in property as a custom property

Hi Geoff, for me the solution is to have a naming convention for all of a developers / projects work - so everything is prefixed by 4 letters, and then in the case of custom properties / custom property sets - to migrate off them and just stick to arrays. The custom property / set syntax

Never, ever use the name of a built-in property as a custom property

https://github.com/gcanyon/navigator/issues/27 I just found that Navigator breaks when editing the custom properties of datagrids, because of the custom property dgProps["style"]. When I originally added custom properties to the property editor in Navigator it was simple: I pretty much

Re: Custom Property

Thanks! :-) Actually there’s no pain . . . it’s easy to work around. I was just curious why a stack I’m playing with from dev@livecode exhibits this problem. Roger > On Dec 21, 2017, at 9:58 AM, Richmond Mathewson via use-livecode > wrote: > > "Sacrifice" . .

Re: Custom Property

"Sacrifice" . . . I wasn't really complaining; just "laughing with you" as they say. I feel your pain 8-) Richmond. On 21/12/17 6:17 pm, Roger Guay via use-livecode wrote: So sorry for your sacrifice, Richmond!! 1. I didn’t ask you specifically to do any testing. 2. You have no idea how

Re: Custom Property

So sorry for your sacrifice, Richmond!! 1. I didn’t ask you specifically to do any testing. 2. You have no idea how much testing I did, nor the nature of it Roger > On Dec 21, 2017, at 2:30 AM, Richmond Mathewson via use-livecode > wrote: > > 1. Obviously

Re: Custom Property

s > > Monte > >> On 21 Dec 2017, at 5:22 pm, Roger Guay via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> Please, how is it that a graphic can have a custom property that does not >> show up in the property in

Re: Custom Property

again: In the 8.1.8 Property Inspector GRUNT showed up in the Custom Properties section. ---- So: 1. You have failed to set the Custom property. 2. Possibly (?) setting the Custom property AFTER setting the Behavior doesn't work. In LC 8.1.8 I setup

Re: Custom Property

Hi Roger If you could create a bug report with a stack containing the offending graphic that would be helpful Cheers Monte > On 21 Dec 2017, at 5:22 pm, Roger Guay via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Please, how is it that a graphic can have

Custom Property

Please, how is it that a graphic can have a custom property that does not show up in the property inspector? Does the fact that the graphic has a behavior have anything to do with it? TFYH, Roger ___ use-livecode mailing list use-livecode

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

> Richard H. wrote: > I'm also bothered by *not* being able to use a text literal in quotes; > I'm generally vary careful about declared variables, etc. (I'd really > like an option to enforce case in variable names!) on mouseUp put "hello" into p1 put quote&"hello" into p2 set the p1 of me

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

On Tue, Aug 8, 2017 at 8:56 AM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > > Years ago I knew a woman who wanted to use special characters on her mac > for file names which were perfectly legal with HFS, but NOT legal for NTFS. > When we moved her files to a Windows

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

On Tue, Aug 8, 2017 at 8:33 AM, Mark Waddingham via use-livecode < use-livecode@lists.runrev.com> wrote: > On 2017-08-08 17:25, J. Landman Gay via use-livecode wrote: > >> The answer to the first case is "don't do that". Use a different >> variable name for the local. >> > > Well, yes, that is

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

On 08/08/2017 08:56 AM, Bob Sneidar via use-livecode wrote: Again, don't do that. Years ago I knew a woman who wanted to use special characters on her mac for file names which were perfectly legal with HFS, but NOT legal for NTFS. When we moved her files to a Windows share, some of her files,

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

unctuation in a property name is a good idea? Is there any use case where punctuation in a variable name is a good idea? ;) As a custom property set is an unconstrained array; you can actually have custom properties which have any string as key (set via the customProperties property) - so

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

I agree here with Mark that this is an oversight, an aberration. It should't work the way it presently does, and I would not count on it being this way forever. Some other issue may arise in the future requiring someone to "fix this" and your code will break. Swim away from the other fish if

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

On 2017-08-08 17:49, hh via use-livecode wrote: From a viewpoint of the "get property /set property" syntax "unexpected results" sounds convincing here, but, TMHO, it is exactly what I would expect from a **viewpoint of array syntax**. on mouseUp local catness put "minimal" into catness

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

On 08/08/2017 08:49 AM, hh via use-livecode wrote: JLG wrote: In what circumstance would it be necessary to quote the property name? Use "&" in a key, for example the "G" of me Is there any use case where punctuation in a property name is a good idea? -- Mark Wieder ahsoftw...@gmail.com

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

Again, don't do that. Years ago I knew a woman who wanted to use special characters on her mac for file names which were perfectly legal with HFS, but NOT legal for NTFS. When we moved her files to a Windows share, some of her files, though visible, were inaccessible. (Why Windows even

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

On 2017-08-08 17:46, Bob Sneidar via use-livecode wrote: famous last words. :-) Indeed - perhaps a slight case of over-optimism on my part... :'( Mark. -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Everyone can create apps

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

> JLG wrote: > In what circumstance would it be necessary to quote the property name? Use "&" in a key, for example the "G" of me > Mark wrote: > What doesn't work at the moment is if you have a var name which is > quoted: > > local catness > put "minimal" into catness > set the "catness" of

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

famous last words. :-) Bob S > On Aug 8, 2017, at 08:15 , Mark Waddingham via use-livecode > wrote: > > I think the latter is probably something which is unlikely to hurt anyone if > tweaked though... > > Warmest Regards, > > Mark. >

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

On 2017-08-08 17:33, Mark Waddingham via use-livecode wrote: (Of course, I'm now going to go off and see if you can use quoted variables in other places - I bet that's going to a 50/50 chance in every place!) Okay - so: the of ... Is the *only* place where a check to make sure something

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

rcumstance would it be necessary to quote the property name? The original case Dr Hawkins encountered was something along the lines of: local someVar put 100 into someVar put the someVar of me Here, this will fetch the custom property '100'. Ideally you'd be able to do put the "someVar" of

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

case Dr Hawkins encountered was something along the lines of: local someVar put 100 into someVar put the someVar of me Here, this will fetch the custom property '100'. Ideally you'd be able to do put the "someVar" of me Instead - the quoting indicating you want to use that *literal* v

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

the custom property '100'. Ideally you'd be able to do put the "someVar" of me Instead - the quoting indicating you want to use that *literal* value for the property name, instead of the variables context. Another case is wanting to fetch custom property names which contain chars

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

In what circumstance would it be necessary to quote the property name? On August 8, 2017 6:05:21 AM Mark Waddingham via use-livecode wrote: What doesn't work at the moment is if you have a var name which is quoted: local catness put "minimal" into

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

& cp[8.1] &" : "& cp[8+1/10] Test and then interchange the first two lines and test again. [b] set "G" of me to "I dreamt to be geometry and trigonometry" put the customProperties of me into cp put cp["G"] So this does work as 'expec

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

Two examples for testing ambiguity. [a] set "8.1" of me to "I dreamt to be quoted" set 8.1 of me to "I dreamt to be 8.2" put the customProperties of me into cp put cp["8.1"] &" : "& cp[8.1] &" : "& cp[8+1/10] Test and then interchange the first two lines and test again. [b] set "G" of

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

On 2017-08-03 05:39, Monte Goulding via use-livecode wrote: Er… why if you know the name wouldn’t you type it unquoted? Are you really suggesting to put any expression there? The property/function ambiguity with `the` will make our heads explode! For the reason Dr Hawkins originally asked

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

about the need to get the constant from another script, until I remembered it's just easier to set a custom property. In fact (I think I've said so before) custom props are a great way to mimic scoped variables, and even constants. For instance all my datagrids have a property tablename containing

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

our heads explode! > If I have a variable "propertyZ", then under current code I *cannot* use set the propertyZ of theThing to 7 to affect the custom property named propertyZ. Allowing quotes would solve this. In my case, I hit this in a "metaprocedure" that runs in

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

> On 3 Aug 2017, at 7:36 am, Mark Waddingham via use-livecode > wrote: > > Of course, if you'd like to file a bug report / enhancement about being able > to do 'the "mycustompropname" of ... - then that is probably the 'future' > much better solution :) Er…

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

> > let´s say a card has a custom property name cMyProp. > > The variable tMyVar contains the word “cMyProp” > > How do i get the value of the custom property using the variable tMyVar? Using the “do” command, a quick test and this works OK: on mouseUp

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

On Wed, Aug 2, 2017 at 2:36 PM, Mark Waddingham via use-livecode < use-livecode@lists.runrev.com> wrote: > You can put the name of the property into a local var and use that (unless > I misunderstood the problem). > That's what I do > > > Of course, if you'd like to file a bug report /

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

You can put the name of the property into a local var and use that (unless I misunderstood the problem). Ali's suggestion is however the very pragmatic one - there are always going to be cases where var names might conflict with other things 'in context' and require disambiguation. (Although

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

A good reason to use consistent prefixes to distinguish custom props and variables perhaps. On Wed, 2 Aug 2017 at 20:56, Dr. Hawkins via use-livecode < use-livecode@lists.runrev.com> wrote: > On Wed, Aug 2, 2017 at 10:25 AM, Klaus major-k via use-livecode < > use-livecode@lists.runrev.com> wrote:

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

On Wed, Aug 2, 2017 at 10:25 AM, Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > > answer the tMyVar of this cd > This is an area that is awkward in live code. The use of unquoted literals for this is inconsistent with most of live code (but quoting would be

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

code >> <use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>>: >> >> Hi, >> >> let´s say a card has a custom property name cMyProp. >> The variable tMyVar contains the word “cMyProp” >> How do i get the value of the custom property

Re: how to get the value of a custom property if the name of the cProperty is in a variable?

Hi Matthias, > Am 02.08.2017 um 19:20 schrieb Matthias Rebbe via use-livecode > <use-livecode@lists.runrev.com>: > > Hi, > > let´s say a card has a custom property name cMyProp. > The variable tMyVar contains the word “cMyProp” > How do i get the value of the cust

how to get the value of a custom property if the name of the cProperty is in a variable?

Hi, let´s say a card has a custom property name cMyProp. The variable tMyVar contains the word “cMyProp” How do i get the value of the custom property using the variable tMyVar? Regards, Matthias Matthias Rebbe +49 5741 31 ‌matthiasrebbe.eu <http://matthiasrebbe

Bizarre problem setting a custom property

From the message box, I type set the autoFitted of group “a” of stack “specs” to false Works as expected. But if I type set the frameOptions of group “a” of stack “specs” to false Fails with this message: Message execution error: Error description: Chunk:

Re: inheriting a custom property from a supergroup ("effective" custom property)

On Wed, Apr 27, 2016 at 5:00 PM, Monte Goulding wrote: > Actually if not being set has value then I don't think you want effective > either. I think you need a property on any parent that should be ignored > when recursing through the hierarchy. > Ack. You're right;that's

Re: inheriting a custom property from a supergroup ("effective" custom property)

Actually if not being set has value then I don't think you want effective either. I think you need a property on any parent that should be ignored when recursing through the hierarchy. Sent from my iPhone > On 28 Apr 2016, at 9:49 AM, Dr. Hawkins wrote: > > I suppose that

inheriting a custom property from a supergroup ("effective" custom property)

I have an id number, call it unDna, for entries in my database. When elements are displayed or manipulated, either the card or the group I've placed has unDna set as a custom property. The handlers for close field check for a unDna of the field or the owner of a field. This backfires, though

Re: setprop handlers for custom property sets

On Jul 30, 2015, at 4:34 PM, Mark Wieder wrote: Paul Dupuis paul@... writes: The LC 6.7.5 dictionary entry for setProp has the following: If the custom property you want to control is in a custom property set, use array notation in the first line of the setProp handler

Re: setprop handlers for custom property sets

Paul Dupuis paul@... writes: On 7/30/2015 4:34 PM, Mark Wieder wrote: Paul Dupuis paul at ... writes: The LC 6.7.5 dictionary entry for setProp has the following: If the custom property you want to control is in a custom property set, use array notation in the first line

Re: setprop handlers for custom property sets

On 7/30/2015 4:34 PM, Mark Wieder wrote: Paul Dupuis paul@... writes: The LC 6.7.5 dictionary entry for setProp has the following: If the custom property you want to control is in a custom property set, use array notation in the first line of the setProp handler, as in the following example

Re: setprop handlers for custom property sets

Paul Dupuis paul@... writes: The LC 6.7.5 dictionary entry for setProp has the following: If the custom property you want to control is in a custom property set, use array notation in the first line of the setProp handler, as in the following example: Interesting. I do see

Re: setprop handlers for custom property sets

notation with my setProp and getProp. I just was having trouble figuring out exactly what the coding should be. I now understand that if I have a custom property set for a stack called mySet and property in mySet called myNumber So if I want a setProp handler to calculate myNumber as the parameter

Re: setprop handlers for custom property sets

On 7/30/2015 6:44 PM, Mark Wieder wrote: Paul Dupuis paul@... writes: it does correctly execute the setProp handler. Much to my surprise. This implies that you can NOT have two custom property sets that have the same property name IF you want to use setprop or getProp handlers with them

Re: setprop handlers for custom property sets

Maybe I'm missing something, but I originally thought the following would cause a recursion error, because the property being set appears within a setProp handler of the same name. Trying this in LC 7.0.5 works, but I still see a warning in the docs about recursion. So does the following work

Re: setprop handlers for custom property sets

Paul Dupuis paul@... writes: it does correctly execute the setProp handler. Much to my surprise. This implies that you can NOT have two custom property sets that have the same property name IF you want to use setprop or getProp handlers with them. No, that's the point of the custom property

Re: setprop handlers for custom property sets

pValue set the propB of me to pValue set the propA of me to pValue * 2 end propB The 1st line of each is okay - setting the actual custom property value in it's own handler will not cause recursion However, the 2nd line will result in run-away recursion

Re: setprop handlers for custom property sets

exactly what the coding should be. I now understand that if I have a custom property set for a stack called mySet and property in mySet called myNumber So if I want a setProp handler to calculate myNumber as the parameter div 100 - for example to convert a percent to a decimal number

Re: setprop handlers for custom property sets

can't have the same setprop/getprop handlers in multiple custom property sets. You *can* have the same properties in multiple sets, though. -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit

setprop handlers for custom property sets

The LC 6.7.5 dictionary entry for setProp has the following: If the custom property you want to control is in a custom property set, use array notation in the first line of the setProp handler, as in the following example: setProp mySet[thisProperty] newValue if thisProperty is that then put

Re: setprop handlers for custom property sets

Paul Dupuis paul@... writes: The recursion issue is of you have a pair (or more) or setProp handlers that call back to one another: ie. Right. There's a special-case trap for that. From the docs: If you use the set command within a setProp control structure to set the same custom property

Expressions as custom property names

Starting a new thread on this. The bug I entered on this has been changed to an enhancement request with a comment from Mark Waddingham that it should be straightforward to implement expressions within parentheses but more investigation needed to see if it could have a broader scope than that.

Delete a single custom property set

Does anybody know how to delete a single custom property set without deleting any others? The documentation mentions setting an object's customPropertySets to empty, but that deletes ALL the customPropertySets. I just want to delete one specific custom property set. Thanks, Ray

RE: Delete a single custom property set

Ray... from the user guide... In LiveCode, there is no command to delete a custom property set. Instead, you place all the custom property set names in a variable, delete the one you don't want from that variable, and set the customPropertySets back to the modified contents of the variable

Re: Delete a single custom property set

. Thanks, Ray On 2/11/2014 8:55 AM, John Dixon wrote: Ray... from the user guide... In LiveCode, there is no command to delete a custom property set. Instead, you place all the custom property set names in a variable, delete the one you don't want from that variable, and set the customPropertySets

Re: Delete a single custom property set

Ray asked: Thanks for this tip. That's really weird though isn't it? It may be helpful to submit a request for that in the Bug DB, something like: delete propertySet propSetName Under the hood it would do what we can do now in script, but it would be much more intuitive. -- Richard

Re: Delete a single custom property set

I'll do that, and I'll also add a request for an intuitive, one-liner way to rename a custom property set, as in set the name of customPropertySet oldName of object objName to newName which is another thing we can currently only do by writing a script. Thanks Richard, Ray On 2/11/2014

Re: Storing a control in a custom property

I've copied this tidbit to the Scripter's Scrapbook. www.ssbk.co.uk Hugh Senior FLCo -- Original message Hi All, After reading this thread, I just keep wondering if this particular tidbit was published before. (and where?) This thread is a useful reminder (at least for me) that I don't

Re: Storing a control in a custom property

I wish that the demo of the scripted library came with a whole bunch of useful snippets for Livecode programmers. Brevity and errors in this email probably the result of being sent by a mobile device. On May 5, 2013, at 3:07 AM, FlexibleLearning.com ad...@flexiblelearning.com wrote: I've

Re: Storing a control in a custom property

The Scripter's Scrapbook download is indeed a 'starter-kit', but it does include a lot of LC/Rev snippets. Hugh Senior FLCo -- Original message From: William Humphrey shoreag...@gmail.com To: How to use LiveCode use-livecode@lists.runrev.com Subject: Re: Storing a control in a custom property

Re: Storing a control in a custom property

: http://runtime-revolution.278305.n4.nabble.com/Storing-a-control-in-a-custom-property-tp4664040p4664234.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit

Re: Storing a control in a custom property

On Mon, Apr 29, 2013 at 5:52 PM, Mike Bonner bonnm...@gmail.com wrote: I was doing this with whole stacks and it works fine. To restore the object, put the cWhereIStoredIt into the clipboarddata[objects] and then paste it. (didn't check dictionary so not positive if objects is correct) Hmm.

Re: Storing a control in a custom property

Can't do it with a stack that is not its own mainstack so you have to make sure any stacks you store this way are set to point to themselves, but I don't see why you couldn't do it. Copy the stack to clipboard (after making sure it is not a sub) pop it out of the clipboard data, encrypt it and

  1   2   3   >