Seamless MinMax ToDo ?
Paulo Pacheco <[email protected]>
| Newsgroups | gmane.network.rdesktop.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi all !!
I came across the notes.txt file, in the seamless package, where it states:
______________________________________________________________________
todo:
-----
<WINDOW WORK>
-support dos boxes/special cases (see:
http://www.macadamian.com/column/windowshooks.html)
<TASKBAR WORK>
-maximise implementation
-'un-maximise' implementation
-minimise implementation
-min/max of windows works with items on the taskbar
-when window title changes on server, change it on client as well
. . .
Limitations:
------------
-Must run in fullscreen mode. Client screen res must be set to a
compatable TS screen res.
______________________________________________________________________
Looking at the clipper.cpp code, line 166, there is indeed a " // TODO
" for the MINMAX case:
______________________________________________________________________
. . .
} else if ( strcmp( messageType, "HCBT_MINMAX" ) == 0 ) {
if ( OUTPUT_DEBUG_INFO == 1 ) {
OutputDebugString
( "TS WINDOW CLIPPER :: CLIENT DLL :: Info -->
Message was of type HCBT_MINMAX" );
}
//TODO
} else if ( strcmp( messageType, "HCBT_MOVESIZE" ) == 0 ) {
. . .
______________________________________________________________________
Could anyone please clarify to me:
- Does it mean that, in seamless mode, min / max / restore operations
are not supposed to work?
- Why certain apps (eg. Excel, MS-Word, etc) do
maximise/restore/minimise (with bugs in xfwm4, but better in
metacity)?
- What would be this TODO part related to? Any hints, please?
Thanks a lot !!!
Paulo Pacheco
------------------------------------------------------------------------------