The "of me" clause is the way to go. Adding the extra card reference makes it invalid.
If "me" contains:
Code: Select all
group id 2001 of card id 1001 of stack "SomeStack"
...then prepending the object and card reference as shown above would give us this evaluation:
Code: Select all
field "E_B" of card id 1001 of stack "SomeStack" of group id 2001 of card id 1001 of stack "SomeStack"
That will of course generate an "object not found" error.
In general, when constructing object references the expected order is small to large, so putting a card reference before a control reference won't work under any circumstances.
Using "me", "the target", and other functions that return complete object references, there's no need to add anything at all to resolve that object. Here "me" refers to a group, so it will include the card reference as part of its complete descriptor.
So to refer to an object within a group, and given that a complete reference to the group object is already contained in "me", this will be what you'd need:
Setting the location is a second issue here. LC uses absolute coordinates, starting at the upper-left of the card. Being absolute, any DG row group setting one of its controls to a specific absolute location will mean that all rows will be rendered with that control in each of them rendered at the same place on the card. Probably not what you want.
If you want a control within a row group to be placed relative to the row group, you can use something like:
Code: Select all
set the loc of field "E_B" of me to (the left of me + 724),(the top of me + 10)
That will place the center of the field 724 pixels to the left of each row group, and 10 pixels below the top of each row group.
And I'm guessing from those coordinates that perhaps rather than "location" (which is the object's center) you may have meant "topLeft". If so, "topLeft" (or "topRight", "bottomLeft", and "bottomRight" where needed) can be used:
Code: Select all
set the topLeft of field "E_B" of me to (the left of me + 724),(the top of me + 10)