LiveCode Forums

OK, yeah, I guess that's the only solution. Thanks!

In your example, the effects are applied to the group. I'm talking about when the controls have the effect, and the group itself does not. This becomes an issue if you have a group that has some controls with a shadow effect, and others that don't have a shadow. In that case, you can't apply the sha...

Is there a way to get groups to consider the size of effects (eg Drop Shadow, OuterGlow, etc.) of controls? Livecode groups will cut off the shadow effect if the group's margin isn't large enough, and groups don't take any effect size into account. I see that there are a couple feature requests that...

but if I try read from file "/dev/XXXXX" the stack crashes I assume I don't have the correct permissions to read from "/dev/..." etc Have you tried open driver "/dev/XXXXX" for (binary/text) (read/write/update) ? I don't know what the implementation of the open/close driver is under the hood; but t...

Thanks everyone for the suggestions. I tend to agree that the ideal case would be to name everything uniquely. I think the case where this wouldn't be possible is somewhat theoretical. My idea would be something like: I have a set of grouped controls, which functions as a tabbed group. All the code ...

Livecode's normal behavior for referencing controls is to reference the first control (in layer order) that matches. Is there a way (besides using control id) to force livecode to do an exact path match of a reference? Example: I have a group "abc". Inside group "abc", I have two controls: group "de...

Awesome, thanks so much for the help!
Richard, that sounds like great advice regarding variable naming; I'll definitely adopt that convention.

I want to take a field (name or id) as a parameter, and then write into that field. Currently the code looks like this: command writeOutput pField put "Hello" after pField with the call being something like: put the long id of fld "test" into tTest writeOutput tTest However, this just updates the pF...