Enrico
Enrico Maria Giordano wrote: > > Maybe I'm missing something but the following sample > > #xtranslate TestX(<r>,<c>,<x>,[<l>],<g>) => TestY( <r>,<c>,<x>,<l>,<g> ) > #xtranslate TestX(<r>,<c>,<x>,[<l>]) => TestY( <r>,<c>,<x>,<l>,h ) > > #xtranslate test( => testx( > I was experimenting with other example, not yours. Yours is OK too but it needs that function call is always done in UPPER case, here as, TEST. Here is what I experimented: //-----------------------------------------// // // hGT will be the application defined variable name to hold GT context handle // This is along the line of GetList public variable. // #define VAR_GT hGT #xtranslate DispOutAtX(<r>,<c>,<x>,[<l>],<g>) => DispOutAtY(<r>,<c>,<x>,[<l>],<g>) #xtranslate DispOutAtX(<r>,<c>,<x>,[<l>]) => DispOutAtY(<r>,<c>,<x>,[<l>],VAR_GT) #xtranslate DispOutAt( => DispOutAtX( FUNCTION GTOutPut() Local nHandle Local hGT DispOutAt( 10,10,'dara','w+/r' ) DispOutAt( 12,10,'lara','w+/b',nHandle ) Return nil //-----------------------------------------// // The code below be clubbed in another PRG //----------------------------------------// // // Only if the function below is part of same prg // #untranslate DispOutAt( Function DispOutAtY( a,b,c,d,e ) Return DispOutAt( a,b,c,d,e ) //-----------------------------------------// This way all GT commands/functions can be isolated in other PRG/INCLUDE and if multi-window functionality is needed #include and link script is enough. No need to change the code. PPO output: Function GTOutput() Local nHandle Local hGT DispOutAtY(10,10,"dara","w+/r",hGT) DispOutAtY(12,10,"lara","w+/b",nHandle) Return nil Function DispOutAtY( a,b,c,d,e ) Return DispOutAt( a,b,c,d,e ) Regards Pritpal Bedi, INDIA-USA -- View this message in context: http://www.nabble.com/A-Question-on-Directives-tp14573513p14602890.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
