TOPIC:

• own scripts after no or minimal editing under the version of vfp X# will implement
• check out benchmarking scripts comparing the implementation in X# on your machine
• follow the discussion and examples between dev team and fox heads by running small examples
• copy the small tidbits found in fox help file and play with those in fox
• Try out the benefit of integrated SQL
• Try out the benefit of the buffering / optimistic locking approach coupled with tableupdate
• write own or run foreign benchmarks and pipe results into text files to compare to VO or X#
• call into GUI Class libraries after set classlib or via NewObject()
• build GUI in prg from scratch / test previously class based and prg-ported GUI
• connect to several backends via Cursoradapter, View or SQL Pass Through
• and much more

FoxProMatt wrote: 1. I'll check this out.
2. I really wish you would post it as a repo on Github, rather than attaching it as a zip file in a message board.

#2 allows for public discussion and issue tracking in the GitHub space, rather than tucked away here in an X# message thread. In my opinion, it would be a lot more interest to the general FoxPro community if it we in it's own github repo.

FoxProMatt wrote:

Interesting.... I could be missing something but it asks for a password that I do not know. Scanning through the files in the zip I do not see a password field or clue. I also don't see a PJX/PJT file so think at least some of the source is missing. -Jeff

Any advice for this issue??

Karl-Heinz wrote: Hi Thomas,
thanks for the upload. Now i´m able to run Foxpro 2.0 code with VFP

Here´s what i´ve found so far:
- it seems that the "?" output is not redirected to the main screen. I noticed that you are using in your samlpes "wait window" to show results.

- when i open or create a prg file via the "modify command" i can edit and save the code via the "File" menu. Somewhat annoying is that an opened editor is always closed as soon as I click on another area than the menu.

- It seems that the menu item states are not always updated. e.g. it´s not possible to compile a prg via the menu item "compile" because the item is always disabled. But that´s no show stopper, because there´s no problem to compile sources inside the command window via the "compile" command.

Karl-Heinz wrote: - it seems that the "?" output is not redirected to the main screen. I noticed that you are using in your samlpes "wait window" to show results.

_Screen.ForeColor = RGB(0,0,0)
? _Screen.ForeColor, "Black as _Screen.ForeColor"
_Screen.BackColor = RGB(255,255,255)
? _Screen.BackColor, "White as _Screen.BackColor"
? _Screen.ForeColor, "Black _Screen.ForeColor"
_Screen.ForeColor = RGB(255,0,0)
? _Screen.ForeColor, "Red as _Screen.ForeColor"
_Screen.ForeColor = RGB(0,255,0)
? _Screen.ForeColor, "Green as _Screen.ForeColor"
_Screen.ForeColor = RGB(0,0,255)
? _Screen.ForeColor, "Blue as _Screen.ForeColor"
_Screen.ForeColor = RGB(0,0,0)
? _Screen.ForeColor, "Black as _Screen.ForeColor"

Karl-Heinz wrote: About the Texteditor "auto close" behaviour: Nope, that´s not acceptable My FP never closes the editor when i jump to e.g. the command window.

About the "?" behaviour: There´s no problem with the "?" output when i try something like "? Date()" inside the command window. i correctly see the current date in the main window. The problem is the "?" usage inside a called proc/func. Just compile this prg and run it with "Do Test2" . Do you see anywhere the expected output "Hello from '?'" ?

FUNCTION Qmark(tcMess)
tcMess = EVL(m.tcMess, "Keine Message mitgegeben")
WAIT WINDOW m.tcMess + chr(13) + "before"
_screen.LockScreen = .f.
_screen.Activate
WAIT window _screen.ActiveForm.Name
*_screen.Cls
_screen.Enabled = .T.
*_screen.Paint()
_screen.Print(CHR(10))

_screen.Print(m.tcMess + "in PRINTSTATUS()")
_screen.Print(m.tcMess + "in PRINTSTATUS() again")
_screen.Print(CHR(13))
_screen.Print(CHR(10))
_screen.Print(m.tcMess + "in PRINTSTATUS() 3")
_screen.Print(m.tcMess + "in PRINTSTATUS() 4")

SET CONSOLE ON
? m.tcMess
WAIT WINDOW m.tcMess + chr(13) + "after"
RETURN

Karl-Heinz wrote: To see the '?' output i´ll use for the moment this skeleton:

PROCEDURE Arrtest1
=set ( "safety" , .f. )
set alternate to output.txt
set alternate on
? "one" , 12 
? "two"
? Date() , Time()
?
? .f. , .t.
close alternate
set alternate to 

modi comm output.txt
Return

FUNCTION QL_Ln ( p01, p02, p03, p04,p05 ;
		,p06, p07, p08, p09,p10 ;
		,p11, p12, p13, p14,p15 ;
		,p16, p17, p18, p19,p20 ;
		,p21, p22, p23, p24,p25 )
*-- read QuestionmarkList_writeLN
LOCAL lnRun, lcPr, lcAdd
lcAdd = ",   "
lcPr = ""
FOR lnRun = 1 TO PCOUNT()
	lcPr = m.lcPr + TRANSFORM(EVALUATE("m.p";
			+PADL(ALLTRIM(STR(m.lnRun)),2,"0")))  ;
			+ m.lcAdd 
next
IF PCOUNT()>0
	lcPr = Left(m.lcPr, LEN(m.lcPr)-LEN(m.lcAdd))
ENDIF
_screen.Print(CHR(13)+CHR(10)+m.lcPr)

Karl-Heinz wrote: To see the '?' output ....

ACTIVATE SCREEN

Karl-Heinz wrote: i entered 'Activate screen' in the command window, but the '?' output is still not visible. Anyway, for the moment 'Set Alternate' does what i need.

btw. There´s a FoxConsole.ini, but it seems the values are ignored ? i ve tried these settings but they have no effect.
CompileOnSave=.T.
SaveCmdText=.F.
the names suggest that:
- The source code is automatically compiled -> but it doesn ´t happen.
- The values entered in the command window are not added to the vRunFoxCmd.txt -> but they are still added.