Hi Frank,
Frank Schönheit - Sun Microsystems Germany escribió:
Hi Ariel,
the C++ VCL tree controls inside OOo work just like always did, it's
only the UNO tree control that has this painting issue
Interesting.
(buy the way, I tested it on Win XP, Solaris, and Linux SuSe on my PC,
AND in different PCs, notebooks, etc. - so it seems to be an issue, not
only happening to me ; and this gives me second thoughts: how did it
pass the QA? didn't anyone test it with a simple sample?
AFAIK, the Object Inspector SDK sample was migrated to the AWT tree
instead of a Swing tree control.
this may sound like I'm not very modest, but I've got some skills on OOo
AWT Api :-) - the OOo AWT version of the Java Swing ScriptSelector
openoffice.org2.3_sdk/examples/DevelopersGuide/ScriptingFramework/ScriptSelector
that you see in the document on the issue tracker was done by me :-)
(may be you are talking about another one :-) ).
I translated the Dev's Guide example from Java Swing to OOo AWT in Java
bridge and in OOo Basic (if you see with attention, my version
distinguish the different containers with different icons, and the
different doc's models in the Desktop -- of this last one not so proud,
because I still got some issues, as the Scripting Framework API does not
tell us anything about the doc. model)
So, there has been testing, thus I
assume the behaviour is a) not present in all setups or b) not present
from the beginning of development (i.e. has been introduced after the
control was finished). I tend to believe the latter, since an issue as
this would in fact not have survived any QA.
may be they did just like me: I realized about the "childs" issue on 07
September, as soon as I could read the IDL files
http://api.openoffice.org/servlets/ReadMsg?list=dev&msgNo=18155
but as I was using the NetBeans IDE on Win XP (on Linux doesn't work so
well) with Metal Look and Feel, I didn't realize this painting issue...
and for some specs. I see some of you people are using Win XP with the
same L&F.
am I the only
one in all the world testing the new tree control? It's very strange for
me not to have heard questions on the API mailing list concerning some
other features of the tree control :-( )
Admittedly, there seems to be some advertising missing.
Done !! See
http://www.openoffice.org/nonav/issues/showattachment.cgi/49297/AWT_TREE_sample_code.odt
Will try to find to have a quick look. You might also have noticed I
nominated the issue as 2.3.1 blocker (though I don't think it will be
accepted, but it's worth a try).
I do not have many hopes on that: CL said the "childs" issue "will be
fixed for OOo 2.4. So please be aware that an incompatible
change to the interface is comming."
http://api.openoffice.org/servlets/ReadMsg?list=dev&msgNo=18263
So I will wait until 2.4
It's really frustrating all this story with the tree control: with it's
"childs" on demand and this issue, the new control is completely useless.
I have some extensions in mind, some are for this project: for example,
to my "extended version" of the DirectSQLDlg
http://www.arielconstenlahaile.com.ar/ooo/temp/DBExtras_XSQLDirect_04.png
I wanted to add a tree, like most front-end have, to display the
database structure -- tables, fields, type of fields, etc. -- very
useful when performing SQL DDL...) but all I can do is play around
(other features of the tree control, like in-place editing, I still
can't make them work, so either it's a lack of skills from my part, or
may be they are issues :-( -- in the case of in-place editing I tend to
think I'm doing something wrong == I'm so used to the JTree where you
just set a property!!!)
By the way, was I right assigning this to cl? isn't he the one how
developed the tree control?
Yes and perhaps not (in reverse order) :)
CL (Christian Lippka) designed and implemented the API wrapper around
the existing tree control. Thus, the issue will finally appear on his desk.
However, in a normal work flow, an UNCONFIRMED issue manifests in QA,
which evaluates and finally confirms and assigns it. The main difference
is the "confirms": People tend to overlook UNCONFIRMED issues, since
there are way too many of them. Especially developers are simply unable
to evaluate *all* unconfirmed issues, that's done by QA.
Thus, assigning an unconfirmed issue to a developer is somewhat probably
to be a one-way road, for quite some time.
So: Either look for somebody confirming the issue (NEW, but untargeted
issues *do* appear on a developer's radar regularily), or assign it to QA.
Can I change the status from UNCONFIRMED to NEW? I think we simple users
can not do this, am I wrong?
Well, this makes me think about what I did wrong with issue
http://www.openoffice.org/issues/show_bug.cgi?id=81985
It's been a moth...and nothing. It's serious because it makes OOo crash!!!
This is the typical case where I had no idea to which component submit
the issue, and the issue tracker help didn't give me much advice on the
topic: as it is something that happens inside the IDE I thought... but
is also something with embedded objects ... and ...
I send error reports ... and ... also nothing happens...
Well... seems like some day I'm gonna issue an issue to the issue
tracker ;-) . The way it is designed and all the stuff involved does
not make it easy for us people testing dev's snaps. and tying to help.
Bye and thanks for your time (in something that does not concern your
project :-) )
Ariel.
--
Ariel Constenla-Haile
La Plata, Argentina
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.arielconstenlahaile.com.ar/ooo/
"Aus der Kriegsschule des Lebens
- Was mich nicht umbringt,
macht mich härter."
Nietzsche Götzendämmerung, Sprüche und Pfeile, 8.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
