problem with debugging:
I found that:

1.

if the app is in readmodal function
and i stops the app with the debugger (with the 2 small blue icon "stop")
menu command,
then the application crashes with "internal structure ... error"

2.

if i start debugging the app , and sets a breakpoint at the first line of
code of main(),
the app stops there.
than, if i steps with F8, there is the message: file is modified in project,
recompile yes/no/cancel

if i chose yes, the prg which contains main() is recompiled, than the same
thing happens again
( i did not change anything)
if i chose no, the next statement is executed and the question is asked
again. if i chose "no" again, about 2 or 3 times, ther is no more question.

some 5 to 10 steps later with f8, in the same function main(), without any
call of another function and/or prg-file, the annoying
"file is modified ....recompile yes/no/cancel" reappears
and so on.........

Jrg Bertram

Joerg
I don't have these problem. Maybee you are using an Antivirus software that change the time of your source file (You can easily do
this by hand when you are in debug mode open and save the prg using a plain editor. You'll see then these message even if you
haven't change anythink in your file). Also there is no need to place a breakpoint on the first line to debug your application. Just
press f8 and the debugger will stop in the first line of your program

Regards
Mike Evans

> 2.
>
> if i start debugging the app , and sets a breakpoint at the first line of
> code of main(),
> the app stops there.
> than, if i steps with F8, there is the message: file is modified in project,
> recompile yes/no/cancel
>
> if i chose yes, the prg which contains main() is recompiled, than the same
> thing happens again
> ( i did not change anything)
> if i chose no, the next statement is executed and the question is asked
> again. if i chose "no" again, about 2 or 3 times, ther is no more question.
>
> some 5 to 10 steps later with f8, in the same function main(), without any
> call of another function and/or prg-file, the annoying
> "file is modified ....recompile yes/no/cancel" reappears
> and so on.........
>
> Jrg Bertram
>
>

joerg bertram wrote:

> if i start debugging the app , and sets a breakpoint at the first line of
> code of main(),
> the app stops there.
> than, if i steps with F8, there is the message: file is modified in project,
> recompile yes/no/cancel

I have same problem if targets (EXE DLL) are on different directory.

Regards.
Claudio Driussi

"Claudio Driussi" <claudio.driussi@libero.it> wrote in message
news:O#QTCxb1DHA.2016@S15147418...
> joerg bertram wrote:
>
> > if i start debugging the app , and sets a breakpoint at the first line
of
> > code of main(),
> > the app stops there.
> > than, if i steps with F8, there is the message: file is modified in
project,
> > recompile yes/no/cancel
>
> I have same problem if targets (EXE DLL) are on different directory.

Claudio,

could you please post a sample project that illustrates this problem?
We aren't aware of that.

Regards,
  Till

--
---------------------------------------------------
ARD - Alaska Research & Development

Web:       http://www.alaska-research.com
Investors: http://www.alaska-research.com/tifund
E-Mail:    mailto:till.warweg@alaska-research.com
Contact:   mailto:info@alaska-research.com
---------------------------------------------------

Till Warweg wrote:

>>I have same problem if targets (EXE DLL) are on different directory.
> 
> Claudio,
> 
> could you please post a sample project that illustrates this problem?
> We aren't aware of that.

file is attached.

I need CS.DLL on the parent directory, so i used TARGET_DIR directive,
but the result is what i mentioned, i would like to have on the
TARGET_DIR also DEF, EXP and LIB filse.

I hope to have these fixes on the next delivery.

Regards
Claudio Driussi

Claudio,

thanks a lot. We'll have a closer look at the project file you
sent.

