|
If you didn't want to inherit the class and override OnInitDialog, you could probably just declare the dialog, say CFileDialog myDialog and then call myDialog.CalcWindowRect() and pass the resulting RECT or CRect structure into myDialog.Create(). This is how the framework already sets up the window size prior to creation, but if you do some of it yourself, you can change the RECT or CRect structure in between to whatever size you wish.
I've never actually tried this myself in practice, but reading through the documentation, it should work. Check out MSDN.
Danny
The stupidity of others amazes me!
|
|
|
|
|
I guess this method won't work as the HWND of the CFileDialogis not yet created !
(Worst case - try with Hooks ) .
Install a hook before Do Modal ()
Handle the Hook for it and delete the hook after that .
Cause is my effort;
Effect is God's effort
|
|
|
|
|
The method I noted in my post only handles a CRect or RECT structure, so you don't need the window to be created yet, but yes, your method, Raaja, would require the window to be created already.
Danny
The stupidity of others amazes me!
|
|
|
|
|
CFileDialog myDialog
myDialog.CalcWindowRect()
myDIalog.create ....
If this is what you have suggested ,then CalcWindowRect () call is going to fail as the window is not yet created !
Check for the Assert statement in CWnd ::GetExStyle() which is accessed in CalcWindowRect()
Cause is my effort;
Effect is God's effort
|
|
|
|
|
Ah, I see that MFC guru. Since you know MFC so well, explain this explanation of CalcWindowRect,
"Call this member function to compute the required size of the window rectangle based on the desired client-rectangle size. The resulting window rectangle (contained in lpClientRect) can then be passed to the Create member function to create a window whose client area is the desired size.
Called by the framework to size windows prior to creation.
A client rectangle is the smallest rectangle that completely encloses a client area. A window rectangle is the smallest rectangle that completely encloses the window."
I noted in there some phrases like, this is "called by the framework to size windows prior to creation" and how this function is called "to compute the required size of the window" and then you can pass the rectangle "to the Create Member function to create a window".
Do you have some constructive critism, like how he might be able to make this work?
Danny
The stupidity of others amazes me!
|
|
|
|
|
hi
can i overide my GetWindowRect.
|
|
|
|
|
Not sure, but I would guess, no.
Danny
The stupidity of others amazes me!
|
|
|
|
|
DOn't take this personally danny !!!Iam no expert ,iam just sharing what i have tried in Visual Studio ..thats it .
I just refrred to the example in MSDN
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_mfc_cwnd.3a3a.calcwindowrect.asp
If thee link is not working ,refer to Cwnd ::calWindowRect in MSDN and refer to the example given at the end .
calcWindowRect will calculate the window Rectangle ,given the client reactangle size (required size).
In this case ,ur call to calcWindowrect will return the same client rectangle size as m_hWnd of that window is NULL .CHeck CWnd::GetStyle() and CWnd ::calWindowrect() .
In this case CalcWindowRect won't be useful at all .U can directly use Create with required window size .
Cause is my effort;
Effect is God's effort
|
|
|
|
|
I'm trying to write a new class that is a derivative of CObject. The code all looks fine to me, but when I try to compile I get an error saying "constructor not allowed a return type", but I'm not trying to put a return type, or a return statement. Here's the code.
In ClassNameOb.cpp:
#include "stdafx.h"
#include "ClassNameOb.h"
ClassName::ClassName()
{
m_var->VarOne = m_var->VarTwo = m_var->VarThree = m_var->VarFour = m_var->VarFive = -1;
m_otherVar = -1;
}
ClassName::~ClassName(){}
In ClassNameOb.h:
class ClassName : public CObject
{
protected:
struct structType
{
int VarOne;
int VarTwo;
int VarThree;
int VarFour;
int VarFive;
}*m_var;
int m_otherVar;
public:
ClassName();
~ClassName();
}
And then I get an error pointing to the line with the first { bracket of the constructor saying, "constructors not allowed a return type".
Why am I getting this error when I'm not even trying to return anything?
Danny
The stupidity of others amazes me!
|
|
|
|
|
You need:
class ClassName : public CObject
{
...
};
"Take only what you need and leave the land as you found it." - Native American Proverb
|
|
|
|
|
Aaaahhh!!! How annoying! I wish it couldn've told me it was a stupid syntax error!
Danny
The stupidity of others amazes me!
|
|
|
|
|
The OP missed the semicolon at the end of the class declaration?
Regards
Senthil
_____________________________
My Blog | My Articles | WinMacro
|
|
|
|
|
OP? I assume you mean the compiler? In that case, yes, it missed it. How annoying!
Danny
The stupidity of others amazes me!
|
|
|
|
|
|
Oh, thanks. Yes, and I feel dumb for having missed it.
Danny
The stupidity of others amazes me!
|
|
|
|
|
Hi everyone,
I hope that someone can help me solve my problem...
Well, I would like to click-and-drag the child window and move it within its parent!
From child's window procedure, catching WM_MOUSEMOVE, I tried to call SendMesage(hWndParent,WM_MOUSEMOVE, NULL, NULL) in order to make it move.
Well it does not work! I tried Handling WM_MOUSEMOVE from the parent only but the child window would move with the mouse only whan the mouse leaves the child and 'touches' the parent window!
Is there anyone who can, in simple C++, help me to get over this issue?!
Thanks!
|
|
|
|
|
... SS_NOTIFY ....
see one thread below 
SkyWalker
|
|
|
|
|
Frstly thanks to SkyWalker for the agility.
Unfortunately it will not work with the SS_NOTIFY because I referred to the windows which I created from the scratch, i.e. I did not use the MFC.
I have two windows involved, one is the main app’s window and the other one is created with the extended style, which identifies it as a child window (WS_CHILD).
I managed to move the child window by calling SetWindowPos while catching WM_MOUSEMOVE events from the parent window!
The thing is that, while with the mouse over the child window, I do not know how to catch WM_MOUSEMOVE of the parent. Naturally while over the child window all messages are going to that window!
I hope that the picture of my problem is slightly clearer.
|
|
|
|
|
Then you have to treat the event in the PreTranslateMassage() of the app class.
SkyWalker
|
|
|
|
|
Hi -
I did this.
The best way to do it is to have the child window capture the mouse input and move itself.
MFC makes it easy to do. You can do it with a WIN32 API windProc - but it's more straight foward in MFC.
void myStatic::OnLButtonDown(UINT nFlags, CPoint point)
{
// TODO: Add your message handler code here and/or call default
::SetCapture(*this) ;
::OutputDebugString("myStatic::OnLButtonDown\n") ;
mdown = 1 ;
m_x = point.x ;
m_y = point.y ;
// CStatic::OnLButtonDown(nFlags, point);
}
void myStatic::OnMouseMove(UINT nFlags, CPoint point)
{
// TODO: Add your message handler code here and/or call default
if( mdown )
{
::OutputDebugString("myStatic::OnMouseMove\n") ;
RECT lrect ;
::GetWindowRect(*this,&lrect) ;
point.x -= m_x;// modify the pt with the saved point
point.y -= m_y;
POINT lpt ;
lpt.x = lrect.left ;
lpt.y = lrect.top ;
::ScreenToClient(*this->GetParent(),&lpt) ;
lpt.x += point.x ;
lpt.y += point.y ;
::SetWindowPos( *this, 0, lpt.x, lpt.y, 0, 0, SWP_NOZORDER | SWP_NOSIZE );
}
// CStatic::OnMouseMove(nFlags, point);
}
void myStatic::OnLButtonUp(UINT nFlags, CPoint point)
{
// TODO: Add your message handler code here and/or call default
if( mdown )
{
mdown = 0 ;
::OutputDebugString("myStatic::OnLButtonUp\n") ;
::ReleaseCapture() ;
}
// CStatic::OnLButtonUp(nFlags, point);
}
- Joe
-- modified at 16:28 Thursday 20th October, 2005
|
|
|
|
|
Hi,
I am developing and application that requires images manipulation.
All the interface is developped using Dialogs.
The controls were images are displayed are derived from CStatic control.
The problem is that I cannot catch the OnLButtonDown event straight in the CStatic control. I must catch the OnLButtonDown event in the dialog and then call the OnLButtonDown member function for each of my controls.
This doesn't happend with a CButton derived class.
I will apreciate any help.
Thank you.
Cédric
-- modified at 10:05 Thursday 20th October, 2005
|
|
|
|
|
And why don't you make it a custom control instead ?
I never subclassed a CStatic control so I cannot answer your question but for me it looks like a custom control instead.
|
|
|
|
|
The CStatic control must have the SS_NOTIFY> style.
Check "Notify" within the "Style" properties tab.
SkyWalker
-- modified at 10:27 Thursday 20th October, 2005
|
|
|
|
|
I already tried this but it didn't work!
I also tried to override the OnCreate member function but it is not called!
Thank's.
|
|
|
|
|
This cannot be 
Make a break point in the mouse button handler. Tell me if it goes there.
If not, I send you tomorrow a piece of code.
SkyWalker
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
