[gedmurphy] 36668: It looked like we could get away with removing this hack, but it seems it still causes painting problems when increasing the width. No time to investigate at the moment. (anyone else wanna take a look?)

Author: gedmurphy
Date: Mon Oct  6 14:15:09 2008
New Revision: 36668

URL: http://svn.reactos.org/svn/reactos?rev=36668&view=rev
Log:
It looked like we could get away with removing this hack, but it seems it still causes
painting problems when increasing the width. No time to investigate at the moment. (anyone
else wanna take a look?)

Modified:
    trunk/reactos/base/shell/explorer/shell/mainframe.cpp

Modified: trunk/reactos/base/shell/explorer/shell/mainframe.cpp
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/base/shell/explorer/shell/…
==============================================================================
--- trunk/reactos/base/shell/explorer/shell/mainframe.cpp [iso-8859-1] (original)
+++ trunk/reactos/base/shell/explorer/shell/mainframe.cpp [iso-8859-1] Mon Oct  6 14:15:09
2008
@@ -306,8 +306,15 @@
 		break;
 
 	  case WM_SIZE: {
-		resize_frame(LOWORD(lparam), HIWORD(lparam));
-		SendMessage(_hwndrebar, WM_SIZE, 0, 0);
+#ifdef __REACTOS__	///@todo Work around to display rebar in ROS (with flickering) as long
as the control isn't fixed
+		int height = SendMessage(_hwndrebar, RB_GETBARHEIGHT, 0, 0);
+		MoveWindow(_hwndrebar, 0, 0, LOWORD(lparam), height, TRUE);
+#else
+ 		resize_frame(LOWORD(lparam), HIWORD(lparam));
+ 		SendMessage(_hwndrebar, WM_SIZE, 0, 0);
+#endif
+
+
 		break;}	// do not pass message to DefFrameProc
 
 	  case WM_GETMINMAXINFO: {