Hi
Przemysław Czerpak wrote: > > I'm afraid that I do not know what is the problem and what you > want to do. The above PP rule is correct so it will work. > Anyhow if QTextCursor() is class function then each call to > QTextCursor() create new object of QTextCursor class. > Is it a problem? > Or maybe you only want to pass more parameters to :configure() method? > If yes then it's enough to change the PP rule to: > #xtranslate QTextCursor( <x,...> ) => QTextCursor():configure( <x> ) > This is the situation: QTextCursor() is a class and :configure( xObject ) is its method resturning self. In application code I have frequent calls like this: QTextDocument():configure( ::qEdit:document() ):setModified( .f. ) / OR / qDoc := QTextDocument():configure( ::qEdit:document() ) qDoc:setModified( .t. ) I want to reduce code which must be eliminated as QTextDocument( ::qEdit:document() ):setModified( .f. ) / OR / qDoc := QTextDocument( ::qEdit:document() ) qDoc:setModified( .t. ) But it GPFs because call QTextDocument() returns the class object itself. So the above notation fails. I realize that this cannot be achieved like this. Or you may forward another solution. Regards Pritpal Bedi -- View this message in context: http://old.nabble.com/Classes----xtranslate-QTextCursor%28-%3Cx%3E-%29-%3D%3E-QTextCursor%28%29%3Aconfigure%28-%3Cx%3E-%29-tp27250898p27251307.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
