... hDC, cText, oFont, nWidth ) corrected by Nageswarao On your sample: oPaneltext cannot be the same name of a Panel I propose to usare oTExt MEMOTEXT := alltrim( cMsg ) @ oPanel2:nTitleHeight+5, 10 GET oText VAR MEMOTEXT SIZE oPaneltext:nWidth-2, oPaneltext:nHeight-40 PIXEL MEMO NO ...
... DEFINE DIALOG oIndex TITLE "Generado Facturas en PDF" FROM 1,1 TO 3,40 @0,2 SAY oText PROMPT xsay OF oIndex COLOR CLR_HBLUE Font m->oFontFis ACTIVATE DIALOG oIndex NOWAIT CENTER do while !eof() xnum:=99->numero VTA1100PE() ...
hi, Of course: oText_2 is not a property of oASKFORM, it is a local variable! right but i use "OF" which work under HMG "as expect" using "semi-OOP" Syntax I think you should have to carefully read a good book about OOP. :-) sorry, it work that Way under Xbase++ and HMG...
hi Enrico, Ok, understand so i have to make a own CLASS and use CLASS Code / DATA when i do not want to pass Parameter --- have forgot to say that i have DATA oASKFORM and made this ::oASKFORM := oASKFORM but still my Question about Object and "OF Parent" when assign Object to a Parent, ...
hi, when using #xCommand Syntax in CLASS like this LOCAL oText_2, cTargetDir DEFINE WINDOW oASKFORM FROM 0,0 TO 270, 534 PIXEL TITLE cAction @ 110,10 GET oText_2 VAR cTargetDir SIZE 500,30 PIXEL FONT oFontDefault OF oASKFORM will VAR "cTargetDir" be Property of oText_2 :?: if YES can ...
... mouse or keyboard cursors I can scroll it but the scroll at left of the control not run Your test local cMessage:=Memoread(cFiletxt) @ 35, 4 GET oText VAR cMessage OF oDlg ; :?: placed inside the main-dialog see my first get MEMO READONLY COLOR CLR_BLUE SIZE 300, 100 PIXEL I added some tests ...
... with the mouse or keyboard cursors I can scroll it but the scroll at left of the control not run local cMessage:=Memoread(cFiletxt) @ 35, 4 GET oText VAR cMessage OF oDlg; MEMO READONLY COLOR CLR_BLUE SIZE 300, 100 PIXEL https://i.postimg.cc/d0cS9zHM/scr.jpg I tried also with ...
... for your kind responses. Sorry, but I meant without using a dialog, only the advantages of MsgMeter (if there is a simple way). There is also a oText and oDlg object there, so maybe... You cannot beat one line of code with at least 20 lines of creating and administrating yourself a dialog :( ...
If you use SAY( x,y, oText, oFont, nWidth, nClrText ) in tPrinter, and specify a nClrText, it should be used only for that oText specified, and return to default. Instead, any further calls where nClrText is not specified will print ...