Re: Making wxnet API more C# like.

Jesus Garcia <[email protected]>
Newsgroups gmane.comp.lib.wxwindows.wxnet
Message-ID <[email protected]>
Excellent!, 

I will experiment with it tonight.

-J

On Sat, 31 Jul 2004 19:15:48 +0200, Alexander Olk
<[email protected]> wrote:
> Am So, den 25.07.2004 schrieb Jesus Garcia um 14:31:
> > I have two suggestions for improving the wxnet API.
> >
> > I like the new event model, but it still feels awkward defining ID
> > Constants for each control.
> >
> > The first enhancement should be a static class variable for the base
> > wxobject, that holds the next available id. We can increment this
> > value every time a control is created, giving us nicer API.
> 
> I've added something like this to cvs head. The only difference is that
> class Window holds that static variable (uniqueID) and not wxObject
> because only Window derived classes use id's...
> 
> Just call the ctor of a Window/Control without the id parameter. An id
> will then be added automatically. To get the value of the id call
> myWindow.ID.
> 
> --
> Alexander Olk
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> 
> 
> _______________________________________________
> wxnet-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wxnet-users
>


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.