[MEETING] Montreal 4D Club Meeting

[Thierry Daigneault via 4D_Tech]

The next meeting of the Montreal 4D Club will be held Wednesday November 20th 
at 7 PM.


The schedule for the next meeting is as follows:
News
Questions
Presentations
- François Hill will give a demo about a module that manager hierarchical 
listboxes.
End of the meeting

We usually end up at some sort of restaurant after each meeting. Come and join 
us!



Address
---
Softconcept Canada
4378 Av Pierre-De Coubertin (coin Bennett)
Montréal



Anyone can attend. Please note that the meetings are usually held in French.

If you need more information, you can check out our web page at:
http://www.macapa.com/4dmtl 

You can also write to our communications officer:
Thierry Daigneault: tdaignea...@macapa.com 
**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Re: Significant Debugger Window Issue

[Jim Hays via 4D_Tech]

(adding this to an old thread so I can find the answer 2 years from now...)
My structure file was crashing the instant it hit the debugger (v17.2).

Here's how to clear your debugger expression pain:
https://kb.4d.com/assetid=78161

"If by accident an expression is added and saved to the pane that executes
code that causes issue it is possible to clear the expressions by holding
down the *SHIFT* button while the debugger is opened.

After the debugger is opened with the cleared expression pane it is
important to save a new set of expressions or else the next time the
expression pane is opened the last saved set of expression (the one that
were possibly causing issues) will return."

(Click the Save icon)

Also found the answer here from Achim PESCHKE:
https://forums.4d.com/Post/EN/3360111/1/3360112#3368866

The debugger expressions _are_ stored in the structure.  This happened when
I tried the same structure on different machines.


As for v18 Project Mode?  Next to the project folder:
Project
userPreferences.[macOSUserName]
 debuggerWatches.json

So nice!

BTW - I think converting your structure to project mode clears the debugger
pane - not that it helps you if you aren't ready to use project mode.


Jim Hays




On Sat, Aug 24, 2013 at 11:02 PM David Belote 
wrote:

> One last post on this topic from me that I think might help someone else
> who has to delete the 4D preference file and because of it, have to
> reenter the license information.  As noted before, it looked like I was
> going to have to reenter my license information after deleting  the
> corrupted preference file (saved it to a save location), but I think I
> found a way around this.
>
> I initially found that if I started up 4D without any preference file,
> that it started in demo mode.  But if I put the corrupted preference file
> back in place that 4D would start up as usual with my licenses, but of
> course, the debug window wouldn't work properly.
>
> After playing around with it a few times, I found that if I started up 4D
> using the corrupted "4D Preferencesv13.4DPreferences" file that caused the
> debug window not to work correctly, but then deleted that same corrupted
> 4D preferences file while 4D was running, that when I quit 4D, 4D wrote a
> new "4D Preferencesv13.4DPreferences" file.  That new 4D preferences file
> includes the pointers to my license files. Everything is running just like
> it is supposed to.
>
> It makes sense because the corrupted preference file somehow didn't
> contain the correct info to allow the debug window to run, but it did
> contain my license info (and the other required parameters).  So when 4D
> quit and it found that the preference file was missing, 4D wrote the new
> one with the info that was present in the running 4D app.
>
> I verified that this worked by pulling down 4D/About 4D and it contains my
> name and company name.  Then in then pulling down Help/Update License, I
> can see my licenses.
>
> Dave Belote
> Colorado Springs, Colorado USA
>
>
> On 8/23/13 12:23 PM, "Donald Koffman"  wrote:
>
> >I second the thank you. It fixed the same problem on the OC.
> >
> >On Aug 23, 2013, at 9:19 AM, David Belote 
> >wrote:
> >
> >> Miyako, Chip, and all who helped me with this,
> >>
> >> Thanks for using the Show On Disk command.  With it I found the file you
> >> all have been talking about. When I deleted the "4D Preferences
> >> v13.4DPreferences" file (really rename it so 4D couldn't find it), 4D
> >> re-created the preference file and the debug window appears to be back
> >>to
> >> normal.  After deleting the preference file, 4D made me enter the system
> >> as a demo license.  I'll have to go back and reenter my licenses later
> >> today.  Chip alluded to that possibility earlier.
> >>
> >> Again, thanks to all who helped,
> >>
> >> Dave Belote
> >> Colorado Springs, Colorado USA
> >>
> >> P.S.  I hope those of you who are into cycling are enjoying the USA Pro
> >> Challenge (aka Tour of Colorado).  We sure enjoyed watching the Tour de
> >> France.
> >>
> >> On 8/22/13 8:12 PM, "miyako"  wrote:
> >>
> >>> Hello,
> >>>
> >>> just to be clear,
> >>>
> >>> the preferences file is located at
> >>>
> >>> SHOW ON DISK(Get 4D folder+"4D Preferences v13.4DPreferences")
> >>>
> >>> which is an XML file, with keys such as
> >>>
> >>>  >>> height="641"> >>> width="1227" height="0"/> >>> left="1035" top="624" width="186" height="15"/> >>> name="bCtrlD"> >>> height="30"/> >>>top="499"
> >>> width="1227" height="15"/> >>>left="10"
> >>> top="7" width="30" height="21"/> >>> left="45" top="7" width="30" height="21"/> >>> name="bAbortEdit"> >>> height="21"/> >>> width="30" height="21"/> >>> left="150" top="7" width="30" height="21"/> >>> name="bStepOver"> >>> height="21"/> >>>top="7"
> >>> width="30" height="21"/> >>>name="bStepIntoProcess"> >>> left="270" top="7" width="30" height="21"/> >>> name="bStepOut"> >>> height="21"/> >>>top="246"
> >>> width="1227" height="4"/> >>> left="366" top="52" width="