+1,
Thanks
Vivi
On 1/14/2016 4:02 AM, Alexander Scherbatiy wrote:
The fix looks good to me.
Thanks,
Alexandr.
On 1/14/2016 12:06 AM, Pete Brunet wrote:
How does this look?
http://cr.openjdk.java.net/~ptbrunet/JDK-8145735/webrev.01/
Pete
On 1/13/16 7:16 AM, Alexander Scherbatiy wrot
The fix looks good to me.
Thanks,
Alexandr.
On 1/14/2016 12:06 AM, Pete Brunet wrote:
How does this look?
http://cr.openjdk.java.net/~ptbrunet/JDK-8145735/webrev.01/
Pete
On 1/13/16 7:16 AM, Alexander Scherbatiy wrote:
On 1/13/2016 1:12 AM, Pete Brunet wrote:
Hi Alexandr,
On 1/12/16
How does this look?
http://cr.openjdk.java.net/~ptbrunet/JDK-8145735/webrev.01/
Pete
On 1/13/16 7:16 AM, Alexander Scherbatiy wrote:
> On 1/13/2016 1:12 AM, Pete Brunet wrote:
>> Hi Alexandr,
>>
>> On 1/12/16 1:03 PM, Alexander Scherbatiy wrote:
>>> It seems that there still is the case when tab
On 1/13/2016 1:12 AM, Pete Brunet wrote:
Hi Alexandr,
On 1/12/16 1:03 PM, Alexander Scherbatiy wrote:
It seems that there still is the case when tab titles are empty
string, tab components are null, components are not null and the
correct index should be returned for the given page.
In the cod
Hi Alexandr,
On 1/12/16 1:03 PM, Alexander Scherbatiy wrote:
>
> It seems that there still is the case when tab titles are empty
> string, tab components are null, components are not null and the
> correct index should be returned for the given page.
In the code of the current webrev (webrev.00) i
It seems that there still is the case when tab titles are empty string,
tab components are null, components are not null and the correct index
should be returned for the given page.
May be it is better to replace searching the page index by tab component
to by component?
We already do this
Please review this patch:
http://cr.openjdk.java.net/~ptbrunet/JDK-8145735/webrev.00/
The issue being resolved is that the JTabbedPane code can't solely rely
on tabComponent when fetching the index in the parent component.
tabComponent is optionally used and its presence indicates that the
assoc
