nanogui: repeated XSetClipMask question
Subject:
Re: [nanogui] repeated XSetClipMask question
From:
Robin Clark ####@####.####
Date:
15 Jan 2007 09:44:49 +0000
Message-Id: <929296.89711.qm@web25513.mail.ukl.yahoo.com>
Hi,
We fixed this memory leak by making the
region a static pointer and calling destroy on
re-entering the function if the pointer is not null.
old C++ trick ;-)
Robin
--- Greg Haerr ####@####.#### wrote:
> : that "isXSetClipMask 285" indicates any memory
> leak?
>
> As indicated in the NXLIB source, there's currently
> a memory
> leadk in XSetClipMask, a region is allocated and
> not free'd. You should the the FLTK underchassis to
> see
> where XSetClipMask is used, and then determine where
> a call to GrDestroyRegion might called from.
>
>
> : it it correct to implement an updatin clock in
> this way?
> : Which is the correct way to implement an updating
> clock?
>
> I'm not big on C++, so I can't give advice here.
> Another
> idea might be to keep a drawable around and use a
> timer
> to draw the new time when required, without
> recreating
> the FL_Output* each time.
>
> Regards,
>
> Greg
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> ####@####.####
> For additional commands, e-mail:
> ####@####.####
>
>
___________________________________________________________
What kind of emailer are you? Find out today - get a free analysis of your email personality. Take the quiz at the Yahoo! Mail Championship.
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk
[Content type text/x-csrc not shown. Download]
