| |
| |
|
 | XPSE geupdated. Neuste Version V0.1.3i. See supra.
The through Ragnar acquainted Bugs are eliminating,- one new Compilerschalter is introduced and bisl Feinschliff is happens. 
salvo, iF *coolyeah* |
|
| |
| |
| |
|
|
 | new Version xpse v1.0.3j soeben uploaded.
Compilerschalter $runtime correct,- Compilerschalter $compiler introduced.
Please supra under Compilerschalter nachlesen.
ex now is it dead easy, in the Source To decide, which Compiler/Runtime-Set used go should - circa z.B. between different Profanversionen To discern.
for example:
CompileMarkSeparation {$runtime p9}
{$compiler p9}e>
CompileMarkSeparation {$runtime p8}
{$compiler p8}e>
naturally can also complete way/Dateiangaben made go - xpse respect on it.
salvo, iF |
|
| |
| |
| |
|
|
| small Update uploaded which the XPSE-Window on Win9x-Systemen rather looks can.
(wish of Dietmar horn)
salvo, iF |
|
| |
| |
| |
|
|
| Update soeben uploaded - V0.1.3m
now can yet rather comments go - because /* and */ must not any more on the Beginning of the line stand - separate can even in the middle in a row used go.
CompileMarkSeparationprint &gettickount + "weiterer Text " + + time$()/* remark innerhalb Zeile*//*und nochn Rem inner Zeile*//*0?*/ >
likewise watts XProfan9-Kompatiblität manufactured - the separate of Lines with the : becomes How had interprets - and allows even following Syntax:
CompileMarkSeparationLabels must not self-contained in a new row written go - but ans Zeilenende. otherwise could I during of my Tests fehlerfrei with : nest.
@Dietmar: is The Fensterposition/Size now veränderbar on Win9x?
in the next Version becomes too the ; Semikolon to that separate of Lines possible his. Geproggt ists already - only have I The suitable Passage from the Version V0.1.3m gecancelt, I not yet any Tests completed have. It can then too between : and ; within of/ one row mixed go.
@Frank: I faith, now there one geringes Problem with the Assemblerblöcken - or?
salvo, iF |
|
| |
| |
| |
|
|
| Bugfixupdate uploaded - with Pfadangaben in Compilerschaltern ought to now The :-Trennung not grab.
salvo, iF |
|
| |
| |
| |
|
|
| Update uploaded.
Assemblerblöcke should now correctly. interprets go.
The expansion the Create-function through (:hidden etc) had because of to Kompatiblität To P9 abgeändert go.
from
createtext (%hwnd,,0,0,100,100):disable:vscroll
becomes simply
createtext (%hwnd,,0,0,100,100)~disable~vscroll
.
The colon becomes means to that Tilde.
It can however too furthermore with Createangaben The Positionierung over %percent erfolgen.
in example
CreateText (%hwnd,Text,0%,0%,100%,100%)
for a Text box in the Size of 100% of %hwnd To produce.
salvo, iF |
|
| |
| |
| |
|
|
| Update uploaded.
The Semikolontrennung How from others Languages famous ought to now functions. Please extensively testing.
Simple mögliches example:
CompileMarkSeparationsalvo, iF |
|
| |
| |
| |
|
|
| [quote:615db0a249=Ragnar Rehbein]Hello IF
as further possibility for debugausschriften would I me instead of the spending in a File, optional the edition over OutputDebugStringA in the KERNEL32 wish.
I use to display DebugView (of SysInternals). so is it too possible, netzwerkweit debugausgaben central view.
r.r.[/quote:615db0a249]and very the can the new XPSE with the switch {$debug kernelout}.
to that 1. Male sees one time XProfans Fehlermeldungen together with the View source, the this auslöst. simply super Ragnars idea and the Result is wonderful!
salvo, iF |
|
| |
| |
| |
|
|
| new Version - some buxr fixd. 
salvo, iF |
|
| |
| |
| |
|
|
| new Version - new crazy Bugs. 
@Frank: working now the Inline-Assembler again?
salvo. |
|
| |
| |
| |
|
|
| yet ne newer Version - yet tollere Bux.
small Error in the Module {$replace} terminiert. 
salvo. |
|
| |
| |
| |
|
|
| first XPSE the 0.1.4it generation soebend uploaded. 
I have Vorgereitungen met -
a)whom Source yet optimierter To konvertieren
b)whom Source yet stronger on Unstimmigkeiten To to check on
but deference: there are only Vorbereitungen met - yet happens not plenty!
particularly in the create-area have I the Parser explicit correct.
See this example:
CompileMarkSeparationbut&:=if(o&<3,createbutton(%hwnd,if(o&==1,"RUN ","STOP ")+str$(i&),i&*60,30+o&*30,60,30),createbutton(%hwnd,"",i&*60,50+o&*30,60,20)) >
CompileMarkSeparationBUT&=IF(O&<3,(CREATE("BUTTON",(%HWND),IF(O&=1,"RUN ","STOP ")+STR$(I&),(I&*60),(30+O&*30),(60),(30))),(CREATE("BUTTON",(%HWND),"",(I&*60),(50+O&*30),(60),(20))))>
this allows later genaueres Hinsehen the XPSE on syntaktische Error - How z.B. Parameterzahl etc.
For this has XPSE The quality lost, that Controlgrößenangaben too in % (percent) erfolgen can. of my opinion to having eh nobody these option used. If hereon nevertheless worth laid becomes - so is these simply again To implementieren - I habs me vorbehalten.
XPSE has too another second quality lost - these the one to for ... to ... do ... the begin too omit can - if one only a only commands behind it writes. now any forToDo-creep with a Begin To begin - and one End To terminate. these sure on my own already therefore, that one mehere command - with a Semikolon or with a colon separated - in a row write can, slight To verschmerzen. Both supported the XPSE.
Z.B. so - in link with a if:
CompileMarkSeparationsalvo, iF |
|
| |
| |
| |
|
(899)
Deutsch
English
Français
Español
Italia