As to the original issue discussed here, something new
has popped up (and yeah, it's in the "oh my...!" category);

we've found that the "Keywords in uppercase" option
(see Tools -> Editor options -> Intellicode tab) may cause
the behaviour you describe. If you're using (eg. debugging)
sources that use lowercase for keywords such as
"PROCEDURE", "ENDIF" and the like, the debugger
visiting these code passages during step operations may
cause the editor to apply "Keywords in uppercase". So,
in fact, your sources probably were modified implicitly!

Please try switching this option off and see if it helps
in your case, okay?

Regards,
  Till

--
---------------------------------------------------
ARD - Alaska Research & Development

Web:       http://www.alaska-research.com
Investors: http://www.alaska-research.com/tifund
E-Mail:    mailto:till.warweg@alaska-research.com
Contact:   mailto:info@alaska-research.com
---------------------------------------------------

Till Warweg wrote:

> we've found that the "Keywords in uppercase" option
> (see Tools -> Editor options -> Intellicode tab) may cause
> the behaviour you describe. If you're using (eg. debugging)
> sources that use lowercase for keywords such as
> "PROCEDURE", "ENDIF" and the like, the debugger
> visiting these code passages during step operations may
> cause the editor to apply "Keywords in uppercase". So,
> in fact, your sources probably were modified implicitly!
> 
> Please try switching this option off and see if it helps
> in your case, okay?

No, i already switched off uppercase and the problem still
exists.

Best regards.
Claudio Driussi

Claudio Driussi wrote:

> Till Warweg wrote:
> 
>>> I have same problem if targets (EXE DLL) are on different directory.
>>
>>
>> Claudio,
>>
>> could you please post a sample project that illustrates this problem?
>> We aren't aware of that.
> 
> 
> file is attached.
> 
> I need CS.DLL on the parent directory, so i used TARGET_DIR directive,
> but the result is what i mentioned, i would like to have on the
> TARGET_DIR also DEF, EXP and LIB filse.

Here the error is (I think). TARGET_DIR is no official define in the
project file. Currently VX is not able to handle that.

I have posted infos about TARGET_DIR to give an overview about comming
things and to give assistance for rare circumstances.

DO NOT USE IT!

Set your target as with next VX:
   [..\target.exe]

There is an other problem with with your project. You are using rlative
pathes. The current VX can not really handle them. This will be possible
with next upgrade that is available this evening (I Hope 

Regards
   Andreas Herdt
   [Alaska Research & Development]

> I hope to have these fixes on the next delivery.
> 
> Regards
> Claudio Driussi
> 
> 
> ------------------------------------------------------------------------
> 
> [PROJECT]
>     DEBUG         = yes
>     VERSION       = 2.0
>     Project.xpj
> 
> [Project.xpj]
>     AGC.exe
>     CS.dll
> 
> [AGC.exe]
>     COMPILE       = xpp
>     COMPILE_FLAGS = /es /a /m /n /q /w
>     DEBUG_SAVE    = no
>     GUI           = yes
>     LINKER        = ALINK
>     LINK_FLAGS    =
>     RC_COMPILE    = ARC
>     RC_FLAGS      = /v
>     OBJ_DIR       = ..\MAK\OBJ
> // $START-AUTODEPEND
>     ..\MAK\OBJ\AGC.obj
>     ..\MAK\OBJ\AGE.obj
>     ..\MAK\OBJ\ART.obj
>     ..\MAK\OBJ\BAN.obj
>     ..\MAK\OBJ\BDG.obj
>     ..\MAK\OBJ\CAU.obj
>     ..\MAK\OBJ\CEE.obj
>     ..\MAK\OBJ\CIV.obj
>     ..\MAK\OBJ\CLI.obj
>     ..\MAK\OBJ\CMN.obj
>     ..\MAK\OBJ\CSP.obj
>     ..\MAK\OBJ\CSR.obj
>     ..\MAK\OBJ\CTA.obj
>     ..\MAK\OBJ\DBESYS.obj
>     ..\MAK\OBJ\DEP.obj
>     ..\MAK\OBJ\DIV.obj
>     ..\MAK\OBJ\DLS.obj
>     ..\MAK\OBJ\DOCUM.obj
>     ..\MAK\OBJ\DST.obj
>     ..\MAK\OBJ\DVR.obj
>     ..\MAK\OBJ\FRN.obj
>     ..\MAK\OBJ\FTT.obj
>     ..\MAK\OBJ\GCZ.obj
>     ..\MAK\OBJ\LST.obj
>     ..\MAK\OBJ\LTT.obj
>     ..\MAK\OBJ\MCN.obj
>     ..\MAK\OBJ\MIV.obj
>     ..\MAK\OBJ\MMG.obj
>     ..\MAK\OBJ\MVC.obj
>     ..\MAK\OBJ\NUM.obj
>     ..\MAK\OBJ\PAG.obj
>     ..\MAK\OBJ\PDC.obj
>     ..\MAK\OBJ\PRIMA.obj
>     ..\MAK\OBJ\RIT.obj
>     ..\MAK\OBJ\SCA.obj
>     ..\MAK\OBJ\SCN.obj
>     ..\MAK\OBJ\STBIL.obj
>     ..\MAK\OBJ\STCNT.obj
>     ..\MAK\OBJ\STMAG.obj
>     ..\MAK\OBJ\TBV.obj
>     ..\MAK\OBJ\TCN.obj
>     ..\MAK\OBJ\TDO.obj
>     ..\MAK\OBJ\TMG.obj
>     ..\MAK\OBJ\TVC.obj
>     ..\MAK\OBJ\VET.obj
>     ..\MAK\OBJ\VLE.obj
>     ..\MAK\OBJ\VRN.obj
>     ..\MAK\OBJ\XADD.obj
> // $STOP-AUTODEPEND
>     ..\BAP.LIB
>     AGC.ARC
>     CS.LIB
>     ..\DBESYS.PRG
>     AGC.PRG
>     AGE.PRG
>     ART.PRG
>     BAN.PRG
>     BDG.PRG
>     CAU.PRG
>     CEE.PRG
>     CIV.PRG
>     CLI.PRG
>     CMN.PRG
>     CSP.PRG
>     CSR.PRG
>     CTA.PRG
>     DEP.PRG
>     DIV.PRG
>     DLS.PRG
>     DOCUM.PRG
>     DST.PRG
>     DVR.PRG
>     FRN.PRG
>     FTT.PRG
>     GCZ.PRG
>     LST.PRG
>     LTT.PRG
>     MCN.PRG
>     MIV.PRG
>     MMG.PRG
>     MVC.PRG
>     NUM.PRG
>     PAG.PRG
>     PDC.PRG
>     PRIMA.PRG
>     RIT.PRG
>     SCA.PRG
>     SCN.PRG
>     STBIL.PRG
>     STCNT.PRG
>     STMAG.PRG
>     TBV.PRG
>     TCN.PRG
>     TDO.PRG
>     TMG.PRG
>     TVC.PRG
>     VET.PRG
>     VLE.PRG
>     VRN.PRG
>     XADD.PRG
> 
> [CS.dll]
>     COMPILE       = xpp
>     COMPILE_FLAGS = /DLL /es /a /m /n /q /w
>     DEBUG_SAVE    = no
>     GUI           = no
>     LINKER        = ALINK
>     LINK_FLAGS    = /dll
>     RC_COMPILE    = ARC
>     RC_FLAGS      = /v
>     OBJ_DIR       = ..\MAK\OBJ
>     TARGET_DIR    = ..
> // $START-AUTODEPEND
>     ..\MAK\OBJ\arPrint.obj
>     ..\MAK\OBJ\csAlert.obj
>     ..\MAK\OBJ\csApp.obj
>     ..\MAK\OBJ\csAppUt.obj
>     ..\MAK\OBJ\csBrowse.obj
>     ..\MAK\OBJ\csCl.obj
>     ..\MAK\OBJ\csDoc.obj
>     ..\MAK\OBJ\csFilter.obj
>     ..\MAK\OBJ\csGet.obj
>     ..\MAK\OBJ\csKey.obj
>     ..\MAK\OBJ\csMenu.obj
>     ..\MAK\OBJ\csParts.obj
>     ..\MAK\OBJ\csPrint.obj
>     ..\MAK\OBJ\csUtils.obj
>     ..\MAK\OBJ\DbeSys.obj
>     ..\MAK\OBJ\INIFiles.obj
>     ..\MAK\OBJ\mPack.obj
>     ..\MAK\OBJ\NetName.obj
>     ..\MAK\OBJ\SYSINFO.obj
>     ..\MAK\OBJ\WinMenu.obj
> // $STOP-AUTODEPEND
>     ..\ANDRep\arPrint.prg
>     ..\csAlert.prg
>     ..\csApp.prg
>     ..\csAppUt.prg
>     ..\csBrowse.prg
>     ..\csCl.prg
>     ..\csDoc.prg
>     ..\csFilter.prg
>     ..\csGet.prg
>     ..\csKey.prg
>     ..\csMenu.prg
>     ..\csParts.prg
>     ..\csPrint.prg
>     ..\csUtils.prg
>     ..\DbeSys.prg
>     ..\INIFiles.prg
>     ..\mPack.prg
>     ..\NetName.prg
>     ..\SYSINFO.PRG
>     ..\WinMenu.prg
>