FiveTech Software tech support forums

... Still, as you stated, privates are visible everywhere (even within FW and Harbour code) as long as they are in scope. So you have to worry about naming conflicts in all your code, even code that is unrelated to the Privates. I just don't see any good reason to use Privates. I think they are only ...

... need it for Windows CE (ARM) :-) :oops: So, do you mean "Windows Embedded CE": http://www.elbacom.com/embedded/wince/overview ? :roll: Naming and Branding • The name is now Windows Embedded CE 6.0 • Changing branding color from orange to blue Redesigned Architecture • Redesigned unified ...

Hi all It seems that if I use the same name for the source file of a class as the class itself ( for example CLASS myclass in file myclass.prg ) the harbour compiler gives an error, namely: Error F0002 Redefinition of procedure or function: 'MYCLASS' 1 error and the compilation ( to C source ) fails...

... equivalent FiveWin classes. I rather gather that we can use namespaces to overcome this but I was thinking that it might be good to sort out some naming conventions before we get too far. Regards Doug

... footer, ... via items in an associated ini-file. So far so good. I thought to alter via the same way the behaviour of a button in the buttonbar by naming a function, that is outside the class-object itself, in the ini-file. This function should be compiled at runtime, instead of the build-in standard ...

... DSN to connect to a data source, is that you only need to change code in one place in order for all the references to that code to be effected. Naming of the individual parameters, however, creates a direct connection, is slightly faster, and, of course, the code is clearer to read. You could ...

I saw that I had a mistake in naming the variables. X was y and vice versa. I changed the code. Please lets go ahead with this. Carles: What is local aInfo := oWndPlan:DispBegin() exactly doing? Regards, Otto PS: Could you please send me ...

Quique, Rochinha, NageswaraRao, Carles I saw that I had a mistake in naming the variables. X was y and vice versa. I changed the code. Please lets go ahead with this. Carles: What is local aInfo := oWndPlan:DispBegin() exactly doing? Regards, Otto PS: Could ...

... Personally I would be happier with a 12 or perhaps 16 character limit as witha 10 limit I effectively restrict myself to 7 characters due to my naming scheme (which started out with corporate work with SQL where there is no such limit). I also like to keep comments relatively short and minimalist. ...

... chars That's good. From memory I think it was initially a 9 character limit as documented and I use all 10 allowed in the "standard" because of my naming scheme. For example my data file might be PT_PATIENT with fields such as PT_KEY, PT_FAMLYNM, PT_GIVENNM etc. I know xBase supports alias->fieldname ...

... From the above it appears that oBrw:nAt() always returns ::nColSel. If so where is the need for the method nAt() ? If the intention is to have naming compatibility with TWBrowse and TCBrowse, nAt should have been named nColAct(). This helps easy migration from TWBrowse or TCBrowse to TXBrowse. ...

That would be most welcome.

Other requests are :
1. To add the method SetAdo to TWBrowse and TCBrowse also.
2. To bring uniformity of naming the methods like DrawSelect and Drawline, nAt of xBrowse and nColAct, etc.

... you are getting? Are you inheriting from an existing FWH class or one that you wrote? Have you read my OOP articles on my website? I advise not naming your method PrintCl but rather just Print. Remember that one of the great features of OOP is that you can use the same method name in more than ...

Only to ensure

No more limitation in naming the dbf-files. Is it correct?

use (cdatawin+"marketingliste") new
select marketingliste

Regards,
Otto

... when I need to customize just one or two methods of a FiveWin class (such as the tget class). Ah, yes inheritance is great. Polymorphism (same naming) is also. You can pass around various objects and call the same method (e.g. edit(), print(), delete(), etc.). Incredibly useful! I also encourge ...