U++ framework: U++ Library : Other (not classified elsewhere)

Home » U++ Library support » U++ Library : Other (not classified elsewhere) » subclassing LineEdit is ugly

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Re: subclassing LineEdit is ugly [message #2565 is a reply to message #2562]

Tue, 18 April 2006 00:15

mirek
Messages: 14290
Registered: November 2005

Ultimate Member

hojtsy wrote on Mon, 17 April 2006 17:38

The only cost is minimal CPU overhead.

I do not care about virtual method overhead here (not a bit). But I am very concerned about fuzzy interfaces.

One problem with this approach is: where are limits?

String::Cat ?
Ctrl::HSizePos ?
DrawLabel::GetSize ?

Another problem is that introducing too much virtual methods often exposes too much of implementation details.

Now about our specific example: I see LineEdit as "blackbox" with defined (and final) operations, which has "default interface" represented by current "Key" method and default menu.

If you want more than "default interface", simply change the interface part (that one is well defined in Ctrl).

Mirek

Report message to a moderator

[Message index]

		subclassing LineEdit is ugly By: hojtsy on Sun, 09 April 2006 21:46
		Re: subclassing LineEdit is ugly By: mirek on Sun, 09 April 2006 22:11
		Re: subclassing LineEdit is ugly By: hojtsy on Sun, 09 April 2006 23:29
		Re: subclassing LineEdit is ugly By: fudadmin on Mon, 10 April 2006 01:48
		Re: subclassing LineEdit is ugly By: mirek on Mon, 10 April 2006 10:08
		Re: subclassing LineEdit is ugly By: hojtsy on Mon, 17 April 2006 23:38
		Re: subclassing LineEdit is ugly By: mirek on Tue, 18 April 2006 00:15

Previous Topic:	Add and AddPick should return reference to added element
Next Topic:	uvs wishes

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Apr 25 04:51:42 GMT+2 2026

Total time taken to generate the page: 0.00573 seconds