This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 47854 - [40cat] Ability to maximize sliding windows
Summary: [40cat] Ability to maximize sliding windows
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: David Simonek
URL:
Keywords: UI
: 54470 (view as bug list)
Depends on:
Blocks: 41470
  Show dependency tree
 
Reported: 2004-08-25 06:06 UTC by coldrick
Modified: 2008-12-22 14:56 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description coldrick 2004-08-25 06:06:45 UTC
[ BUILD # : beta 1 ]
[ JDK VERSION : J2SE 1.4.2_05 ]

The quick start for web apps in the "Compiling and Running a Project" section suggests maximising the output window by double-clicking the titlebar.

Doesn't work for me, nor does Shift-Esc. Works for other windows, but not the Output Window
Comment 1 Jan Chalupa 2004-08-29 21:46:21 UTC
Re-assigning from 'ui'. I can maximize Output window by double-click 
just fine in build #200408262030. I haven't tried the web apps quick 
start though.
Comment 2 Milos Kleint 2004-08-30 07:50:58 UTC
reassigning
Comment 3 Milos Kleint 2004-08-30 15:18:52 UTC
works for me as well. One usecase where it doesn't work, is when the
output is in auto-hide mode (it has a button on the bottom edge). when
such component slides into desktop, it cannot be maximized.

Closing as worksforme, please provide additional information (steps to
reproduce, screenshots etc)

CCing dsimonek: Is the maximizing of auto-hide windows planned for
next release? I could not find it in the spec.
Comment 4 coldrick 2004-08-31 05:59:18 UTC
oho! Didn't know about the  auto-hide.

Since the output window is obviously set to auto-hide by default, this
could be very confusing for a user.

Maximising auto-hide windows makes sense to me.
Comment 5 Milos Kleint 2004-09-01 09:28:56 UTC
No, none of the windows is currently set to autohide by default.

while resizing of autohide windows makes sense to me, I'm not
completely sure about maximization.
Comment 6 Milos Kleint 2004-09-24 12:14:08 UTC
not to be done for 4.0
Comment 7 Jesse Glick 2004-10-04 17:10:51 UTC
I agree that it should be possible to maximize sliding windows. Why
not? I sometimes want to see the OW in full-screen mode, yet I
normally keep it in sliding mode. Annoying to have to take it out of
sliding mode first.
Comment 8 David Simonek 2004-10-05 10:13:47 UTC
I agree. Changing to task (enhancement) for next release and ccing HIEs.
Comment 9 David Simonek 2004-10-12 17:13:35 UTC
Prioritizing.
Comment 10 Milos Kleint 2005-01-03 07:48:54 UTC
maximizing the sliding windows has some problems IMHO.

1. there's close to nonexisting visual indication that a component is
maximized. Adding sliding windows maximalization creates another
slightly different user mode to the existing ones, again without a
clear visual indication of the current state of the system.
2. how permanent should the maximalization be? when the editor mode is
maximized, all opened documents can be iterated. Does maximazing the
output window also affect all the other components on the lower
slidebar? or is it just for the output window.
3. when the sliding window is closed/hidden, does it mean the
maximized mode is still on or cancelled?
4. how shall the auto sliding on hovering over the slidebar button
work under maximized mode?
Comment 11 dpavlica 2005-01-13 15:00:06 UTC
Just summary after discussion with Milos:

1. there's close to nonexisting visual indication that a component is
maximized. Adding sliding windows maximalization creates another
slightly different user mode to the existing ones, again without a
clear visual indication of the current state of the system.

I suggested to add restore icon in the toolbar of window, when this window is maximized. 
I will request it from our visual designer (For Metal, XP and Classic). 

2. how permanent should the maximalization be? when the editor mode is
maximized, all opened documents can be iterated. Does maximazing the
output window also affect all the other components on the lower
slidebar? or is it just for the output window.

I tended to say "Just for maximized window" first. But then I played with IDE and tried to 
imagine that iteration (sharing of maximized state by more auto hidden windows) and I 
think, that isn't bad idea. But I am not sure in this and it should by checked by real 
usecases or on usability study. So is it possible to implement this sharing of max state?

3. when the sliding window is closed/hidden, does it mean the
maximized mode is still on or cancelled?

Yes, maximized mode shouldn't be persistent mode, but only temporary one.

4. how shall the auto sliding on hovering over the slidebar button
work under maximized mode?

What do you mean by this exactly?
Comment 12 Milos Kleint 2005-02-03 14:04:59 UTC
*** Issue 54470 has been marked as a duplicate of this issue. ***
Comment 13 colorblind 2005-05-13 16:07:04 UTC
wouldn't it be nice the following strict behaviour:

if a window i autohiding 

1) when you dbl-click the title bar it becomes maximized (permamently) with no
mimize button
2) when you dbl-click the title bar again it goes back to autohiding status

ciao,

Comment 14 Marian Mirilovic 2005-10-04 11:51:45 UTC
The last comment is more enhancement, than task
Comment 15 Milos Kleint 2006-07-27 07:38:37 UTC
reassigning to dsimonek
Comment 16 Stanislav Aubrecht 2007-08-03 18:06:06 UTC
it is possible to maximize/restore slided out windows in nb6.0, closing as fixed
(pls reopen if you want a different behavior)