Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Debug - Trace window is empty
Message
From
23/07/2006 11:12:31
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
 
To
23/07/2006 07:41:34
Hans-Otto Lochmann
Dr. Lochmann Consulting Gmbh
Frankfurt, Germany
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
01138798
Message ID:
01138915
Views:
12
This message has been marked as a message which has helped to the initial question of the thread.
>Hi Thomas,
>
>thank you for your proposal. Just a few minutes ago I found the solution and it so easy: This obviously is exactly the situation, for which the "Debug info" checkbox is provided for and why it bloats up the build .app and .exe so heavily (see Kilo-Fox, Chapter 14.3 for more detailed information, where I found this hit, which caused me thinking again). If the "Debug info" checkbox is checked, the Build method of the Project Manager includes the missing source. I have had it unchecked all the time, because of its bloating habit.

I knew I'd miss something obvious :)

Actually you could have a project hook class which would turn debug info on or off, depending on some setting, which you could put in place before building... something like
* build.prg
n=messagebox("Include debug info", FlagsForYesNo)
addproperty(_screen, "IncludeDebugInfo", n=6)
build exe myexe from mypjx
And the project hook class would include or remove the debug info depending on the value of _screen.IncludeDebugInfo.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform