C / C++ / MFC

prasad_som18-May-07 0:05

18-May-07 0:05

Sethuraman.K wrote:
i tried with SetWindowPos(),

Can you show your attempted code?

Prasad
MS MVP - VC++

Sethuraman.K18-May-07 0:20

Sethuraman.K

18-May-07 0:20

//This is my code...
// Mypropertysheet.cpp : implementation file
//

#include "stdafx.h"
#include "freshpdk.h"
#include "Mypropertysheet.h"

#ifdef _DEBUG
#define new DEBUG_NEW
#undef THIS_FILE
static char THIS_FILE[] = __FILE__;
#endif

extern int presentlyreading;
/////////////////////////////////////////////////////////////////////////////
// CMypropertysheet

IMPLEMENT_DYNAMIC(CMypropertysheet, CPropertySheet)

CMypropertysheet::CMypropertysheet(UINT nIDCaption, CWnd* pParentWnd, UINT iSelectPage)
:CPropertySheet(nIDCaption, pParentWnd, iSelectPage)
{

}

CMypropertysheet::CMypropertysheet(LPCTSTR pszCaption, CWnd* pParentWnd, UINT iSelectPage)
:CPropertySheet(pszCaption, pParentWnd, iSelectPage)
{
//AddPage(&fstpg);//Commected By Abhi on 170507
AddPage(&secpg);

}

CMypropertysheet::~CMypropertysheet()
{
}

BEGIN_MESSAGE_MAP(CMypropertysheet, CPropertySheet)
//{{AFX_MSG_MAP(CMypropertysheet)
ON_WM_CLOSE()
ON_WM_CREATE()
ON_WM_KEYDOWN()
ON_WM_KEYUP()
ON_WM_VKEYTOITEM()
ON_COMMAND(IDOK, OnOK)
ON_WM_ENABLE()
//}}AFX_MSG_MAP
END_MESSAGE_MAP()

/////////////////////////////////////////////////////////////////////////////
// CMypropertysheet message handlers

void CMypropertysheet::OnClose()
{
// TODO: Add your message handler code here and/or call default
if(presentlyreading != 0)
return;

EndDialog(IDOK);
CPropertySheet::OnClose();
}

int CMypropertysheet::OnCreate(LPCREATESTRUCT lpCreateStruct)
{
if (CPropertySheet::OnCreate(lpCreateStruct) == -1)
return -1;

// TODO: Add your specialized creation code here
CWnd *pTemp;

pTemp = GetDlgItem(ID_APPLY_NOW);
if(pTemp != NULL)
pTemp->DestroyWindow();
if(pTemp != NULL)
pTemp->DestroyWindow();
pTemp = GetDlgItem(IDCANCEL);
if(pTemp != NULL)
pTemp->SetWindowText("Close");
return TRUE;

return 0;
}

void CMypropertysheet::OnCancel()
{
// MessageBox("hello");
// CDialog::OnCancel();

}

BOOL CMypropertysheet::OnInitDialog()
{
BOOL bResult = CPropertySheet::OnInitDialog();

CWnd *pTemp;
pTemp = GetDlgItem(ID_APPLY_NOW);
if(pTemp != NULL)
pTemp->DestroyWindow();
/////////// sujith 07-02-07 (delete) ////////////

//pTemp = GetDlgItem(IDOK);
//if(pTemp != NULL)
// pTemp->DestroyWindow();

/////////// sujith 07-02-07 ////////////
pTemp = GetDlgItem(IDCANCEL);
if(pTemp != NULL)
pTemp->SetWindowText("Close");

//////****/Here am changing the position of Propertysheet window

int i= ((CWnd*)this)->SetWindowPos((CWnd*)this ,1038,73,0,0, SWP_NOMOVE | SWP_NOSIZE | SWP_NOZORDER | SWP_FRAMECHANGED);

//////****
return TRUE;
}

void CMypropertysheet::OnOK()
{
// TODO: Add extra validation here

//CDialog::OnOK();
//MessageBox("Hello");
}

void CMypropertysheet::OnEnable(BOOL bEnable)
{
CPropertySheet::OnEnable(bEnable);

// TODO: Add your message handler code here

}

