Although it may seem as a convenience, there is
an issue from design point of view.
Invalidate is a message sent to a view, which
means "request repaint ASAP". ASAP means that
between the call and actual repaint, control
goes through the message loop. These mechanisms
are beyond the scope of the gl2, graphics API.
For example, assuming the drawable can be a bitmap,
invalidate does not make sense.
A custom control should maintain the graphics view ID
for many reasons: glsel, hooking events, etc.
So the ID is available. And the custom control stands
above the low-level gl2 API, so it's OK for it
maintain the information related to both the drawable
and the view.
Isigraph is a two faced object: it's both a
WD view and a gl2 drawable. But the gl2 and wd
APIs are separate and should be mixed.
Here's a dependency and levels relationship
custom control
/ \
gl2 WD
/ \ / \
bitmap isigraph button
--- Eric Iverson <[EMAIL PROTECTED]> wrote:
> Idea possibly has merit, but won't be included at this late date in the
> beta.
>
> ----- Original Message -----
> From: "bill lam" <[EMAIL PROTECTED]>
> To: "Beta forum" <[email protected]>
> Sent: Monday, September 04, 2006 9:50 AM
> Subject: [Jbeta] glinvalid ?
>
>
> > how about add a new gl2 cmd "glinvalid" that setinvalid the current
> > glsel
> > isigraph, so that it does not need child control name for updating?
> >
> > glinvalid ''
> >
> > --
> > regards,
> > bill
> > ----------------------------------------------------------------------
> > For information about J forums see http://www.jsoftware.com/forums.htm
>
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
