Work in Progress. The server keeps the client window up to date on layer movement/resizing. This fixes quite a few problems and brings support for FrameMoved and Resized hooks. But implementing it this way has its own set of problem, most importantly: When a BView calles Window()->CurrentMessage() in its FrameMoved/Resized hooks, it will see something very different from what it would see in R5. This needs to be fixed, but I have not had a good idea how to do this other than faking the current message in BWindow, which I didn't look into.

git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@12689 a95241bf-73f2-0310-859d-f6bbb57e9c96
2005-05-16 15:39:58 +00:00
parent a1c5fb3432
commit ad6b480400
6 changed files with 102 additions and 16 deletions
@@ -122,7 +122,8 @@ ServerWindow::ServerWindow(	const char *string,
 	// fClientWinPort is the port to which the app awaits messages from the server
 	fClientWinPort(winport),
 	fClientLooperPort(looperPort),
-	fHandlerToken(handlerID)
+	fHandlerToken(handlerID),
+	fClientViewsWithInvalidCoords(B_VIEW_RESIZED)
 {
 	STRACE(("ServerWindow(%s)::ServerWindow()\n",string? string: "NULL"));