RE: Window.Font

> This was done to avoid some name issues.  Since wx.Font also exists,
> using the name 'Font' within a class derived from wx.Window would be
> ambiguous; the attribute would need to be referred to as 'this.Font'.

But this is a pretty general namespace issue. I do not import wx for this
very reason: I like to know visually that I am using something from wx vs.
my own class or even variable.

And since Font is an instance member you are always referring to it via a
variable anyway. And within the definition of wx.Window this.Font would be
used to get around this very problem.

Seems like an odd one off to me that should be nuked in favor of ONLY
Window.Font. It is a mismatch to the wxWidgets docs that is unnecessary. In
fact I noticed Font was added to TextCtrl to fix this issue for it (wrong
place).

-Mike

--
Michael S. Muegel
Dallas, TX



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE. 
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click