Re: Help to modify dialog style using ModifyStyleEx() - C / C++ / MFC Discussion Boards

Re: Help to modify dialog style using ModifyStyleEx()

bosfan19-Feb-07 5:10

19-Feb-07 5:10

Hello WhiteSky,
ähm, the dialog style stay the same, they dont change style from [popup with dialog frame] to child dialog style without frame, title bar etc.

Is there any thing what i forgot to use oder set?

thanks

Re: Help to modify dialog style using ModifyStyleEx()

Hamid_RT19-Feb-07 5:14

Hamid_RT

19-Feb-07 5:14

What happens if you use of ModifyStyle instead ModifyStyleEx

WhiteSky

Re: Help to modify dialog style using ModifyStyleEx()

bosfan19-Feb-07 5:18

bosfan

19-Feb-07 5:18

Nothing, no errors or something, style stay without changes, the same like i create him with the assistance!
Just normal dialog, not included to my parent dialog, but like his own dialog Smile | :)

Re: Help to modify dialog style using ModifyStyleEx()

Hamid_RT19-Feb-07 5:37

Hamid_RT

19-Feb-07 5:37

Whats return value of ModifyStyle?

WhiteSky

Re: Help to modify dialog style using ModifyStyleEx()

bosfan19-Feb-07 21:51

bosfan

19-Feb-07 21:51

Hi,
return 1!

Re: Help to modify dialog style using ModifyStyleEx()

Hamid_RT19-Feb-07 23:10

Hamid_RT

19-Feb-07 23:10

Return 1 this meaning that function is working

WhiteSky

Re: Help to modify dialog style using ModifyStyleEx()

prasad_som19-Feb-07 6:05

prasad_som

19-Feb-07 6:05

break; wrote:
pReportDlg.ModifyStyleEx(WS_EX_OVERLAPPEDWINDOW | WS_EX_DLGMODALFRAME, WS_CHILD);

Modify this to,

pReportDlg.ModifyStyleEx(WS_EX_OVERLAPPEDWINDOW | WS_EX_DLGMODALFRAME, WS_CHILD,SWP_FRAMECHANGED);

Prasad
Notifier using ATL | Operator new[],delete[][^]

Re: Help to modify dialog style using ModifyStyleEx()

bosfan19-Feb-07 21:49

bosfan

19-Feb-07 21:49

Hello Prasad,
thanks for help, the dialog i now showed with new style, without border etc., also like a child
dialog, but they is showed outside of hims parent stay only to clip the dialog to them...

// CFileDialogReport is inherited from CFileDialog
BOOL CFileDialogReport::OnInitDialog()
{
	const UINT iExtraSize = 220;
	CWnd* pParentWnd = GetParent();
	RECT cRect;
	pParentWnd->GetWindowRect(&cRect);
	pParentWnd->SetWindowPos(NULL, 0,0,cRect.right - cRect.left, cRect.bottom - cRect.top + iExtraSize, SWP_NOMOVE);

	CWnd* pComboFileName = pParentWnd->GetDlgItem(cmb1);
	pComboFileName->GetWindowRect(&cRect);
	pParentWnd->ScreenToClient(&cRect);

	// Position for my new controls(for that child dialog)
	cRect.top += 20;
	cRect.bottom += 120;
	cRect.left += 50;
	cRect.right += 160;

	pReportDlg.Create(IDD_REPORT, pParentWnd);
	pReportDlg.ModifyStyle(WS_OVERLAPPEDWINDOW ,WS_CHILD , SWP_FRAMECHANGED);
	pReportDlg.ModifyStyleEx(WS_EX_OVERLAPPEDWINDOW | WS_EX_DLGMODALFRAME, 
		WS_CHILD ,SWP_FRAMECHANGED);

	pReportDlg.ShowWindow(SW_SHOW);
	pReportDlg.SetWindowPos(pComboFileName, 8, cRect.top, cRect.right, cRect.bottom, NULL);
}

ok, i can set settings in the template to child and without border, but i want to try everything
what is posible to do this to runtime, any idea how to do this now?

regards

Re: Help to modify dialog style using ModifyStyleEx()

bosfan19-Feb-07 22:15

bosfan

19-Feb-07 22:15

Hi,
I solve this now, i forgot to set the parent window ,
before i call ShowWindow(SW_SHOW);
i set the parent for my dialog:

pReportDlg.SetParent(pParentWnd);
pReportDlg.ShowWindow(SW_SHOW);
pReportDlg.SetWindowPos(pComboFileName, 8, cRect.top, cRect.right, cRect.bottom, NULL);

regards

Re: Help to modify dialog style using ModifyStyleEx()

prasad_som19-Feb-07 22:31

prasad_som

19-Feb-07 22:31

You can mention parent window, at the time of creation only.

Prasad
Notifier using ATL | Operator new[],delete[][^]

Re: Help to modify dialog style using ModifyStyleEx()

David Crow19-Feb-07 6:14

David Crow

19-Feb-07 6:14

Your code looks correct. I did the same thing sans the call to ModifyStyleEx() and the child dialog was definitely contained within the parent. In the child's dialog template, I set the Style to Child, and the Border to None.

