[Closed] SDK: Rollout Panel issues

Hi scorpion, good to hear from you…again

I’ve attached the RC file (VS 2005) so you can have a look over it…I will have a look over the debug when I next get a chance…

Thanks for the ideas

Shane

I had a look at the debug suggestion it remained as s_ok through out the execution the creation methoth (where I setup the window).

It is possible the the window is invisible, although I thought I set the visibility property on the resource and createWindow style to visible…but these things could have been overlooked.

I wondering if it might have to do with the type of panel I’m using…

Shane

Knew it was something stupid

Though personally, from a style POV, I’d refactor your code and get rid of the seemingly useless CreateDynamicControl() function. It looks like a unnecessary wrapper around CreateWindow that adds little functionality, if any. Your CreateDynamicRollupWindow hides the return value of CreateWindow, which you could have used directly in <whatever the main method is called> for ICUIFrame::SetContentHandle().
Yeah, I tend to over abstract, it’s a bad habit…

Shane

Just a quick update, I tried that and it mad no difference…or least from what I can see

I still get the “scrollable” area of the RollupWindow, which, as I understand it, is capable of holding 0 or more RollupPanels…and in fact, when the plugin first loads, it shows the scrollbar…which is making me think that SOMETHING is happening…

However, I’m not seeing the roll up panel when the plugin loads…My expectation is that I’ll get the normal “RollUp”, with a title area, bounding box and expand/collapse control…now either I’m doing something wrong or my expectations are incorrect…

I will have a look at the custom control example tommorrow and see if I can un-earth anything. If you have any other strokes of brillance, let me know…

Cheers
Shane

Yes, this has been working quite fine since I changed the content type TO hwnd, and before I set the hWnd

Could you post your dialog procedure for the rollup panel, and DoLayout()’s code, and does your message handler do anything ‘funny’ (pCUIFrame->InstallMsgHandler(this)) ?

Perhaps post the (modifed) complete method source too.
Yep, not problem. I’ve attached the source code (as much as I can and stay under the 2 meg limited)

DoLayout – This method only effcts the pRollupWindow so far, it will handle the remaining windows eventually…

void CustomToolBar::DoLayout() {

	// Get the various window rectangles
	RECT windowRect;
	RECT clientRect;
	RECT maxClientRect;
	GetWindowRect(pCUIFrame->GetHwnd(), &windowRect);
	GetClientRect(pCUIFrame->GetHwnd(), &clientRect);
	GetClientRect(GetCOREInterface()->GetMAXHWnd(), &maxClientRect);

	// Default spacing within the main CUIFrame
	int hGap = 10;
	int vGap = 10;

	// The default top/left offset
	int xOffset = 5;
	int yOffset = 5;

	// Allow for some additional spacing at the top of the window for the
	// CUIFrames handles
	if (pCUIFrame->GetCurPosition() != CUI_FLOATING) {

		vGap = 15;
		yOffset = 10;

	}

	// Calculate the new client area
	int width = (clientRect.right - clientRect.left) - hGap;
	int height = (clientRect.bottom - clientRect.top) - vGap;

	// Layout the pRollUpWindow...
	MoveWindow(pRollupWindow->GetHwnd(), xOffset, yOffset, width, height, TRUE);

}

DynamicRollupDialogProc – Does nothing, as yet…although I might use it to manage the individual rollups contents…

INT_PTR CALLBACK DynamicsRollupDialogProc( HWND hDlg, UINT message, WPARAM wParam, LPARAM lParam ) {

	switch ( message ) 
	{
		case WM_INITDIALOG: 
		{
			DebugPrint("WM_INITDIALOG
");
			break;
		}
			/*
			 DLSetWindowLongPtr(hDlg, lParam);
			 dlg = (JiggleTrackDlg*)lParam;
			 dlg->dynDlg = hDlg;
			 dlg->InitDynamicsParams();
			 return TRUE;
			*/
		case WM_DESTROY:
		{
			DebugPrint("WM_DESTROY
");
			break;
		}
	}

	return FALSE;

}

ProcessMessage – This handles the CUI_POSDATA_MSG, WM_GETMINMAXINFO and, WM_SIZE messages…Yes, I know the breaks after the returns are redundent, force of habit

int CustomToolBar::ProcessMessage(UINT message, WPARAM wParam, LPARAM lParam) {

	switch(message) {
		case CUI_POSDATA_MSG: 
		{

			CUIPosData **cpd = (CUIPosData **)lParam;

			cpd[0] = this;

			return TRUE;

			break;
		}
		case WM_INITDIALOG: 
		{
			DebugPrint("ToolBarMsgHandler.WM_INITDIALOG
");
			break;
		}
		case WM_DESTROY:
		{
			DebugPrint("ToolBarMsgHandler.WM_DESTROY
");
			break;
		}
		case WM_GETMINMAXINFO: 
		{

			DebugPrint( _T("wm_getMinMaxInfo
") );
			MINMAXINFO * pMinmax =( MINMAXINFO *)lParam ;

			int width = GetWidth(CUI_MIN_SIZE, CUI_FLOAT);
			int height = GetHeight(CUI_MIN_SIZE, CUI_FLOAT);

			pMinmax->ptMinTrackSize.x = width;
			pMinmax->ptMinTrackSize.y = height;			
			pMinmax->ptMaxTrackSize.x = width;
			pMinmax->ptMaxTrackSize.y = height;
		
			return TRUE;

			break;
		}
		case WM_SIZE: 
		{

			DoLayout();

			break;
		}
	}

	return FALSE;
}

The GetHeight/GetWidth methods for the CUIPosData class look like this

int CustomToolBar::GetHeight(int sizeType, int orient) {

	int height = 100;

	DebugPrint( _T("GetHeight...
") );

	if (GetICUIFrame()->GetCurPosition() != CUI_FLOATING) {
		DebugPrint( _T("...CUIFrame is docked...
") );

		RECT windowRect;
		RECT clientRect;
		RECT maxClientRect;
		GetWindowRect(pCUIFrame->GetHwnd(), &windowRect);
		GetClientRect(pCUIFrame->GetHwnd(), &clientRect);
		GetClientRect(GetCOREInterface()->GetMAXHWnd(), &maxClientRect);

		height = (maxClientRect.bottom - maxClientRect.top) - 10;
	}

	return height;

}

int CustomToolBar::GetWidth(int sizeType, int orient) {

	int width = 100;

	return width;

}

The over intentation is, obviously, to manage the max/min size of the toolbar while it is floated and docked, as the calculations will change slightly. To this is end, some of the layout needs to be handled by the code into order to keep the RollupWindow sized correctly.

Excuse me while I go outside and shot myself…

The stupid thing was that the scrollbar was showing up properly, when the panel was to long for the avaliable space, it would allow scrolling…

Thank you so much for all that Scrop, very much appricated!!

Shane