Hi all,
Attempting to update one of my components with a new method and getting an
inscrutable error when I added. The component compiled with no problem when
converted from 15 r5. The error is:
General error: "4D method and variable have the same name?"
Been through all the code and there's no
Hi Chip,
Here's the pseudocode:
Create a 4d method mySortMethod
GET MACRO PARAMETER highlighted text
Parse returned text to text array with substring using CR as delimiter
Sort array
Rebuild method text from array: For(1;$element;size of array())+CR
SET MACRO PARAMETER highlighted text
Then in y
Dave,
Along those lines, objects have made passing long parameter lists to
methods a joy. 8 parameters => 1 object with 8 attributes, optional
parameters don't have to be at the end, etc.
Another trick: create constants for object attributes of commonly used
objects, to wit:
Constants Theme: Use
Hi Dave,
Yeah, something seems squirrely with the v16 compiler. I just posted about
an error on a component which compiles fine in 15r5, but now generates a
"4d method and variable with same name" error (and of course you can't find
out the name of said conflict, which btw does not exist in review
Hi David,
Thanks for asking about my old components - good timing. All my components
(including ones never for sale) are v16 ready, and I've been looking to
upload them as open source once I figured out the right repository. Most
have been kept up to date & debugged, although Freedom of Choice (my
ethod that you wish to sort.
>
> – Call the Macro -- SortMethod -- from the macro dropdown list that is
> part of the method editor.
>
> – Boom, the method is sorted.
>
>
> *** * ** ** *******
> ******
So, trying to compile a component in v16 and getting repeated error:
0: A method and a variable have the same name: ?
I generally keep my components in the 4D application folder Components.
Unhelpfully, 4D doesn't tell what the conflict is. Oh, and there's no
variable which conflicts with a meth
he component you are compiling call any other components?
>
> On Sat, Jun 3, 2017 at 12:31 PM, Bob Finnerty via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
>
> > So, trying to compile a component in v16 and getting repeated error:
> >
> > 0: A method and a variable h
Kirk,
I've been growing my constants list exponentially for this very reason.
Since object attributes are case sensitive, the opportunity for maddening
bugs is high. Attribute name constants eliminate this. I group them with a
prefix for easy typeahead and code clarity ("PREF Save error to log att
Kirk,
First of all, 4D has now released the source of its components such as
4DPop, so your on your own for debugging.
On my component compiling error, I think the problem is thus:
My Compiler folder next to the 4D app is where I keep the critters. Being
lazy, I put the 4DPop components interpre
Hi Folks
Using 4D 18 r4 windows. Working great until recently; then suddenly lost
the ability to autocomplete constants - both 4D and custom - in the method
editor. Commands, methods & macros still autocomplete. Constants tokenize
properly when full name entered.
Any idea what's up & how to fix?
ed by d4:groupName.
>
> 2021/01/19 4:33、Bob Finnerty via 4D_Tech <4d_tech@lists.4d.com 4d_tech@lists.4d.com>>のメール:
> And BTW, anyone point me to the xlf definition for a constants file (or
> have a blank)?
> **
Been using the new var compiler declarations extensively, which work well
in interpreted mode, but won't compile (tried in several components). This
was in R4, haven't tried yet in R5
Also, in 18 R4 using var on parameters generated a (nonsensical) error.
Just noted that this is fixed in R5, howev
13 matches
Mail list logo
