Re: v17 conundrum in design

2019-02-11 Thread Chuck Miller via 4D_Tech
Been there done that Regards Chuck Chuck Miller Voice: (617) 739-0306 Informed Solutions, Inc. Fax: (617) 232-1064 mailto:cjmillerinformed-solutions.com Brookline, MA 02446 USA

Re: v17 conundrum in design

2019-02-11 Thread Jim Hays via 4D_Tech
Chuck, I've seen some cases where I put a break point in a method that was called repeatedly. I would click on the break point to remove it in the debugger, but it would still stop there. I solved it by: - click to remove the break point - click again, adding it back - click again to remove it

Re: v17 conundrum in design

2019-02-10 Thread ADeeg via 4D_Tech
4D Tech mailing list wrote > Hi All, > > I have an object method that shows no break points either in the method or > when I show break points, yet it continues to stop at a particular line of > code and it is annoying. Any ideas out there what it might be. > > Thanks and regards > Chuck Chuck

Re: v17 conundrum in design

2019-02-10 Thread Kirk Brooks via 4D_Tech
I worked on a project that did this too. In that case it turned out to be an error in some old ALP code. Something subtle like a mistyped variable. You may have a component or plugin that's generating the error silently. On Thu, Feb 7, 2019 at 12:52 PM Chuck Miller via 4D_Tech <

Re: v17 conundrum in design

2019-02-09 Thread Jeremy French via 4D_Tech
Using the Runtime Explorer window, ave you tried clicking "Delete All" for Break and Catch, even if no breaks or catches are listed? > On Feb 7, 2019, at 3:39 PM, Chuck Miller via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > no break points either in the method or when I show break points, yet

Re: v17 conundrum in design

2019-02-08 Thread Keith Goebel via 4D_Tech
Chuck, I have encountered this a few times since at least v15 (now using v17.0 HF3). The only way I found to clear it is to - create a new method - copy the code across - delete old method I found it impossible to “make it happen” for a reproducible bug for 4D, though I did report it anyway (a

Re: v17 conundrum in design

2019-02-08 Thread Chuck Miller via 4D_Tech
No it is not and I have quite and restarted many times Regards Chuck Chuck Miller Voice: (617) 739-0306 Informed Solutions, Inc. Fax: (617) 232-1064 mailto:cjmillerinformed-solutions.com

Re: v17 conundrum in design

2019-02-08 Thread Koen Van Hooreweghe via 4D_Tech
Hi Chuck, Is it happening on a line of code which is split up in several lines ('\')? I've seen this happening a number of times. Mainly quitting and restarting 4D is enhough to solve this issue. You might try to remove the slash chars, set a breakpoint at the remaining line and remove it right

Re: v17 conundrum in design

2019-02-07 Thread Alberto Bachler via 4D_Tech
Chuck I experienced this behavior from time to time since v16r2 (and maybe even v15) I believe can happen when 2 or more instances of 4D are running at the same time Last time was yesterday (macOS) I restarted my Mac and everything came back to normality Cordialmente, Alberto > El

Re: v17 conundrum in design

2019-02-07 Thread Chuck Miller via 4D_Tech
Thanks Steve, I do not think so and the debugger comes up on a NON alp line Regards Chuck Chuck Miller Voice: (617) 739-0306 Informed Solutions, Inc. Fax: (617) 232-1064

RE: v17 conundrum in design

2019-02-07 Thread Stephen J. Orth via 4D_Tech
com> On Behalf Of Charles Miller via 4D_Tech Sent: Thursday, February 7, 2019 3:24 PM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc: Charles Miller Subject: Re: v17 conundrum in design Nope it is filling arrays and then updating ALP. After tabbing out of query field Chuck On Thu, Feb 7, 201

Re: v17 conundrum in design

2019-02-07 Thread Douglas von Roeder via 4D_Tech
Chuck: ALP will go into trace mode when there's an error in a plugin call. Common reasons for that happening - you've executed a plugin call that's a function but haven't added the code to receive the return value or moving code that was using a local ($eList) to code that is using, a process

RE: v17 conundrum in design

2019-02-07 Thread Drew Waddell via 4D_Tech
19 4:24 PM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc: Charles Miller Subject: Re: v17 conundrum in design Nope it is filling arrays and then updating ALP. After tabbing out of query field Chuck On Thu, Feb 7, 2019 at 4:15 PM Chip Scheide via 4D_Tech < 4d_tech@lists.4d.com> wrote

Re: v17 conundrum in design

2019-02-07 Thread Chip Scheide via 4D_Tech
is there a trace or break in the query? i.e. Query by Formula where the formula is a method On Thu, 7 Feb 2019 16:24:27 -0500, Charles Miller via 4D_Tech wrote: > Nope it is filling arrays and then updating ALP. After tabbing out of query > field > > Chuck > > On Thu, Feb 7, 2019 at 4:15 PM

Re: v17 conundrum in design

2019-02-07 Thread Charles Miller via 4D_Tech
Nope it is filling arrays and then updating ALP. After tabbing out of query field Chuck On Thu, Feb 7, 2019 at 4:15 PM Chip Scheide via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Chuck > look for a hard break (TRACE) > either in a called component, plugin or method called via EXECUTE > FORMULA >

Re: v17 conundrum in design

2019-02-07 Thread Chip Scheide via 4D_Tech
Chuck look for a hard break (TRACE) either in a called component, plugin or method called via EXECUTE FORMULA On Thu, 7 Feb 2019 16:12:38 -0500, Chip Scheide via 4D_Tech wrote: > Chuck > also I get this sometimes when there is break in a method which is > called via EXECUTE FORMULA >

Re: v17 conundrum in design

2019-02-07 Thread Chip Scheide via 4D_Tech
Chuck also I get this sometimes when there is break in a method which is called via EXECUTE FORMULA especially if the method is called during screen drawing (On display detail) Chip a break in codeOn Thu, 7 Feb 2019 15:39:26 -0500, Chuck Miller via 4D_Tech wrote: > Hi All, > > I have an

Re: v17 conundrum in design

2019-02-07 Thread Charles Miller via 4D_Tech
I already did what you suggest to no avail. I even reccreated code but did use copy and paste On Thu, Feb 7, 2019 at 4:10 PM Chip Scheide via 4D_Tech < 4d_tech@lists.4d.com> wrote: > a break in a component, plug-in > > an oddity... > use runtime explorer to clear all break points > - if it still

Re: v17 conundrum in design

2019-02-07 Thread Chip Scheide via 4D_Tech
a break in a component, plug-in an oddity... use runtime explorer to clear all break points - if it still persists try restart 4D I have seen this in earlier versions too Chip On Thu, 7 Feb 2019 15:39:26 -0500, Chuck Miller via 4D_Tech wrote: > Hi All, > > I have an object method that shows