Bug 64846

Summary:	[CTabFolder] CTabFolder's maximize tracking indication is not cleared when view maximized
Product:	[Eclipse Project] Platform	Reporter:	Nick Edgar <n.a.edgar>
Component:	SWT	Assignee:	Duong Nguyen <duongn>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	steve_northover
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Nick Edgar

2004-05-31 17:05:49 EDT

build I20040529-0105

- move the mouse over the maximize button of a view
- the white tracking rectangle appears
- click without moving the mouse
- the view is maximized, but the tracking rectangle is still visible
- move the mouse
- the tracking rectangle disappears

Comment 1 Nick Edgar

2004-05-31 17:06:05 EDT

Problem does not occur when the view is restored.

Comment 2 Steve Northover

2004-06-01 09:29:22 EDT

Vikki to assess and advise.

Comment 3 Veronika Irvine

2004-06-01 10:39:32 EDT

I don't see the problem.

Go to the Package Explorer.  
Move the mouse over the "collapse all items" tool item.  Notice that it 
becomes "hot".
Click on the toolitem without moving the mouse.
Notice that the toolitem remains hot.

This seems to be normal toolitem behaviour.  The only time the toolitem looses 
its hotness is if it causes a dialog to be opened and the dialog takes focus.  
The minimize/maximize/restore buttons on CTabFolder are supposed to act like 
tool items.

Comment 4 Nick Edgar

2004-06-01 11:22:59 EDT

The problem is that clicking on maximize moves the button elsewhere, so it is no
longer under the mouse pointer, so it should not be tracking.

Comment 5 Veronika Irvine

2004-06-01 11:38:44 EDT

On Windows XP, the "hot" rectangle disappears immediately when the widget is 
maximized (if the button moves).  Will have to try this on Windows 2000.

Comment 6 Nick Edgar

2004-06-01 14:56:24 EDT

I can demonstrate it on my laptop if you like.

Comment 7 Eclipse Webmaster

2019-09-06 16:11:16 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.