nanogui: repeated XSetClipMask question
Subject:
Re: [nanogui] repeated XSetClipMask question
From:
"Greg Haerr" ####@####.####
Date:
14 Jan 2007 17:04:36 +0000
Message-Id: <1b7701c737fd$ff40d140$6401a8c0@winXP>
: 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