"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15

"Judge not by the eye but by the heart." - Native American Proverb

Re: Help to modify dialog style using ModifyStyleEx()

bosfan19-Feb-07 21:27

bosfan

19-Feb-07 21:27

Hello David,
yes, it works too when i set the same settings like you, in the template, but i need to change
this properties to runtime, before i show the dialog...

regards

Re: Help to modify dialog style using ModifyStyleEx()

David Crow20-Feb-07 2:33

David Crow

20-Feb-07 2:33

break; wrote:
...but i need to change
this properties to runtime, before i show the dialog...

Just out of curiosity, why? Do you not have access to the project's .rc file?

"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15

"Judge not by the eye but by the heart." - Native American Proverb

Re: Help to modify dialog style using ModifyStyleEx()

bosfan20-Feb-07 2:37

bosfan

20-Feb-07 2:37

Hello David,
thanks for help, i have all access to project, that is not the reason, i want to learn how to
do this for the future!
And i know now!

regards
break;

Re: Help to modify dialog style using ModifyStyleEx()

David Crow20-Feb-07 2:52

David Crow

20-Feb-07 2:52

Even if you did something like:

ModifyStyle(WS_POPUPWINDOW | WS_CLIPSIBLINGS | WS_DLGFRAME | DS_MODALFRAME, WS_CHILDWINDOW);
ModifyStyleEx(WS_EX_DLGMODALFRAME | WS_EX_WINDOWEDGE | WS_EX_CONTROLPARENT, 0);

there's no guarantee that it will work.

"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15

"Judge not by the eye but by the heart." - Native American Proverb

Re: Help to modify dialog style using ModifyStyleEx()

bosfan20-Feb-07 4:46

bosfan

20-Feb-07 4:46

ok, i'm now complete confused, but thanks! Confused | :confused:

regards
break;

P.S. i think i do this in the template, set the properties to child , with no border...

Windows SDK Communication Question

Jethro6319-Feb-07 4:53

Jethro63

19-Feb-07 4:53

Greetings:

Does anybody know anything about a limit to the COMn designation that can be successfully opened by the "CreateFile" SDK function?

We have serial ports here that can take mappings greater than 9 (ie: COM10, COM11, etc...). "CreateFile" returns NULL for anything greater than COM9.

Does anybody know a way of getting around this?

Its Windows XP-Pro at the moment, but we have to expect our application to run on other versions as well. I'm using VS 2003 and MFC.

Thank you,
Mark

Re: Windows SDK Communication Question

Roger Stoltz19-Feb-07 5:13

Roger Stoltz

19-Feb-07 5:13

Jethro63 wrote:
Does anybody know anything about a limit to the COMn designation that can be successfully opened by the "CreateFile" SDK function?

This is special case code (or hack) in the implementation of ::CreateFile() that recognizes the filename "COM" followed by one single integer. You can have COM ports from COM1 to COM255, but for port numbers above 9 you have to use "\\\\.\\COMnnn" as filename, e.g. "\\\\.\\COM10".

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

Re: Windows SDK Communication Question

Jethro6319-Feb-07 7:53

Jethro63

19-Feb-07 7:53

Hey! That, like, totally worked!!! Cool | :cool:

Thanks!
Mark

ComBSTR Question

Like2Byte19-Feb-07 3:41

Like2Byte

19-Feb-07 3:41

Hello everyone,

I'm migrating an MFC application to use a new interface (Old DLL to new OCX). the old interface used _TCHAR, bool, etc..., types. The new interface (OCX) uses VARIANTs - *everywhere*.

here's the problem: We're using a structure to maintain a list of active connections (MAX 10).

/*header file - SANDBOX.H*/
typedef struct SModuleInfo
{
#if 1
/*new*/
  CComBSTR bstrModName[256];
  CComBSTR bstrBinFileName[256];
  VARIANT  vbSelected;  /*T/F - if item was selected
  VARIANT  vModHandle;  /*Module Handle*/
  VARIANT  vModID;  /*Module ID*/
  VARIANT  *m_cpzModName;
  VARIANT  *m_pzBinFileName;
#else
/*old*/
  BOOL  bSelected;  /*T/F - if item was selected
  long  lModHandle;  /*Module Handle*/
  long  lModID;  /*Module ID*/
  _TCHAR  m_cpzModName[256];
  _TCHAR  m_pzBinFileName[256];
#endif
} SModuleInfo_t;


class CSandboxApp : public CWinApp
{
public:
  void ModInfoDestroy();
  bool InitModInfo();
  SModuleInfo_t mods[10];
  CSandboxApp();

// Overrides
   ...

// Implementation
   ...
};

Would the following code be the best way to initialize my structure?

/*SOURCE CODE - SANDBOX.CPP*/

bool CSandboxApp::InitModInfo()
{
  for( short i = 0 ; i < 10 ; i++ )
  {
     mods[i].bSelected.vt = VT_BOOL;
     mods[i].lModHandle.vt = VT_I4;
     mods[i].lModID.vt = VT_I4;
     mods[i].lVdsID.vt = VT_I4;
	
     mods[i].m_cpzModName->vt = VT_BSTR;
     mods[i].m_pzBinFileName->vt = VT_BSTR;
     mods[i].m_cpzModName->bstrVal = mods[i].bstrModName->Copy();
     mods[i].m_pzBinFileName->bstrVal = mods[i].bstrBinFileName->Copy();
   }
   return 1;
}

