This will also reset window coordinates of design environment to default, so if
you have a method that has opened off screen (Previously on a second monitor,
holding shit key down will reset to default
Regards
Chuck
Chuck Miller Voice: (617) 739-0306
Informed Solutions, Inc. Fax: (617) 232-1064
mailto:cjmillerinformed-solutions.com
Brookline, MA 02446 USA Registered 4D Developer
Providers of 4D and Sybase connectivity
http://www.informed-solutions.com
This message and any attached documents contain information which may be
confidential, subject to privilege or exempt from disclosure under applicable
law. These materials are intended only for the use of the intended recipient.
If you are not the intended recipient of this transmission, you are hereby
notified that any distribution, disclosure, printing, copying, storage,
modification or the taking of any action in reliance upon this transmission is
strictly prohibited. Delivery of this message to any person other than the
intended recipient shall not compromise or waive such confidentiality,
privilege or exemption from disclosure as to this communication.
> On Nov 17, 2019, at 8:39 AM, Jim Hays via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> (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 Prefe
