A problem with clearing fields on marked cards

[stephen barncard]

I don't think you need to 'opt out' the other fields. That would negate the
ease of just checking for some data in the property in your loop. Simplify!

 If it exists, then it is. Otherwise it isn't! "false" is implied in objects
that aren't "branded".

-- inside your loop checking fields:
get the nothingText of stack "mystack"
if it is empty
 then
   next repeat (or whatever)
else
 -- execute something here if there is something in it
end if

On 9 June 2010 11:44, <DunbarX at aol.com> wrote:

> Charles.
>
> Custom properties are very simple and very powerful. They work just like
> any other property.
>
> You just make them up. Write:
>
> set the isLabel of field "yourField" to "true"     --isLabel is the new
> custom property
>
> Then ask:
>
> answer the isLabel of fld "yourField"
>
> You will get "true".
>
> You will set the isLabel of all your other fields to "false". You can do
> this in a script.
>
> This property is separate from the ordinary properties of your fields. For
> example, you might want a locked field in your application for some reason,
> and that would then interfere with your ability to distinguish it from a
> label field.
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>



-- 
-------------------------
Stephen Barncard
San Francisco