void CSandboxApp::ModInfoDestroy()
{
   int i = 0;
      for( i = 0 ; i < 10 ; i++ )
      {
         mods[i].bSelected.bVal = FALSE;
         mods[i].lModHandle.lVal = 0;
         mods[i].lModID.lVal = 0;
         mods[i].lVdsID.lVal = 0;
         mods[i].m_cpzModName->bstrVal = NULL;
         mods[i].m_pzBinFileName->bstrVal = NULL;
         mods[i].bstrModName->Empty();
         mods[i].bstrBinFileName->Empty();	
      }
}

Between InitModInfo() and DestroyModInfo() I will be populating mods[i].m_pzBinFileName and mods[i].m_cpzModName with textual data the user will be selecting from a listbox. The other values (longs, bools, etc.) will be filled as appropriate later.

My chief concern is properly maintaining the two BSTR arrays. Can I expect this code to align the data correctly so I can pass the variant String data to a function that takes VARIANTs? I think it is ATL and I've not used it before.

Thanks. Unsure | :~

Re: ComBSTR Question

prasad_som19-Feb-07 6:00

prasad_som

19-Feb-07 6:00

Like2Byte wrote:
CComBSTR bstrModName[256]; CComBSTR bstrBinFileName[256];

CComBSTR is a string, so no need to define array.

Like2Byte wrote:
void CSandboxApp::ModInfoDestroy(){ int i = 0; for( i = 0 ; i < 10 ; i++ ) { mods[i].bSelected.bVal = FALSE; mods[i].lModHandle.lVal = 0; mods[i].lModID.lVal = 0; mods[i].lVdsID.lVal = 0; mods[i].m_cpzModName->bstrVal = NULL; mods[i].m_pzBinFileName->bstrVal = NULL; mods[i].bstrModName->Empty(); mods[i].bstrBinFileName->Empty(); }}

Modify this to,

void CSandboxApp::ModInfoDestroy()
{ 
  int i = 0;  
  for( i = 0 ; i < 10 ; i++ )
  {  
    mods[i].bSelected.bVal = FALSE;  
    mods[i].lModHandle.lVal = 0;
    mods[i].lModID.lVal = 0;
   mods[i].lVdsID.lVal = 0; 
   mods[i].m_cpzModName->bstrVal = NULL;
   mods[i].m_pzBinFileName->bstrVal = NULL; 
   SysFreeString(mods[i].m_cpzModName->bstrVal);
   mods[i].m_cpzModName->bstrVal = NULL;

   SysFreeString(mods[i].m_pzBinFileName->bstrVal);
   mods[i].m_pzBinFileName->bstrVal = NULL; 

   mods[i].bstrModName->Empty(); //actually, no need to do this
   mods[i].bstrBinFileName->Empty();
}
}

Prasad
Notifier using ATL | Operator new[],delete[][^]

Re: ComBSTR Question

Like2Byte19-Feb-07 7:21

Like2Byte

19-Feb-07 7:21

Thanks for your both of your posts - excellent information. I figured it out and it's working as intended with your changes. Smile | :)

Re: ComBSTR Question

Stephen Hewitt19-Feb-07 17:40

Stephen Hewitt

19-Feb-07 17:40

You should be probably be using CComVariants instead of raw VARIANTs; both for consistency and to minimise the risk of leaks.

Steve

Re: ComBSTR Question

Like2Byte20-Feb-07 3:51

Like2Byte

20-Feb-07 3:51

Thanks for that. I'm converting an existing project from PC to PocketPC. They recently also converted from using a DLL to an ActiveX control which, of course, all the underlying interfaces must be changed to encompass that, too. Of course, the interface to the OCX uses all VARIANTs.

I'm definitely going to look into using CComVARIANT vs rax VARIANTs. I'm quickly determining that converting their code from chars, int, UINT, etc, is becoming extremely tedious to say the least.

CLISTBOX Owner Drawn ListBox , DrawText does not return correct height.

Killer319-Feb-07 3:35

Killer3

19-Feb-07 3:35

CODE SNIPNET
m_nFormat= DT_NOPREFIX | DT_LEFT | DT_WORDBREAK | DT_EXPANDTABS | DT_EDITCONTROL;
CClientDC dc(pWnd);
UINT nFormat = m_nFormat | DT_CALCRECT;
dc.DrawText(strText, cellRect, nFormat);
int nTotalPadding = (2 * m_nTextPadding);
lpItemStruct->itemWidth = cellRect.Width() + nTotalPadding;
lpItemStruct->itemHeight = cellRect.Height() + nTotalPadding;

The height returned by the CDC::DrawText is not consitent, it behaves different for string of same length example..

1) String full capital letters of length say 160 it returns ==> 81
2) String full capital letters of length say 160 it returns ==> 81
3) String full small letters of length say 160 it returns ==> 100

Please help on this

for thendral

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.