This is the mail archive of the
java-patches@sources.redhat.com
mailing list for the Java project.
Re: Patch: more AWT code
- To: Bryce McKinlay <bryce at albatross dot co dot nz>
- Subject: Re: Patch: more AWT code
- From: Tom Tromey <tromey at redhat dot com>
- Date: 03 Jan 2001 01:19:08 -0700
- Cc: Java Patch List <java-patches at sourceware dot cygnus dot com>
- References: <87itnx8osl.fsf@creche.redhat.com> <3A528137.BB8F76BA@albatross.co.nz>
- Reply-To: tromey at redhat dot com
>>>>> "Bryce" == Bryce McKinlay <bryce@albatross.co.nz> writes:
Bryce> Hmm. Lots of these methods don't exist, according to the JDK
Bryce> 1.3 docs. What spec were you working from? I suspect the peer
Bryce> should be mantaining Adjustable objects that provide this
Bryce> functionality, which client code can access with
Bryce> getVAdjustable()/getHAdjustable().
I was looking at the JCL, which is old, I admit.
However, it also tends to be more detailed.
I don't see the part in the 1.3 docs that you refer to. It mentions
that the block increment is not settable; I'll fix this soon. But it
doesn't mention that accessors for these values don't work.
Maybe that is implied because there are no methods in the peer to
retrieve the values. However, I don't see how it can be given the
getScrollPosition's docs:
This is a convenience method which interfaces with the adjustable
objects which represent the state of the scrollbars.
I'm also basing the implementation on the peer specification. This
might not be the best approach.
Tom