Significant Debugger Window Issue

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

Significant Debugger Window Issue

David Belote
The two issues below appear to be interrelated and only affect the 4D 13.1,
13.2, & 13.3 debug window.  They do not affect 4D v12.4.  I submitted this
issue in as a bug on July 16, 2013, but so far it is just listed as "In
Progress".  My problem is that I have not been able to effectively debug my
apps.  I need some way to reset the debug window back to "normal".   I do
not know if the issue affects the Windows OS version of 4D as my work at
this time is only on the latest deployed version of Mac OS X  (OS version
10.8.4).  I am not having any other problems with any other 4D windows or
any other Mac OS X windows.  This problem is confined to the 4D 13.x debug
window.  The 4D Bug is ACI0083025.  I submitted screen snapshots with this
bug report to show graphically show the problem.

1.  In 4D v13.3 (also 13.1 & 13.2) my debug window content and behavior are
incorrect.  The upper pane contains a list of items on the left (Line
Objects, Variables, Constants, Tables & Fields, etc.  There is a column to
the right named "Value".  That column extends as far to the right as the
window is sized.  There is no more information to the right.  The Call Chain
pane and the Express pane are completely missing.  The bottom of the upper
pane is missing its bottom resizable border.  When I open the items on the
left to look at them (Line Objects, Variables, etc.), they disappear below
that bottom border and the only way I can see them is to collapse the items
once again.  I had to go back to 4D v12.4 to be able to see what the debug
window was supposed to look like.  At this point, I am unable to use the
debugger to look at the Call Chain or to to enter Expressions and their
Values.  I have tried to resize the screen and columns (even resized across
two monitors) and nothing seems to reset the debug window.

2.  Sometimes, not all the time, I have tried to resize the debug window,
the resize behaves totally crazy.  If I try to pull the window to the left,
the window will do it for just a moment and then as long as I continue to
hold down the left mouse button, it will automatically resize to the right
without me moving the mouse and will even exceed the size of both of my
monitors.  The window eventually exceeds both monitors and I can't even grab
the right bottom of the Mac OS X window any longer as it is not visible in
order to try to resize it to a smaller size.  The only way to resize it back
to usefulness is to click the green Mac OS resize at the top of the OS X Mac
window.  The problem with this is that now the debug window is the full size
of the screen which makes it very difficult to code.



**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

Chip Scheide
I am not using either 10.8, nor v13.
However, I would expect that the behavior you are seeing, if it was wide spread, would be a long and heatedly discussed issue here on the Nug; so I expect that there is something "wrong" in your installation.  A corrupted preference, a damaged "resource" inside the 4D application, a plugin or component corruption, maybe even some sort of strange plugin/component interaction, an OS preference or other corruption, or even the structure you are using.

Does this behavior exist for any 4D database you work on?
if you haven't yet done so - try  creating a new database, write a few lines of code and see if the problem exists

if the debugger works OK in the test system - run a full repair of your database structure, and data while you are at it.
 
if the problem is not your database and if you have not already done so I would do the following:
locate and (re)move all 4D preferences
preferences on 10.6 (save the folders - place them somewhere you can find later):
Users / <user name> / Library / application support / 4D
Users / <user name> / Library / preferences
<hard drive> / library / application support
you will likely have to re-enter license codes, although you can try to replace the file with the license if this does not resolve the issue.


if the problem still exists
  if you use plugins and/or components - get new copies and re-install them.

if the problem still exists
 delete the new preference folders, keeping the original ones, delete 4D
 re-download the current version from 4D
 re-install

if all that fails -  maybe there is something flakey about your user account or the OS install.
  try a different user on the the same machine (tests for a damaged ??? in your your account)
    still fails
      try booting from a clean install of 10.8 on a separate drive (tests for a damaged ??? in your OS install)
        still fails
          try a different machine using the above separate drive with OS (tests for a damaged ??? in the machine's hardware)


> The two issues below appear to be interrelated and only affect the 4D 13.1,
> 13.2, & 13.3 debug window.  They do not affect 4D v12.4.  I submitted this
> issue in as a bug on July 16, 2013, but so far it is just listed as "In
> Progress".  My problem is that I have not been able to effectively debug my
> apps.  I need some way to reset the debug window back to "normal".   I do
> not know if the issue affects the Windows OS version of 4D as my work at
> this time is only on the latest deployed version of Mac OS X  (OS version
> 10.8.4).  I am not having any other problems with any other 4D windows or
> any other Mac OS X windows.  This problem is confined to the 4D 13.x debug
> window.  The 4D Bug is ACI0083025.  I submitted screen snapshots with this
> bug report to show graphically show the problem.
>
> 1.  In 4D v13.3 (also 13.1 & 13.2) my debug window content and behavior are
> incorrect.  The upper pane contains a list of items on the left (Line
> Objects, Variables, Constants, Tables & Fields, etc.  There is a column to
> the right named "Value".  That column extends as far to the right as the
> window is sized.  There is no more information to the right.  The Call Chain
> pane and the Express pane are completely missing.  The bottom of the upper
> pane is missing its bottom resizable border.  When I open the items on the
> left to look at them (Line Objects, Variables, etc.), they disappear below
> that bottom border and the only way I can see them is to collapse the items
> once again.  I had to go back to 4D v12.4 to be able to see what the debug
> window was supposed to look like.  At this point, I am unable to use the
> debugger to look at the Call Chain or to to enter Expressions and their
> Values.  I have tried to resize the screen and columns (even resized across
> two monitors) and nothing seems to reset the debug window.
>
> 2.  Sometimes, not all the time, I have tried to resize the debug window,
> the resize behaves totally crazy.  If I try to pull the window to the left,
> the window will do it for just a moment and then as long as I continue to
> hold down the left mouse button, it will automatically resize to the right
> without me moving the mouse and will even exceed the size of both of my
> monitors.  The window eventually exceeds both monitors and I can't even grab
> the right bottom of the Mac OS X window any longer as it is not visible in
> order to try to resize it to a smaller size.  The only way to resize it back
> to usefulness is to click the green Mac OS resize at the top of the OS X Mac
> window.  The problem with this is that now the debug window is the full size
> of the screen which makes it very difficult to code.
>
>
>
> **********************************************************************
> 4D v13 is available now - with more than 200 new features to make
> your applications richer and faster
> http://www.4d.com/products/new.html
>
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[hidden email]
> **********************************************************************
>

**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

David Belote
Thank you for your response.  It affects all databases, not just a certain
one.  To test 4D v13.1 & v13.2, I created new databases and it is the same
for those.  I created a new 4D v12.4 database and it is not a problem
there.  This issue occurs on all 4D v13.3 databases I open.

I am not up on all the ins and outs of OS X so I'll have to be very
careful when deleting something, like a preference since I don't know what
else is affected, but I understand that may be the fix.  I'll read through
your response more carefully and try a few of these things.  Thank you.

On 8/21/13 7:58 AM, "Chip Scheide" <[hidden email]> wrote:

>I am not using either 10.8, nor v13.
>However, I would expect that the behavior you are seeing, if it was wide
>spread, would be a long and heatedly discussed issue here on the Nug; so
>I expect that there is something "wrong" in your installation.  A
>corrupted preference, a damaged "resource" inside the 4D application, a
>plugin or component corruption, maybe even some sort of strange
>plugin/component interaction, an OS preference or other corruption, or
>even the structure you are using.
>
>Does this behavior exist for any 4D database you work on?
>if you haven't yet done so - try  creating a new database, write a few
>lines of code and see if the problem exists
>
>if the debugger works OK in the test system - run a full repair of your
>database structure, and data while you are at it.
>
>if the problem is not your database and if you have not already done so I
>would do the following:
>locate and (re)move all 4D preferences
>preferences on 10.6 (save the folders - place them somewhere you can find
>later):
>Users / <user name> / Library / application support / 4D
>Users / <user name> / Library / preferences
><hard drive> / library / application support
>you will likely have to re-enter license codes, although you can try to
>replace the file with the license if this does not resolve the issue.
>
>
>if the problem still exists
>  if you use plugins and/or components - get new copies and re-install
>them.
>
>if the problem still exists
> delete the new preference folders, keeping the original ones, delete 4D
> re-download the current version from 4D
> re-install
>
>if all that fails -  maybe there is something flakey about your user
>account or the OS install.
>  try a different user on the the same machine (tests for a damaged ???
>in your your account)
>    still fails
>      try booting from a clean install of 10.8 on a separate drive (tests
>for a damaged ??? in your OS install)
> still fails
>          try a different machine using the above separate drive with OS
>(tests for a damaged ??? in the machine's hardware)
>
>
>> The two issues below appear to be interrelated and only affect the 4D
>>13.1,
>> 13.2, & 13.3 debug window.  They do not affect 4D v12.4.  I submitted
>>this
>> issue in as a bug on July 16, 2013, but so far it is just listed as "In
>> Progress".  My problem is that I have not been able to effectively
>>debug my
>> apps.  I need some way to reset the debug window back to "normal".   I
>>do
>> not know if the issue affects the Windows OS version of 4D as my work at
>> this time is only on the latest deployed version of Mac OS X  (OS
>>version
>> 10.8.4).  I am not having any other problems with any other 4D windows
>>or
>> any other Mac OS X windows.  This problem is confined to the 4D 13.x
>>debug
>> window.  The 4D Bug is ACI0083025.  I submitted screen snapshots with
>>this
>> bug report to show graphically show the problem.
>>
>> 1.  In 4D v13.3 (also 13.1 & 13.2) my debug window content and behavior
>>are
>> incorrect.  The upper pane contains a list of items on the left (Line
>> Objects, Variables, Constants, Tables & Fields, etc.  There is a column
>>to
>> the right named "Value".  That column extends as far to the right as the
>> window is sized.  There is no more information to the right.  The Call
>>Chain
>> pane and the Express pane are completely missing.  The bottom of the
>>upper
>> pane is missing its bottom resizable border.  When I open the items on
>>the
>> left to look at them (Line Objects, Variables, etc.), they disappear
>>below
>> that bottom border and the only way I can see them is to collapse the
>>items
>> once again.  I had to go back to 4D v12.4 to be able to see what the
>>debug
>> window was supposed to look like.  At this point, I am unable to use the
>> debugger to look at the Call Chain or to to enter Expressions and their
>> Values.  I have tried to resize the screen and columns (even resized
>>across
>> two monitors) and nothing seems to reset the debug window.
>>
>> 2.  Sometimes, not all the time, I have tried to resize the debug
>>window,
>> the resize behaves totally crazy.  If I try to pull the window to the
>>left,
>> the window will do it for just a moment and then as long as I continue
>>to
>> hold down the left mouse button, it will automatically resize to the
>>right
>> without me moving the mouse and will even exceed the size of both of my
>> monitors.  The window eventually exceeds both monitors and I can't even
>>grab
>> the right bottom of the Mac OS X window any longer as it is not visible
>>in
>> order to try to resize it to a smaller size.  The only way to resize it
>>back
>> to usefulness is to click the green Mac OS resize at the top of the OS
>>X Mac
>> window.  The problem with this is that now the debug window is the full
>>size
>> of the screen which makes it very difficult to code.
>>
>>
>>
>> **********************************************************************
>> 4D v13 is available now - with more than 200 new features to make
>> your applications richer and faster
>> http://www.4d.com/products/new.html
>>
>> 4D Internet Users Group (4D iNUG)
>> FAQ:  http://lists.4d.com/faqnug.html
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:[hidden email]
>> **********************************************************************
>>
>
>**********************************************************************
>4D v13 is available now - with more than 200 new features to make
>your applications richer and faster
>http://www.4d.com/products/new.html
>
>4D Internet Users Group (4D iNUG)
>FAQ:  http://lists.4d.com/faqnug.html
>Archive:  http://lists.4d.com/archives.html
>Options: https://lists.4d.com/mailman/options/4d_tech
>Unsub:  mailto:[hidden email]
>**********************************************************************



**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

Chip Scheide
deleting a preference file/folder for 4D will not affect anything else.

I would not delete the original folders - I would move them to say a desktop folder so that you have them in case you want them.  
I am not sure the exact location but one of those folders probably contains your macro file so just hold on to the folders.

moving the folders from their designated locations - to 4D - is the same as deleting them.

> Thank you for your response.  It affects all databases, not just a certain
> one.  To test 4D v13.1 & v13.2, I created new databases and it is the same
> for those.  I created a new 4D v12.4 database and it is not a problem
> there.  This issue occurs on all 4D v13.3 databases I open.
>
> I am not up on all the ins and outs of OS X so I'll have to be very
> careful when deleting something, like a preference since I don't know what
> else is affected, but I understand that may be the fix.  I'll read through
> your response more carefully and try a few of these things.  Thank you.
>
> On 8/21/13 7:58 AM, "Chip Scheide" <[hidden email]> wrote:
>
>> I am not using either 10.8, nor v13.
>> However, I would expect that the behavior you are seeing, if it was wide
>> spread, would be a long and heatedly discussed issue here on the Nug; so
>> I expect that there is something "wrong" in your installation.  A
>> corrupted preference, a damaged "resource" inside the 4D application, a
>> plugin or component corruption, maybe even some sort of strange
>> plugin/component interaction, an OS preference or other corruption, or
>> even the structure you are using.
>>
>> Does this behavior exist for any 4D database you work on?
>> if you haven't yet done so - try  creating a new database, write a few
>> lines of code and see if the problem exists
>>
>> if the debugger works OK in the test system - run a full repair of your
>> database structure, and data while you are at it.
>>
>> if the problem is not your database and if you have not already done so I
>> would do the following:
>> locate and (re)move all 4D preferences
>> preferences on 10.6 (save the folders - place them somewhere you can find
>> later):
>> Users / <user name> / Library / application support / 4D
>> Users / <user name> / Library / preferences
>> <hard drive> / library / application support
>> you will likely have to re-enter license codes, although you can try to
>> replace the file with the license if this does not resolve the issue.
>>
>>
>> if the problem still exists
>>  if you use plugins and/or components - get new copies and re-install
>> them.
>>
>> if the problem still exists
>> delete the new preference folders, keeping the original ones, delete 4D
>> re-download the current version from 4D
>> re-install
>>
>> if all that fails -  maybe there is something flakey about your user
>> account or the OS install.
>>  try a different user on the the same machine (tests for a damaged ???
>> in your your account)
>>    still fails
>>      try booting from a clean install of 10.8 on a separate drive (tests
>> for a damaged ??? in your OS install)
>> still fails
>>          try a different machine using the above separate drive with OS
>> (tests for a damaged ??? in the machine's hardware)
>>
>>
>>> The two issues below appear to be interrelated and only affect the 4D
>>> 13.1,
>>> 13.2, & 13.3 debug window.  They do not affect 4D v12.4.  I submitted
>>> this
>>> issue in as a bug on July 16, 2013, but so far it is just listed as "In
>>> Progress".  My problem is that I have not been able to effectively
>>> debug my
>>> apps.  I need some way to reset the debug window back to "normal".   I
>>> do
>>> not know if the issue affects the Windows OS version of 4D as my work at
>>> this time is only on the latest deployed version of Mac OS X  (OS
>>> version
>>> 10.8.4).  I am not having any other problems with any other 4D windows
>>> or
>>> any other Mac OS X windows.  This problem is confined to the 4D 13.x
>>> debug
>>> window.  The 4D Bug is ACI0083025.  I submitted screen snapshots with
>>> this
>>> bug report to show graphically show the problem.
>>>
>>> 1.  In 4D v13.3 (also 13.1 & 13.2) my debug window content and behavior
>>> are
>>> incorrect.  The upper pane contains a list of items on the left (Line
>>> Objects, Variables, Constants, Tables & Fields, etc.  There is a column
>>> to
>>> the right named "Value".  That column extends as far to the right as the
>>> window is sized.  There is no more information to the right.  The Call
>>> Chain
>>> pane and the Express pane are completely missing.  The bottom of the
>>> upper
>>> pane is missing its bottom resizable border.  When I open the items on
>>> the
>>> left to look at them (Line Objects, Variables, etc.), they disappear
>>> below
>>> that bottom border and the only way I can see them is to collapse the
>>> items
>>> once again.  I had to go back to 4D v12.4 to be able to see what the
>>> debug
>>> window was supposed to look like.  At this point, I am unable to use the
>>> debugger to look at the Call Chain or to to enter Expressions and their
>>> Values.  I have tried to resize the screen and columns (even resized
>>> across
>>> two monitors) and nothing seems to reset the debug window.
>>>
>>> 2.  Sometimes, not all the time, I have tried to resize the debug
>>> window,
>>> the resize behaves totally crazy.  If I try to pull the window to the
>>> left,
>>> the window will do it for just a moment and then as long as I continue
>>> to
>>> hold down the left mouse button, it will automatically resize to the
>>> right
>>> without me moving the mouse and will even exceed the size of both of my
>>> monitors.  The window eventually exceeds both monitors and I can't even
>>> grab
>>> the right bottom of the Mac OS X window any longer as it is not visible
>>> in
>>> order to try to resize it to a smaller size.  The only way to resize it
>>> back
>>> to usefulness is to click the green Mac OS resize at the top of the OS
>>> X Mac
>>> window.  The problem with this is that now the debug window is the full
>>> size
>>> of the screen which makes it very difficult to code.
>>>
>>>
>>>
>>> **********************************************************************
>>> 4D v13 is available now - with more than 200 new features to make
>>> your applications richer and faster
>>> http://www.4d.com/products/new.html
>>>
>>> 4D Internet Users Group (4D iNUG)
>>> FAQ:  http://lists.4d.com/faqnug.html
>>> Archive:  http://lists.4d.com/archives.html
>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>> Unsub:  mailto:[hidden email]
>>> **********************************************************************
>>>
>>
>> **********************************************************************
>> 4D v13 is available now - with more than 200 new features to make
>> your applications richer and faster
>> http://www.4d.com/products/new.html
>>
>> 4D Internet Users Group (4D iNUG)
>> FAQ:  http://lists.4d.com/faqnug.html
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:[hidden email]
>> **********************************************************************
>
>
>
> **********************************************************************
> 4D v13 is available now - with more than 200 new features to make
> your applications richer and faster
> http://www.4d.com/products/new.html
>
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[hidden email]
> **********************************************************************
>

**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

Donald Koffman
In reply to this post by David Belote
FYI...
I experience this same behavior, only for me it occurs in Windows 7 (running in Parallels). I get around the problem by debugging in Mac OS X (10.8.4).
Clearly, it's a problem with the 4D installation, not the OS.
HTH.

On Aug 21, 2013, at 8:51 AM, David Belote <[hidden email]> wrote:

> The two issues below appear to be interrelated and only affect the 4D 13.1,
> 13.2, & 13.3 debug window.  They do not affect 4D v12.4.  I submitted this
> issue in as a bug on July 16, 2013, but so far it is just listed as "In
> Progress".  My problem is that I have not been able to effectively debug my
> apps.  I need some way to reset the debug window back to "normal".   I do
> not know if the issue affects the Windows OS version of 4D as my work at
> this time is only on the latest deployed version of Mac OS X  (OS version
> 10.8.4).  I am not having any other problems with any other 4D windows or
> any other Mac OS X windows.  This problem is confined to the 4D 13.x debug
> window.  The 4D Bug is ACI0083025.  I submitted screen snapshots with this
> bug report to show graphically show the problem.
>
> 1.  In 4D v13.3 (also 13.1 & 13.2) my debug window content and behavior are
> incorrect.  The upper pane contains a list of items on the left (Line
> Objects, Variables, Constants, Tables & Fields, etc.  There is a column to
> the right named "Value".  That column extends as far to the right as the
> window is sized.  There is no more information to the right.  The Call Chain
> pane and the Express pane are completely missing.  The bottom of the upper
> pane is missing its bottom resizable border.  When I open the items on the
> left to look at them (Line Objects, Variables, etc.), they disappear below
> that bottom border and the only way I can see them is to collapse the items
> once again.  I had to go back to 4D v12.4 to be able to see what the debug
> window was supposed to look like.  At this point, I am unable to use the
> debugger to look at the Call Chain or to to enter Expressions and their
> Values.  I have tried to resize the screen and columns (even resized across
> two monitors) and nothing seems to reset the debug window.
>
> 2.  Sometimes, not all the time, I have tried to resize the debug window,
> the resize behaves totally crazy.  If I try to pull the window to the left,
> the window will do it for just a moment and then as long as I continue to
> hold down the left mouse button, it will automatically resize to the right
> without me moving the mouse and will even exceed the size of both of my
> monitors.  The window eventually exceeds both monitors and I can't even grab
> the right bottom of the Mac OS X window any longer as it is not visible in
> order to try to resize it to a smaller size.  The only way to resize it back
> to usefulness is to click the green Mac OS resize at the top of the OS X Mac
> window.  The problem with this is that now the debug window is the full size
> of the screen which makes it very difficult to code.
>
>
>
> **********************************************************************
> 4D v13 is available now - with more than 200 new features to make
> your applications richer and faster
> http://www.4d.com/products/new.html
>
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[hidden email]
> **********************************************************************


**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

David Belote
The debug window fails on virtually all of my Mac hosted 4D v13.X
databases.  When I copy them over to Windows Vista (running under
Parallels on my Mac) and run them, the debug window runs fine under
Windows Vista on those same database files.  On the flip side, I created a
new database under Windows Vista and the debug window worked fine under
Windows Vista.  When I copied that new 4D database over to the Mac and ran
it, the debug window failed to operate correctly (as described earlier). I
tried many of my 4D databases both on the Mac and on the PC in this same
fashion.  The debug window works for me under Windows Vista, but not under
Mac OS X 10.8.4.

It is very interesting that Donald Koffman and I have the same 4D debug
window issue, but that his works correctly on the Mac, but not under
Windows and mine works under Windows, but not on the Mac.

On 8/21/13 3:48 PM, "Donald Koffman" <[hidden email]> wrote:

>FYI...
>I experience this same behavior, only for me it occurs in Windows 7
>(running in Parallels). I get around the problem by debugging in Mac OS X
>(10.8.4).
>Clearly, it's a problem with the 4D installation, not the OS.
>HTH.
>
>On Aug 21, 2013, at 8:51 AM, David Belote <[hidden email]>
>wrote:
>
>> The two issues below appear to be interrelated and only affect the 4D
>>13.1,
>> 13.2, & 13.3 debug window.  They do not affect 4D v12.4.  I submitted
>>this
>> issue in as a bug on July 16, 2013, but so far it is just listed as "In
>> Progress".  My problem is that I have not been able to effectively
>>debug my
>> apps.  I need some way to reset the debug window back to "normal".   I
>>do
>> not know if the issue affects the Windows OS version of 4D as my work at
>> this time is only on the latest deployed version of Mac OS X  (OS
>>version
>> 10.8.4).  I am not having any other problems with any other 4D windows
>>or
>> any other Mac OS X windows.  This problem is confined to the 4D 13.x
>>debug
>> window.  The 4D Bug is ACI0083025.  I submitted screen snapshots with
>>this
>> bug report to show graphically show the problem.
>>
>> 1.  In 4D v13.3 (also 13.1 & 13.2) my debug window content and behavior
>>are
>> incorrect.  The upper pane contains a list of items on the left (Line
>> Objects, Variables, Constants, Tables & Fields, etc.  There is a column
>>to
>> the right named "Value".  That column extends as far to the right as the
>> window is sized.  There is no more information to the right.  The Call
>>Chain
>> pane and the Express pane are completely missing.  The bottom of the
>>upper
>> pane is missing its bottom resizable border.  When I open the items on
>>the
>> left to look at them (Line Objects, Variables, etc.), they disappear
>>below
>> that bottom border and the only way I can see them is to collapse the
>>items
>> once again.  I had to go back to 4D v12.4 to be able to see what the
>>debug
>> window was supposed to look like.  At this point, I am unable to use the
>> debugger to look at the Call Chain or to to enter Expressions and their
>> Values.  I have tried to resize the screen and columns (even resized
>>across
>> two monitors) and nothing seems to reset the debug window.
>>
>> 2.  Sometimes, not all the time, I have tried to resize the debug
>>window,
>> the resize behaves totally crazy.  If I try to pull the window to the
>>left,
>> the window will do it for just a moment and then as long as I continue
>>to
>> hold down the left mouse button, it will automatically resize to the
>>right
>> without me moving the mouse and will even exceed the size of both of my
>> monitors.  The window eventually exceeds both monitors and I can't even
>>grab
>> the right bottom of the Mac OS X window any longer as it is not visible
>>in
>> order to try to resize it to a smaller size.  The only way to resize it
>>back
>> to usefulness is to click the green Mac OS resize at the top of the OS
>>X Mac
>> window.  The problem with this is that now the debug window is the full
>>size
>> of the screen which makes it very difficult to code.
>>
>>
>>
>> **********************************************************************
>> 4D v13 is available now - with more than 200 new features to make
>> your applications richer and faster
>> http://www.4d.com/products/new.html
>>
>> 4D Internet Users Group (4D iNUG)
>> FAQ:  http://lists.4d.com/faqnug.html
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:[hidden email]
>> **********************************************************************
>
>
>**********************************************************************
>4D v13 is available now - with more than 200 new features to make
>your applications richer and faster
>http://www.4d.com/products/new.html
>
>4D Internet Users Group (4D iNUG)
>FAQ:  http://lists.4d.com/faqnug.html
>Archive:  http://lists.4d.com/archives.html
>Options: https://lists.4d.com/mailman/options/4d_tech
>Unsub:  mailto:[hidden email]
>**********************************************************************



**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

Maurice Inzirillo - AJAR
Hello,

Have you tried to delete the 4D Pref file ?


Maurice Inzirillo
--
AJAR S.A.

4D v13: http://www.ajar.ch/
Wakanda : http://www.wakanda.org/
Hébergement 4D sur Internet : www.4dnetcenter.com
iChat/AIM : [hidden email]
Skype : maurice.inzirillo
twitter :minzirillo
Tél : +41 (0)323422684



On 22 août 2013, at 14:24, David Belote <[hidden email]> wrote:

> The debug window fails on virtually all of my Mac hosted 4D v13.X
> databases.  When I copy them over to Windows Vista (running under
> Parallels on my Mac) and run them, the debug window runs fine under
> Windows Vista on those same database files.  On the flip side, I created a
> new database under Windows Vista and the debug window worked fine under
> Windows Vista.  When I copied that new 4D database over to the Mac and ran
> it, the debug window failed to operate correctly (as described earlier). I
> tried many of my 4D databases both on the Mac and on the PC in this same
> fashion.  The debug window works for me under Windows Vista, but not under
> Mac OS X 10.8.4.
>
> It is very interesting that Donald Koffman and I have the same 4D debug
> window issue, but that his works correctly on the Mac, but not under
> Windows and mine works under Windows, but not on the Mac.
>
> On 8/21/13 3:48 PM, "Donald Koffman" <[hidden email]> wrote:
>
>> FYI...
>> I experience this same behavior, only for me it occurs in Windows 7
>> (running in Parallels). I get around the problem by debugging in Mac OS X
>> (10.8.4).
>> Clearly, it's a problem with the 4D installation, not the OS.
>> HTH.
>>
>> On Aug 21, 2013, at 8:51 AM, David Belote <[hidden email]>
>> wrote:
>>
>>> The two issues below appear to be interrelated and only affect the 4D
>>> 13.1,
>>> 13.2, & 13.3 debug window.  They do not affect 4D v12.4.  I submitted
>>> this
>>> issue in as a bug on July 16, 2013, but so far it is just listed as "In
>>> Progress".  My problem is that I have not been able to effectively
>>> debug my
>>> apps.  I need some way to reset the debug window back to "normal".   I
>>> do
>>> not know if the issue affects the Windows OS version of 4D as my work at
>>> this time is only on the latest deployed version of Mac OS X  (OS
>>> version
>>> 10.8.4).  I am not having any other problems with any other 4D windows
>>> or
>>> any other Mac OS X windows.  This problem is confined to the 4D 13.x
>>> debug
>>> window.  The 4D Bug is ACI0083025.  I submitted screen snapshots with
>>> this
>>> bug report to show graphically show the problem.
>>>
>>> 1.  In 4D v13.3 (also 13.1 & 13.2) my debug window content and behavior
>>> are
>>> incorrect.  The upper pane contains a list of items on the left (Line
>>> Objects, Variables, Constants, Tables & Fields, etc.  There is a column
>>> to
>>> the right named "Value".  That column extends as far to the right as the
>>> window is sized.  There is no more information to the right.  The Call
>>> Chain
>>> pane and the Express pane are completely missing.  The bottom of the
>>> upper
>>> pane is missing its bottom resizable border.  When I open the items on
>>> the
>>> left to look at them (Line Objects, Variables, etc.), they disappear
>>> below
>>> that bottom border and the only way I can see them is to collapse the
>>> items
>>> once again.  I had to go back to 4D v12.4 to be able to see what the
>>> debug
>>> window was supposed to look like.  At this point, I am unable to use the
>>> debugger to look at the Call Chain or to to enter Expressions and their
>>> Values.  I have tried to resize the screen and columns (even resized
>>> across
>>> two monitors) and nothing seems to reset the debug window.
>>>
>>> 2.  Sometimes, not all the time, I have tried to resize the debug
>>> window,
>>> the resize behaves totally crazy.  If I try to pull the window to the
>>> left,
>>> the window will do it for just a moment and then as long as I continue
>>> to
>>> hold down the left mouse button, it will automatically resize to the
>>> right
>>> without me moving the mouse and will even exceed the size of both of my
>>> monitors.  The window eventually exceeds both monitors and I can't even
>>> grab
>>> the right bottom of the Mac OS X window any longer as it is not visible
>>> in
>>> order to try to resize it to a smaller size.  The only way to resize it
>>> back
>>> to usefulness is to click the green Mac OS resize at the top of the OS
>>> X Mac
>>> window.  The problem with this is that now the debug window is the full
>>> size
>>> of the screen which makes it very difficult to code.
>>>
>>>
>>>
>>> **********************************************************************
>>> 4D v13 is available now - with more than 200 new features to make
>>> your applications richer and faster
>>> http://www.4d.com/products/new.html
>>>
>>> 4D Internet Users Group (4D iNUG)
>>> FAQ:  http://lists.4d.com/faqnug.html
>>> Archive:  http://lists.4d.com/archives.html
>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>> Unsub:  mailto:[hidden email]
>>> **********************************************************************
>>
>>
>> **********************************************************************
>> 4D v13 is available now - with more than 200 new features to make
>> your applications richer and faster
>> http://www.4d.com/products/new.html
>>
>> 4D Internet Users Group (4D iNUG)
>> FAQ:  http://lists.4d.com/faqnug.html
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:[hidden email]
>> **********************************************************************
>
>
>
> **********************************************************************
> 4D v13 is available now - with more than 200 new features to make
> your applications richer and faster
> http://www.4d.com/products/new.html
>
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[hidden email]
> **********************************************************************



**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

David Belote
In reply to this post by Chip Scheide
Chip,

Thanks for the advise.  The problem exists with all of my Mac hosted 4D
v13 database apps, but I have now verified (previous post) that the
problem does not exist for me under Windows Vista.

I went into the preferences files (via unix command line) and am trying to
understand the preferences.  In the Application Support/4D directory there
is one folder for every 4D database and it contains a single
preferences.4D.preferences file.  For one of my test databases created to
test this debug window issue (contains nothing but 2 lines of code), I
deleted the folder for that database.  4D recreated that folder at startup
of the database app, but the debug window issue still existed for that
folder.

I then went into /Users/Username/Library/Preferences and found that there
are only a handful of files in there and not one for any of the new test
databases I created.  I did note that there is one named com.4d.4d.plist.
I removed it and ran my test app with two lines of code and 4D recreated
the com.4d.4d.plist file.  But I still have the same issue with the debug
window.

I looked into the <hard drive>/library/application support/4D/Licenses and
noted that it contains the actual license4D files.  I have not yet tried
to delete them.

I'm working through this slowly, but so far, without fixing it.  I do
appreciate the help.

Dave Belote

On 8/21/13 7:58 AM, "Chip Scheide" <[hidden email]> wrote:

>I am not using either 10.8, nor v13.
>However, I would expect that the behavior you are seeing, if it was wide
>spread, would be a long and heatedly discussed issue here on the Nug; so
>I expect that there is something "wrong" in your installation.  A
>corrupted preference, a damaged "resource" inside the 4D application, a
>plugin or component corruption, maybe even some sort of strange
>plugin/component interaction, an OS preference or other corruption, or
>even the structure you are using.
>
>Does this behavior exist for any 4D database you work on?
>if you haven't yet done so - try  creating a new database, write a few
>lines of code and see if the problem exists
>
>if the debugger works OK in the test system - run a full repair of your
>database structure, and data while you are at it.
>
>if the problem is not your database and if you have not already done so I
>would do the following:
>locate and (re)move all 4D preferences
>preferences on 10.6 (save the folders - place them somewhere you can find
>later):
>Users / <user name> / Library / application support / 4D
>Users / <user name> / Library / preferences
><hard drive> / library / application support
>you will likely have to re-enter license codes, although you can try to
>replace the file with the license if this does not resolve the issue.
>
>
>if the problem still exists
>  if you use plugins and/or components - get new copies and re-install
>them.
>
>if the problem still exists
> delete the new preference folders, keeping the original ones, delete 4D
> re-download the current version from 4D
> re-install
>
>if all that fails -  maybe there is something flakey about your user
>account or the OS install.
>  try a different user on the the same machine (tests for a damaged ???
>in your your account)
>    still fails
>      try booting from a clean install of 10.8 on a separate drive (tests
>for a damaged ??? in your OS install)
> still fails
>          try a different machine using the above separate drive with OS
>(tests for a damaged ??? in the machine's hardware)
>
>
>> The two issues below appear to be interrelated and only affect the 4D
>>13.1,
>> 13.2, & 13.3 debug window.  They do not affect 4D v12.4.  I submitted
>>this
>> issue in as a bug on July 16, 2013, but so far it is just listed as "In
>> Progress".  My problem is that I have not been able to effectively
>>debug my
>> apps.  I need some way to reset the debug window back to "normal".   I
>>do
>> not know if the issue affects the Windows OS version of 4D as my work at
>> this time is only on the latest deployed version of Mac OS X  (OS
>>version
>> 10.8.4).  I am not having any other problems with any other 4D windows
>>or
>> any other Mac OS X windows.  This problem is confined to the 4D 13.x
>>debug
>> window.  The 4D Bug is ACI0083025.  I submitted screen snapshots with
>>this
>> bug report to show graphically show the problem.
>>
>> 1.  In 4D v13.3 (also 13.1 & 13.2) my debug window content and behavior
>>are
>> incorrect.  The upper pane contains a list of items on the left (Line
>> Objects, Variables, Constants, Tables & Fields, etc.  There is a column
>>to
>> the right named "Value".  That column extends as far to the right as the
>> window is sized.  There is no more information to the right.  The Call
>>Chain
>> pane and the Express pane are completely missing.  The bottom of the
>>upper
>> pane is missing its bottom resizable border.  When I open the items on
>>the
>> left to look at them (Line Objects, Variables, etc.), they disappear
>>below
>> that bottom border and the only way I can see them is to collapse the
>>items
>> once again.  I had to go back to 4D v12.4 to be able to see what the
>>debug
>> window was supposed to look like.  At this point, I am unable to use the
>> debugger to look at the Call Chain or to to enter Expressions and their
>> Values.  I have tried to resize the screen and columns (even resized
>>across
>> two monitors) and nothing seems to reset the debug window.
>>
>> 2.  Sometimes, not all the time, I have tried to resize the debug
>>window,
>> the resize behaves totally crazy.  If I try to pull the window to the
>>left,
>> the window will do it for just a moment and then as long as I continue
>>to
>> hold down the left mouse button, it will automatically resize to the
>>right
>> without me moving the mouse and will even exceed the size of both of my
>> monitors.  The window eventually exceeds both monitors and I can't even
>>grab
>> the right bottom of the Mac OS X window any longer as it is not visible
>>in
>> order to try to resize it to a smaller size.  The only way to resize it
>>back
>> to usefulness is to click the green Mac OS resize at the top of the OS
>>X Mac
>> window.  The problem with this is that now the debug window is the full
>>size
>> of the screen which makes it very difficult to code.
>>
>>
>>
>> **********************************************************************
>> 4D v13 is available now - with more than 200 new features to make
>> your applications richer and faster
>> http://www.4d.com/products/new.html
>>
>> 4D Internet Users Group (4D iNUG)
>> FAQ:  http://lists.4d.com/faqnug.html
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:[hidden email]
>> **********************************************************************
>>
>
>**********************************************************************
>4D v13 is available now - with more than 200 new features to make
>your applications richer and faster
>http://www.4d.com/products/new.html
>
>4D Internet Users Group (4D iNUG)
>FAQ:  http://lists.4d.com/faqnug.html
>Archive:  http://lists.4d.com/archives.html
>Options: https://lists.4d.com/mailman/options/4d_tech
>Unsub:  mailto:[hidden email]
>**********************************************************************



**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

David Belote
In reply to this post by Maurice Inzirillo - AJAR
Yes, I deleted it with no fix to the issue.

On 8/22/13 6:32 AM, "Maurice Inzirillo - AJAR" <[hidden email]>
wrote:

>Hello,
>
>Have you tried to delete the 4D Pref file ?
>
>
>Maurice Inzirillo
>--
>AJAR S.A.
>
>4D v13: http://www.ajar.ch/
>Wakanda : http://www.wakanda.org/
>Hébergement 4D sur Internet : www.4dnetcenter.com
>iChat/AIM : [hidden email]
>Skype : maurice.inzirillo
>twitter :minzirillo
>Tél : +41 (0)323422684
>
>
>
>On 22 août 2013, at 14:24, David Belote <[hidden email]> wrote:
>
>> The debug window fails on virtually all of my Mac hosted 4D v13.X
>> databases.  When I copy them over to Windows Vista (running under
>> Parallels on my Mac) and run them, the debug window runs fine under
>> Windows Vista on those same database files.  On the flip side, I
>>created a
>> new database under Windows Vista and the debug window worked fine under
>> Windows Vista.  When I copied that new 4D database over to the Mac and
>>ran
>> it, the debug window failed to operate correctly (as described
>>earlier). I
>> tried many of my 4D databases both on the Mac and on the PC in this same
>> fashion.  The debug window works for me under Windows Vista, but not
>>under
>> Mac OS X 10.8.4.
>>
>> It is very interesting that Donald Koffman and I have the same 4D debug
>> window issue, but that his works correctly on the Mac, but not under
>> Windows and mine works under Windows, but not on the Mac.
>>
>> On 8/21/13 3:48 PM, "Donald Koffman" <[hidden email]> wrote:
>>
>>> FYI...
>>> I experience this same behavior, only for me it occurs in Windows 7
>>> (running in Parallels). I get around the problem by debugging in Mac
>>>OS X
>>> (10.8.4).
>>> Clearly, it's a problem with the 4D installation, not the OS.
>>> HTH.
>>>
>>> On Aug 21, 2013, at 8:51 AM, David Belote <[hidden email]>
>>> wrote:
>>>
>>>> The two issues below appear to be interrelated and only affect the 4D
>>>> 13.1,
>>>> 13.2, & 13.3 debug window.  They do not affect 4D v12.4.  I submitted
>>>> this
>>>> issue in as a bug on July 16, 2013, but so far it is just listed as
>>>>"In
>>>> Progress".  My problem is that I have not been able to effectively
>>>> debug my
>>>> apps.  I need some way to reset the debug window back to "normal".   I
>>>> do
>>>> not know if the issue affects the Windows OS version of 4D as my work
>>>>at
>>>> this time is only on the latest deployed version of Mac OS X  (OS
>>>> version
>>>> 10.8.4).  I am not having any other problems with any other 4D windows
>>>> or
>>>> any other Mac OS X windows.  This problem is confined to the 4D 13.x
>>>> debug
>>>> window.  The 4D Bug is ACI0083025.  I submitted screen snapshots with
>>>> this
>>>> bug report to show graphically show the problem.
>>>>
>>>> 1.  In 4D v13.3 (also 13.1 & 13.2) my debug window content and
>>>>behavior
>>>> are
>>>> incorrect.  The upper pane contains a list of items on the left (Line
>>>> Objects, Variables, Constants, Tables & Fields, etc.  There is a
>>>>column
>>>> to
>>>> the right named "Value".  That column extends as far to the right as
>>>>the
>>>> window is sized.  There is no more information to the right.  The Call
>>>> Chain
>>>> pane and the Express pane are completely missing.  The bottom of the
>>>> upper
>>>> pane is missing its bottom resizable border.  When I open the items on
>>>> the
>>>> left to look at them (Line Objects, Variables, etc.), they disappear
>>>> below
>>>> that bottom border and the only way I can see them is to collapse the
>>>> items
>>>> once again.  I had to go back to 4D v12.4 to be able to see what the
>>>> debug
>>>> window was supposed to look like.  At this point, I am unable to use
>>>>the
>>>> debugger to look at the Call Chain or to to enter Expressions and
>>>>their
>>>> Values.  I have tried to resize the screen and columns (even resized
>>>> across
>>>> two monitors) and nothing seems to reset the debug window.
>>>>
>>>> 2.  Sometimes, not all the time, I have tried to resize the debug
>>>> window,
>>>> the resize behaves totally crazy.  If I try to pull the window to the
>>>> left,
>>>> the window will do it for just a moment and then as long as I continue
>>>> to
>>>> hold down the left mouse button, it will automatically resize to the
>>>> right
>>>> without me moving the mouse and will even exceed the size of both of
>>>>my
>>>> monitors.  The window eventually exceeds both monitors and I can't
>>>>even
>>>> grab
>>>> the right bottom of the Mac OS X window any longer as it is not
>>>>visible
>>>> in
>>>> order to try to resize it to a smaller size.  The only way to resize
>>>>it
>>>> back
>>>> to usefulness is to click the green Mac OS resize at the top of the OS
>>>> X Mac
>>>> window.  The problem with this is that now the debug window is the
>>>>full
>>>> size
>>>> of the screen which makes it very difficult to code.
>>>>
>>>>
>>>>
>>>> **********************************************************************
>>>> 4D v13 is available now - with more than 200 new features to make
>>>> your applications richer and faster
>>>> http://www.4d.com/products/new.html
>>>>
>>>> 4D Internet Users Group (4D iNUG)
>>>> FAQ:  http://lists.4d.com/faqnug.html
>>>> Archive:  http://lists.4d.com/archives.html
>>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>>> Unsub:  mailto:[hidden email]
>>>> **********************************************************************
>>>
>>>
>>> **********************************************************************
>>> 4D v13 is available now - with more than 200 new features to make
>>> your applications richer and faster
>>> http://www.4d.com/products/new.html
>>>
>>> 4D Internet Users Group (4D iNUG)
>>> FAQ:  http://lists.4d.com/faqnug.html
>>> Archive:  http://lists.4d.com/archives.html
>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>> Unsub:  mailto:[hidden email]
>>> **********************************************************************
>>
>>
>>
>> **********************************************************************
>> 4D v13 is available now - with more than 200 new features to make
>> your applications richer and faster
>> http://www.4d.com/products/new.html
>>
>> 4D Internet Users Group (4D iNUG)
>> FAQ:  http://lists.4d.com/faqnug.html
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:[hidden email]
>> **********************************************************************
>
>
>
>**********************************************************************
>4D v13 is available now - with more than 200 new features to make
>your applications richer and faster
>http://www.4d.com/products/new.html
>
>4D Internet Users Group (4D iNUG)
>FAQ:  http://lists.4d.com/faqnug.html
>Archive:  http://lists.4d.com/archives.html
>Options: https://lists.4d.com/mailman/options/4d_tech
>Unsub:  mailto:[hidden email]
>**********************************************************************



**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

Keisuke Miyako
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

<window name="4ddebugger" left="257" top="97" width="1227" height="641"><form><object name="Ligne1"><bounds left="0" top="621" width="1227" height="0"/></object><object name="vCursorPos"><bounds left="1035" top="624" width="186" height="15"/></object><object name="bCtrlD"><bounds left="16" top="668" width="77" height="30"/></object><object name="Rectangle"><bounds left="0" top="499" width="1227" height="15"/></object><object name="bRun"><bounds left="10" top="7" width="30" height="21"/></object><object name="bAbort"><bounds left="45" top="7" width="30" height="21"/></object><object name="bAbortEdit"><bounds left="80" top="7" width="30" height="21"/></object><object name="bEdit"><bounds left="115" top="7" width="30" height="21"/></object><object name="bSaveSettings"><bounds left="150" top="7" width="30" height="21"/></object><object name="bStepOver"><bounds left="200" top="7" width="30" height="21"/></object><object name="bStepInto"><bounds left="235" top="7" width="30" height="21"/></object><object name="bStepIntoProcess"><bounds left="270" top="7" width="30" height="21"/></object><object name="bStepOut"><bounds left="306" top="7" width="30" height="21"/></object><object name="Splitter"><bounds left="0" top="246" width="1227" height="4"/></object><object name="Splitter1"><bounds left="366" top="52" width="851" height="4"/></object><object name="Splitter2"><bounds left="359" top="40" width="4" height="201"/></object><object name="Line"><bounds left="0" top="34" width="1227" height="0"/></object><object name="WatchView" separator_ratio="0.17106187343597"><bounds left="370" top="62" width="847" height="174"/></object><object name="StackView" separator_ratio="0.66666668653488"><bounds left="370" top="43" width="847" height="1"/></object><object name="GlobalWatchView" separator_ratio="0.66666668653488"><bounds left="10" top="43" width="340" height="193"/></object><object name="CodeView"><bounds left="0" top="250" width="1227" height="371"/></object><object name="vMethodName"><bounds left="360" top="10" width="857" height="20"/></object><object name="vReason1"><bounds left="5" top="624" width="994" height="15"/></object><object name="separator.1"><bounds left="190" top="7" width="0" height="21"/></object><object name="Line1"><bounds left="0" top="35" width="1227" height="0"/></object></form></window>

I am pretty sure this is where the information is stored. (on v13)

miyako

On 2013/08/23, at 10:50, David Belote <[hidden email]> wrote:

> Yes, I deleted it with no fix to the issue.






**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

KirkBrooks
In reply to this post by David Belote
David,
FWIW I see this problem when I am using two copies of 4D at the same time.
I think it's because 4D doesn't duplicate all the resources for multiple
launches like this. So if I happen to have the debugger open on both
instances at the same time, and even worse if one instance is on one
monitor and the other on a different one, the last window closed seems to
mostly account for the saved values. At least that's the way it seems.


On Wed, Aug 21, 2013 at 5:51 AM, David Belote <[hidden email]>wrote:
>
> 2.  Sometimes, not all the time, I have tried to resize the debug window,
> the resize behaves totally crazy.
>

--
Kirk Brooks
San Francisco, CA
=======================

**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

David Belote
In reply to this post by Keisuke Miyako
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" <[hidden email]> 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
>
><window name="4ddebugger" left="257" top="97" width="1227"
>height="641"><form><object name="Ligne1"><bounds left="0" top="621"
>width="1227" height="0"/></object><object name="vCursorPos"><bounds
>left="1035" top="624" width="186" height="15"/></object><object
>name="bCtrlD"><bounds left="16" top="668" width="77"
>height="30"/></object><object name="Rectangle"><bounds left="0" top="499"
>width="1227" height="15"/></object><object name="bRun"><bounds left="10"
>top="7" width="30" height="21"/></object><object name="bAbort"><bounds
>left="45" top="7" width="30" height="21"/></object><object
>name="bAbortEdit"><bounds left="80" top="7" width="30"
>height="21"/></object><object name="bEdit"><bounds left="115" top="7"
>width="30" height="21"/></object><object name="bSaveSettings"><bounds
>left="150" top="7" width="30" height="21"/></object><object
>name="bStepOver"><bounds left="200" top="7" width="30"
>height="21"/></object><object name="bStepInto"><bounds left="235" top="7"
>width="30" height="21"/></object><object name="bStepIntoProcess"><bounds
>left="270" top="7" width="30" height="21"/></object><object
>name="bStepOut"><bounds left="306" top="7" width="30"
>height="21"/></object><object name="Splitter"><bounds left="0" top="246"
>width="1227" height="4"/></object><object name="Splitter1"><bounds
>left="366" top="52" width="851" height="4"/></object><object
>name="Splitter2"><bounds left="359" top="40" width="4"
>height="201"/></object><object name="Line"><bounds left="0" top="34"
>width="1227" height="0"/></object><object name="WatchView"
>separator_ratio="0.17106187343597"><bounds left="370" top="62"
>width="847" height="174"/></object><object name="StackView"
>separator_ratio="0.66666668653488"><bounds left="370" top="43"
>width="847" height="1"/></object><object name="GlobalWatchView"
>separator_ratio="0.66666668653488"><bounds left="10" top="43" width="340"
>height="193"/></object><object name="CodeView"><bounds left="0" top="250"
>width="1227" height="371"/></object><object name="vMethodName"><bounds
>left="360" top="10" width="857" height="20"/></object><object
>name="vReason1"><bounds left="5" top="624" width="994"
>height="15"/></object><object name="separator.1"><bounds left="190"
>top="7" width="0" height="21"/></object><object name="Line1"><bounds
>left="0" top="35" width="1227" height="0"/></object></form></window>
>
>I am pretty sure this is where the information is stored. (on v13)
>
>miyako
>
>On 2013/08/23, at 10:50, David Belote <[hidden email]> wrote:
>
>> Yes, I deleted it with no fix to the issue.
>
>
>
>
>
>
>**********************************************************************
>4D v13 is available now - with more than 200 new features to make
>your applications richer and faster
>http://www.4d.com/products/new.html
>
>4D Internet Users Group (4D iNUG)
>FAQ:  http://lists.4d.com/faqnug.html
>Archive:  http://lists.4d.com/archives.html
>Options: https://lists.4d.com/mailman/options/4d_tech
>Unsub:  mailto:[hidden email]
>**********************************************************************



**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

Donald Koffman
I second the thank you. It fixed the same problem on the OC.

On Aug 23, 2013, at 9:19 AM, David Belote <[hidden email]> 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" <[hidden email]> 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
>>
>> <window name="4ddebugger" left="257" top="97" width="1227"
>> height="641"><form><object name="Ligne1"><bounds left="0" top="621"
>> width="1227" height="0"/></object><object name="vCursorPos"><bounds
>> left="1035" top="624" width="186" height="15"/></object><object
>> name="bCtrlD"><bounds left="16" top="668" width="77"
>> height="30"/></object><object name="Rectangle"><bounds left="0" top="499"
>> width="1227" height="15"/></object><object name="bRun"><bounds left="10"
>> top="7" width="30" height="21"/></object><object name="bAbort"><bounds
>> left="45" top="7" width="30" height="21"/></object><object
>> name="bAbortEdit"><bounds left="80" top="7" width="30"
>> height="21"/></object><object name="bEdit"><bounds left="115" top="7"
>> width="30" height="21"/></object><object name="bSaveSettings"><bounds
>> left="150" top="7" width="30" height="21"/></object><object
>> name="bStepOver"><bounds left="200" top="7" width="30"
>> height="21"/></object><object name="bStepInto"><bounds left="235" top="7"
>> width="30" height="21"/></object><object name="bStepIntoProcess"><bounds
>> left="270" top="7" width="30" height="21"/></object><object
>> name="bStepOut"><bounds left="306" top="7" width="30"
>> height="21"/></object><object name="Splitter"><bounds left="0" top="246"
>> width="1227" height="4"/></object><object name="Splitter1"><bounds
>> left="366" top="52" width="851" height="4"/></object><object
>> name="Splitter2"><bounds left="359" top="40" width="4"
>> height="201"/></object><object name="Line"><bounds left="0" top="34"
>> width="1227" height="0"/></object><object name="WatchView"
>> separator_ratio="0.17106187343597"><bounds left="370" top="62"
>> width="847" height="174"/></object><object name="StackView"
>> separator_ratio="0.66666668653488"><bounds left="370" top="43"
>> width="847" height="1"/></object><object name="GlobalWatchView"
>> separator_ratio="0.66666668653488"><bounds left="10" top="43" width="340"
>> height="193"/></object><object name="CodeView"><bounds left="0" top="250"
>> width="1227" height="371"/></object><object name="vMethodName"><bounds
>> left="360" top="10" width="857" height="20"/></object><object
>> name="vReason1"><bounds left="5" top="624" width="994"
>> height="15"/></object><object name="separator.1"><bounds left="190"
>> top="7" width="0" height="21"/></object><object name="Line1"><bounds
>> left="0" top="35" width="1227" height="0"/></object></form></window>
>>
>> I am pretty sure this is where the information is stored. (on v13)
>>
>> miyako
>>
>> On 2013/08/23, at 10:50, David Belote <[hidden email]> wrote:
>>
>>> Yes, I deleted it with no fix to the issue.
>>
>>
>>
>>
>>
>>
>> **********************************************************************
>> 4D v13 is available now - with more than 200 new features to make
>> your applications richer and faster
>> http://www.4d.com/products/new.html
>>
>> 4D Internet Users Group (4D iNUG)
>> FAQ:  http://lists.4d.com/faqnug.html
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:[hidden email]
>> **********************************************************************
>
>
>
> **********************************************************************
> 4D v13 is available now - with more than 200 new features to make
> your applications richer and faster
> http://www.4d.com/products/new.html
>
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[hidden email]
> **********************************************************************


**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

David Belote
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" <[hidden email]> wrote:

>I second the thank you. It fixed the same problem on the OC.
>
>On Aug 23, 2013, at 9:19 AM, David Belote <[hidden email]>
>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" <[hidden email]> 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
>>>
>>> <window name="4ddebugger" left="257" top="97" width="1227"
>>> height="641"><form><object name="Ligne1"><bounds left="0" top="621"
>>> width="1227" height="0"/></object><object name="vCursorPos"><bounds
>>> left="1035" top="624" width="186" height="15"/></object><object
>>> name="bCtrlD"><bounds left="16" top="668" width="77"
>>> height="30"/></object><object name="Rectangle"><bounds left="0"
>>>top="499"
>>> width="1227" height="15"/></object><object name="bRun"><bounds
>>>left="10"
>>> top="7" width="30" height="21"/></object><object name="bAbort"><bounds
>>> left="45" top="7" width="30" height="21"/></object><object
>>> name="bAbortEdit"><bounds left="80" top="7" width="30"
>>> height="21"/></object><object name="bEdit"><bounds left="115" top="7"
>>> width="30" height="21"/></object><object name="bSaveSettings"><bounds
>>> left="150" top="7" width="30" height="21"/></object><object
>>> name="bStepOver"><bounds left="200" top="7" width="30"
>>> height="21"/></object><object name="bStepInto"><bounds left="235"
>>>top="7"
>>> width="30" height="21"/></object><object
>>>name="bStepIntoProcess"><bounds
>>> left="270" top="7" width="30" height="21"/></object><object
>>> name="bStepOut"><bounds left="306" top="7" width="30"
>>> height="21"/></object><object name="Splitter"><bounds left="0"
>>>top="246"
>>> width="1227" height="4"/></object><object name="Splitter1"><bounds
>>> left="366" top="52" width="851" height="4"/></object><object
>>> name="Splitter2"><bounds left="359" top="40" width="4"
>>> height="201"/></object><object name="Line"><bounds left="0" top="34"
>>> width="1227" height="0"/></object><object name="WatchView"
>>> separator_ratio="0.17106187343597"><bounds left="370" top="62"
>>> width="847" height="174"/></object><object name="StackView"
>>> separator_ratio="0.66666668653488"><bounds left="370" top="43"
>>> width="847" height="1"/></object><object name="GlobalWatchView"
>>> separator_ratio="0.66666668653488"><bounds left="10" top="43"
>>>width="340"
>>> height="193"/></object><object name="CodeView"><bounds left="0"
>>>top="250"
>>> width="1227" height="371"/></object><object name="vMethodName"><bounds
>>> left="360" top="10" width="857" height="20"/></object><object
>>> name="vReason1"><bounds left="5" top="624" width="994"
>>> height="15"/></object><object name="separator.1"><bounds left="190"
>>> top="7" width="0" height="21"/></object><object name="Line1"><bounds
>>> left="0" top="35" width="1227" height="0"/></object></form></window>
>>>
>>> I am pretty sure this is where the information is stored. (on v13)
>>>
>>> miyako
>>>
>>> On 2013/08/23, at 10:50, David Belote <[hidden email]>
>>>wrote:
>>>
>>>> Yes, I deleted it with no fix to the issue.
>>>
>>>
>>>
>>>
>>>
>>>
>>> **********************************************************************
>>> 4D v13 is available now - with more than 200 new features to make
>>> your applications richer and faster
>>> http://www.4d.com/products/new.html
>>>
>>> 4D Internet Users Group (4D iNUG)
>>> FAQ:  http://lists.4d.com/faqnug.html
>>> Archive:  http://lists.4d.com/archives.html
>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>> Unsub:  mailto:[hidden email]
>>> **********************************************************************
>>
>>
>>
>> **********************************************************************
>> 4D v13 is available now - with more than 200 new features to make
>> your applications richer and faster
>> http://www.4d.com/products/new.html
>>
>> 4D Internet Users Group (4D iNUG)
>> FAQ:  http://lists.4d.com/faqnug.html
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:[hidden email]
>> **********************************************************************
>
>
>**********************************************************************
>4D v13 is available now - with more than 200 new features to make
>your applications richer and faster
>http://www.4d.com/products/new.html
>
>4D Internet Users Group (4D iNUG)
>FAQ:  http://lists.4d.com/faqnug.html
>Archive:  http://lists.4d.com/archives.html
>Options: https://lists.4d.com/mailman/options/4d_tech
>Unsub:  mailto:[hidden email]
>**********************************************************************



**********************************************************************
4D v13 is available now - with more than 200 new features to make
your applications richer and faster
http://www.4d.com/products/new.html

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

4D Tech mailing list
(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 <[hidden email]>
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" <[hidden email]> wrote:
>
> >I second the thank you. It fixed the same problem on the OC.
> >
> >On Aug 23, 2013, at 9:19 AM, David Belote <[hidden email]>
> >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" <[hidden email]> 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
> >>>
> >>> <window name="4ddebugger" left="257" top="97" width="1227"
> >>> height="641"><form><object name="Ligne1"><bounds left="0" top="621"
> >>> width="1227" height="0"/></object><object name="vCursorPos"><bounds
> >>> left="1035" top="624" width="186" height="15"/></object><object
> >>> name="bCtrlD"><bounds left="16" top="668" width="77"
> >>> height="30"/></object><object name="Rectangle"><bounds left="0"
> >>>top="499"
> >>> width="1227" height="15"/></object><object name="bRun"><bounds
> >>>left="10"
> >>> top="7" width="30" height="21"/></object><object name="bAbort"><bounds
> >>> left="45" top="7" width="30" height="21"/></object><object
> >>> name="bAbortEdit"><bounds left="80" top="7" width="30"
> >>> height="21"/></object><object name="bEdit"><bounds left="115" top="7"
> >>> width="30" height="21"/></object><object name="bSaveSettings"><bounds
> >>> left="150" top="7" width="30" height="21"/></object><object
> >>> name="bStepOver"><bounds left="200" top="7" width="30"
> >>> height="21"/></object><object name="bStepInto"><bounds left="235"
> >>>top="7"
> >>> width="30" height="21"/></object><object
> >>>name="bStepIntoProcess"><bounds
> >>> left="270" top="7" width="30" height="21"/></object><object
> >>> name="bStepOut"><bounds left="306" top="7" width="30"
> >>> height="21"/></object><object name="Splitter"><bounds left="0"
> >>>top="246"
> >>> width="1227" height="4"/></object><object name="Splitter1"><bounds
> >>> left="366" top="52" width="851" height="4"/></object><object
> >>> name="Splitter2"><bounds left="359" top="40" width="4"
> >>> height="201"/></object><object name="Line"><bounds left="0" top="34"
> >>> width="1227" height="0"/></object><object name="WatchView"
> >>> separator_ratio="0.17106187343597"><bounds left="370" top="62"
> >>> width="847" height="174"/></object><object name="StackView"
> >>> separator_ratio="0.66666668653488"><bounds left="370" top="43"
> >>> width="847" height="1"/></object><object name="GlobalWatchView"
> >>> separator_ratio="0.66666668653488"><bounds left="10" top="43"
> >>>width="340"
> >>> height="193"/></object><object name="CodeView"><bounds left="0"
> >>>top="250"
> >>> width="1227" height="371"/></object><object name="vMethodName"><bounds
> >>> left="360" top="10" width="857" height="20"/></object><object
> >>> name="vReason1"><bounds left="5" top="624" width="994"
> >>> height="15"/></object><object name="separator.1"><bounds left="190"
> >>> top="7" width="0" height="21"/></object><object name="Line1"><bounds
> >>> left="0" top="35" width="1227" height="0"/></object></form></window>
> >>>
> >>> I am pretty sure this is where the information is stored. (on v13)
> >>>
> >>> miyako
> >>>
> >>> On 2013/08/23, at 10:50, David Belote <[hidden email]>
> >>>wrote:
> >>>
> >>>> Yes, I deleted it with no fix to the issue.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> **********************************************************************
> >>> 4D v13 is available now - with more than 200 new features to make
> >>> your applications richer and faster
> >>> http://www.4d.com/products/new.html
> >>>
> >>> 4D Internet Users Group (4D iNUG)
> >>> FAQ:  http://lists.4d.com/faqnug.html
> >>> Archive:  http://lists.4d.com/archives.html
> >>> Options: https://lists.4d.com/mailman/options/4d_tech
> >>> Unsub:  mailto:[hidden email]
> >>> **********************************************************************
> >>
> >>
> >>
> >> **********************************************************************
> >> 4D v13 is available now - with more than 200 new features to make
> >> your applications richer and faster
> >> http://www.4d.com/products/new.html
> >>
> >> 4D Internet Users Group (4D iNUG)
> >> FAQ:  http://lists.4d.com/faqnug.html
> >> Archive:  http://lists.4d.com/archives.html
> >> Options: https://lists.4d.com/mailman/options/4d_tech
> >> Unsub:  mailto:[hidden email]
> >> **********************************************************************
> >
> >
> >**********************************************************************
> >4D v13 is available now - with more than 200 new features to make
> >your applications richer and faster
> >http://www.4d.com/products/new.html
> >
> >4D Internet Users Group (4D iNUG)
> >FAQ:  http://lists.4d.com/faqnug.html
> >Archive:  http://lists.4d.com/archives.html
> >Options: https://lists.4d.com/mailman/options/4d_tech
> >Unsub:  mailto:[hidden email]
> >**********************************************************************
>
>
>
> **********************************************************************
> 4D v13 is available now - with more than 200 new features to make
> your applications richer and faster
> http://www.4d.com/products/new.html
>
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[hidden email]
> **********************************************************************
>
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************
Reply | Threaded
Open this post in threaded view
|

Re: Significant Debugger Window Issue

4D Tech mailing list
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:cjmiller<AT SIGN>informed-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 <[hidden email]> 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 <[hidden email]>
> 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" <[hidden email]> wrote:
>>
>>> I second the thank you. It fixed the same problem on the OC.
>>>
>>> On Aug 23, 2013, at 9:19 AM, David Belote <[hidden email]>
>>> 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" <[hidden email]> 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
>>>>>
>>>>> <window name="4ddebugger" left="257" top="97" width="1227"
>>>>> height="641"><form><object name="Ligne1"><bounds left="0" top="621"
>>>>> width="1227" height="0"/></object><object name="vCursorPos"><bounds
>>>>> left="1035" top="624" width="186" height="15"/></object><object
>>>>> name="bCtrlD"><bounds left="16" top="668" width="77"
>>>>> height="30"/></object><object name="Rectangle"><bounds left="0"
>>>>> top="499"
>>>>> width="1227" height="15"/></object><object name="bRun"><bounds
>>>>> left="10"
>>>>> top="7" width="30" height="21"/></object><object name="bAbort"><bounds
>>>>> left="45" top="7" width="30" height="21"/></object><object
>>>>> name="bAbortEdit"><bounds left="80" top="7" width="30"
>>>>> height="21"/></object><object name="bEdit"><bounds left="115" top="7"
>>>>> width="30" height="21"/></object><object name="bSaveSettings"><bounds
>>>>> left="150" top="7" width="30" height="21"/></object><object
>>>>> name="bStepOver"><bounds left="200" top="7" width="30"
>>>>> height="21"/></object><object name="bStepInto"><bounds left="235"
>>>>> top="7"
>>>>> width="30" height="21"/></object><object
>>>>> name="bStepIntoProcess"><bounds
>>>>> left="270" top="7" width="30" height="21"/></object><object
>>>>> name="bStepOut"><bounds left="306" top="7" width="30"
>>>>> height="21"/></object><object name="Splitter"><bounds left="0"
>>>>> top="246"
>>>>> width="1227" height="4"/></object><object name="Splitter1"><bounds
>>>>> left="366" top="52" width="851" height="4"/></object><object
>>>>> name="Splitter2"><bounds left="359" top="40" width="4"
>>>>> height="201"/></object><object name="Line"><bounds left="0" top="34"
>>>>> width="1227" height="0"/></object><object name="WatchView"
>>>>> separator_ratio="0.17106187343597"><bounds left="370" top="62"
>>>>> width="847" height="174"/></object><object name="StackView"
>>>>> separator_ratio="0.66666668653488"><bounds left="370" top="43"
>>>>> width="847" height="1"/></object><object name="GlobalWatchView"
>>>>> separator_ratio="0.66666668653488"><bounds left="10" top="43"
>>>>> width="340"
>>>>> height="193"/></object><object name="CodeView"><bounds left="0"
>>>>> top="250"
>>>>> width="1227" height="371"/></object><object name="vMethodName"><bounds
>>>>> left="360" top="10" width="857" height="20"/></object><object
>>>>> name="vReason1"><bounds left="5" top="624" width="994"
>>>>> height="15"/></object><object name="separator.1"><bounds left="190"
>>>>> top="7" width="0" height="21"/></object><object name="Line1"><bounds
>>>>> left="0" top="35" width="1227" height="0"/></object></form></window>
>>>>>
>>>>> I am pretty sure this is where the information is stored. (on v13)
>>>>>
>>>>> miyako
>>>>>
>>>>> On 2013/08/23, at 10:50, David Belote <[hidden email]>
>>>>> wrote:
>>>>>
>>>>>> Yes, I deleted it with no fix to the issue.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> **********************************************************************
>>>>> 4D v13 is available now - with more than 200 new features to make
>>>>> your applications richer and faster
>>>>> http://www.4d.com/products/new.html
>>>>>
>>>>> 4D Internet Users Group (4D iNUG)
>>>>> FAQ:  http://lists.4d.com/faqnug.html
>>>>> Archive:  http://lists.4d.com/archives.html
>>>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>>>> Unsub:  mailto:[hidden email]
>>>>> **********************************************************************
>>>>
>>>>
>>>>
>>>> **********************************************************************
>>>> 4D v13 is available now - with more than 200 new features to make
>>>> your applications richer and faster
>>>> http://www.4d.com/products/new.html
>>>>
>>>> 4D Internet Users Group (4D iNUG)
>>>> FAQ:  http://lists.4d.com/faqnug.html
>>>> Archive:  http://lists.4d.com/archives.html
>>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>>> Unsub:  mailto:[hidden email]
>>>> **********************************************************************
>>>
>>>
>>> **********************************************************************
>>> 4D v13 is available now - with more than 200 new features to make
>>> your applications richer and faster
>>> http://www.4d.com/products/new.html
>>>
>>> 4D Internet Users Group (4D iNUG)
>>> FAQ:  http://lists.4d.com/faqnug.html
>>> Archive:  http://lists.4d.com/archives.html
>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>> Unsub:  mailto:[hidden email]
>>> **********************************************************************
>>
>>
>>
>> **********************************************************************
>> 4D v13 is available now - with more than 200 new features to make
>> your applications richer and faster
>> http://www.4d.com/products/new.html
>>
>> 4D Internet Users Group (4D iNUG)
>> FAQ:  http://lists.4d.com/faqnug.html
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:[hidden email]
>> **********************************************************************
>>
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[hidden email]
> **********************************************************************

**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[hidden email]
**********************************************************************