Sethuraman.K

prasad_som18-May-07 0:47

18-May-07 0:47

I should have mention "relevent code".

Sethuraman.K wrote:
int i= ((CWnd*)this)->SetWindowPos((CWnd*)this ,1038,73,0,0, SWP_NOMOVE | SWP_NOSIZE | SWP_NOZORDER | SWP_FRAMECHANGED);

You are using same window handle as hWndInsertAfter . Refer documentation for correct parameter.
And you are giving 0 and 0 as width and height of window. (Again, refer documentation)

Prasad
MS MVP - VC++

Rajesh R Subramanian18-May-07 0:53

Rajesh R Subramanian

18-May-07 0:53

prasad_som wrote:
I should have mention "relevent code".

Nobody can give you wiser advice than yourself. - Cicero

James R. Twine18-May-07 2:10

18-May-07 2:10

prasad_som wrote:
You are using same window handle as hWndInsertAfter . Refer documentation for correct parameter.
And you are giving 0 and 0 as width and height of window. (Again, refer documentation)

Having a zero width and height is fine - that is what the SWP_NOSIZE flag allows for (they are ignored), and since he also specified the SWP_NOZORDER flag, the first HWND parameter is ignored as well (I would say to "refer to the documentation", but that would be just plain scarstatic my telling that to an MVP...). His problem is with one of the other flags he sets, can you guess which one...?

Peace!

-=- James
Please rate this message - let me know if I helped or not!<HR>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles

prasad_som18-May-07 2:15

Re: How to change position of propertysheet? [modified]

18-May-07 2:15

Yup, by seeing first two flags, I overlooked last parameter. My bad.

James R. Twine wrote:
His problem is with one of the other flags he sets, can you guess which one...?

You have already answered that.

James R. Twine wrote:
Please rate this message - let me know if I helped or not!

Definitely , this time.

Prasad
MS MVP - VC++

James R. Twine18-May-07 2:05

CDateTimeCtrl::GetTime() what it return? UTC or something else?

18-May-07 2:05

Sethuraman.K wrote:
int i= ((CWnd*)this)->SetWindowPos((CWnd*)this ,1038,73,0,0, SWP_NOMOVE | SWP_NOSIZE | SWP_NOZORDER | SWP_FRAMECHANGED);

You are specifying the SWP_NOMOVE flag, which tells the function not to move the window, which is exactly what you are trying to do! You might want to ~~add the SWP_NOZORDER flag and change the first parameter to NULL as well~~ (sorry - did not see you already had that flag set).

Peace!

-- modified at 8:10 Friday 18th May, 2007

brakeshbaldhab17-May-07 23:59

brakeshbaldhab

17-May-07 23:59

Hi,
is anybody having idea?

thanks
rakesh

Re: CDateTimeCtrl::GetTime() what it return? UTC or something else?

led mike18-May-07 4:20

led mike

18-May-07 4:20

brakeshbaldhab wrote:
what it return? UTC or something else?

It's a user input control. It returns whatever the user set the value to.

led mike

int CString::Find()

Immunity1817-May-07 23:28

Immunity18

17-May-07 23:28

goodmorning i am trying to type a fuction that it return me how many times a str exist in a line .Christian told me to work with CString Find but i have some problems here :/

Problem is, i think ,my while loop is wrong and my program becomes (Not Responding)

int CInfoRecoverDlg::Compare( CString line , CString str2)
{
int nCount = 0;
for (int i = 0 ; i < line.GetLength() ; i++)
{
while ( line.Find(str2,i+1)!= -1 )
{
nCount = nCount +1;
}
}
return nCount ;
}

void CInfoRecoverDlg::OnButton1()
{
CString str = "yes";
CString line = "yes i said yes , yes ";
int nCount;

nCount = Compare( line , str);
AfxMessageBox(""+nCount);
}

Re: int CString::Find()

prasad_som17-May-07 23:58

17-May-07 23:58

Have you tried to debug the code ?

Immunity18 wrote:
while ( line.Find(str2,i+1)!= -1 )

I guess, you could modify this to,

