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 interpreted in there, along with the
compiled components of my own.

This mix causes problems when I recompile a component update. If all the
components in the folder are compiled, no problem; if some are interpreted,
I get the "method=variable name" error, and warnings about duplicate method
names for the component being compiled. Take out the interpreted
components, problem goes away.

So I'm guessing the compiler gets confused with components in mixed
environments. Didn't on prior versions - but perhaps because I was using
4D's compiled 4DPop components



On Sun, Jun 4, 2017 at 8:17 AM, Kirk Brooks via 4D_Tech <
[email protected]> wrote:

> Nigel,
>
> On Sun, Jun 4, 2017 at 6:15 AM, Nigel Greenlee via 4D_Tech <
> [email protected]> wrote:
>
> > ​...
> > so it seems someone at 4D needs to pop in to the pop plugs and fix some
> > things.
> >
> ​Nice.
>
> ​But seriously - why would you ​build an app with 4DPOP in it?
>
> --
> Kirk Brooks
> San Francisco, CA
> =======================
>
> *The only thing necessary for the triumph of evil is for good men to do
> nothing.*
>
> *- Edmund Burke*
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************
>



-- 
Bob Finnerty
*Exodus Software*
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to