Hi Karl,
> The default content pane is at least JXPanel. You can cast (*shudder*) and set a painter.
Yeah, I've seen the JXPanel. Unfortunately can't use a painter. I'm wrapping many swing/swingx widgets for a programming language providing an own painting system, i.e. it doesn't expose painters, therefore I'm forced in replacing the contentPane.
> Why do you need to extend it? Why is extending it useless? I'm not seeing your point.
Because also extending the JXTaskPane I would not have access to the JXPanel's container, that is the XCollapsiblePane, which is precisely private.
In other words, what is missing IMO is something like
JXTaskPane.setContentPane
or
JXCollapsiblePane.setContentPane
if the latter would be at least protected.
In general, I would say, but very quietly :-), if you, I mean the swingx developers, can avoid, or at least limit, putting restrictions that prevent access or the replacement of components' internals, as sometimes what the API exposes by default is not enough to satisfy some special needs (what, all things considered, was the distinguishing aspect of Swing, in my opinion).
This of course does not stop me to thank you for the great job you are pursuing with Swingx (with Jeannette, Alex, etc.. of course)
Lucio
[Message sent by forum member 'luciobiondi' (
lbiondi@...)]
http://forums.java.net/jive/thread.jspa?messageID=369443---------------------------------------------------------------------
To unsubscribe, e-mail:
jdnc-unsubscribe@...
For additional commands, e-mail:
jdnc-help@...