while ( line.Find(str2,i)!= -1 )

Again, I'm not sure about aim of the function.

Prasad
MS MVP - VC++

Re: int CString::Find()

Hamid_RT18-May-07 0:33

Hamid_RT

18-May-07 0:33

Try to this code

int CMyDialog::Compare( CString line , CString str2)
{
int nCount = 0;
int index=0;
for (int i = 0 ; i < line.GetLength() ; i++)
{
 index=line.Find(str2,index);
	if( index!= -1 )
	{
	nCount++;
	index++;
        }
	else
         return nCount;
}
return nCount ;
}

WhiteSky

ON_NOTIFY_RANGE problem!

TPN17-May-07 22:52

TPN

17-May-07 22:52

Hi all,

I design a form with about 50 combo boxes and I want to handle the notification message CBN_SELCHANGE of those combo boxes in a same routine, so I use the macro ON_NOTIFY_RANGE(CBN_SELCHANGE, IDC_COMBO1, IDC_COMBO50, MyMsgHandler).

But it seems that nothing happens. Am I wrong?

Pls help me to solve this.

Thanks in advance.

kanduripavan17-May-07 23:10

kanduripavan

17-May-07 23:10

ON_CONTROL_RANGE try this. I hope it will solve the problem

Roger Stoltz17-May-07 23:11

Roger Stoltz

17-May-07 23:11

What happens if you use ON_NOTIFY for only one of the controls?

"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown

TPN18-May-07 0:28

TPN

18-May-07 0:28

Thanks you for your help!

I don't want to use ON_NOTIFY because there are many controls and this will cause many ON_NOTIFY macro.

I try with ON_CONTROL_RANGE and it work fine. But I am still not clear the difference between ON_NOTIFY_RANGE and ON_CONTROL_RANGE...

Once again, thank you.

Roger Stoltz18-May-07 0:52

Roger Stoltz

18-May-07 0:52

TPN wrote:
I don't want to use ON_NOTIFY because there are many controls and this will cause many ON_NOTIFY macro.

I know, my point was that if something doesn't work you should revert to the easiest way to test that you've got the concept down correctly.
You thought there was something wrong with your use of the ON_NOTIFY_RANGE mechanism, but if you would have tried with the simpler ON_NOTIFY you would have found that it won't get called since the control sends a WM_COMMAND notification and not a WM_NOTIFY notification.

TPN wrote:
I try with ON_CONTROL_RANGE and it work fine. But I am still not clear the difference between ON_NOTIFY_RANGE and ON_CONTROL_RANGE...

The difference is that it handles two separate windows messages: WM_COMMAND and WM_NOTIFY.
For actions that send WM_COMMAND notifications you have to use ON_CONROL_RANGE.
WM_NOTIFY was introduced with Win32 API to send notification messages that requires more information and the message handler receives a pointer to a NMHDR struct with control specific data. WM_NOTIFY didn't exist in Win3.x API.

"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown

James R. Twine18-May-07 2:20

18-May-07 2:20

   To further clarify Roger's point - the "older" Windows controls, meaning the ones available in 16-bit Windows like Button, Edit, Static, ComboBox, ListBox, etc. all use WM_COMMAND for their notification messages.

   The "new" 32-bit common controls, such as the ListView, TreeView, Progress Bar, Slider, Rich Edit, etc. all use WM_NOTIFY for their notification messages.

   If using MFC, the easiest way to tell the difference is that the older control's wrapper classes do not end with Ctrl and the newer ones do. For example, the MFC class for the (older) Button is CButton and the class for an (older) Edit is CEdit, while the class for a (newer) Rich Edit is CRichEditCtrl and the class for the (newer) TreeView is CTreeCtrl. So if your control's wrapper class ends with Ctrl, use the WM_NOTIFY-based handlers.

   Peace!

Roger Stoltz18-May-07 2:26

Roger Stoltz

18-May-07 2:26

James R. Twine wrote:
So if your control's wrapper class ends with Ctrl, use the WM_NOTIFY-based handlers.

Good point James.
Hi 5 for that.

"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown

James R. Twine18-May-07 2:55