C / C++ / MFC

3-Mar-06 5:49

Greetings:

I am trying to experiment with making an application with flexible windows that show different things and can be opened and closed at will and in no particular order. I do not want to involve the document / view architecture. There's no need for an underlying document; my program receives input data from external ports of various kinds.

For openers, I tried to create an SDI application with no Doc/View but whose client is a CFormView, not a CChildView. Why is this hard?

Should I REPLACE the CChildView client window with a CFormView? Or, should I create a CFormView and then derive the CChildView from the new CFormView (instead of from CWnd as the App Lizard would have it)?

I have a metric tonne of books on the subject of programming in MFC and I have yet to encounter one, just ONE, that clearly explains and lays out the architecture of SDI, MDI, Doc/View, non-Doc/View, splitters, CMainFrame, Views, etc, etc. I would like to understand these things in such a way that I can finally feel that I have some measure of control and choice as to how my application windows behave and can write a program that breaks from the straight jacket that is the MFC App-Lizard. Has anyone out there encountered a book or resource that does this? I mean, explain it to me like I'm 4 years old! Insult my intelligence! Just make it clear!

There, I feel better. Thanks in advance to anyone who responds.
Cheers,
Mark

David Crow3-Mar-06 6:07

3-Mar-06 6:07

Jethro63 wrote:
my program receives input data from external ports of various kinds.

Why would this preclude the use of Doc/View?

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

Jethro633-Mar-06 7:15

3-Mar-06 7:15

Hi David:
It doesn't necessarily, but MUST I always use Doc/View? I find that I create my application using doc/view and the "doc" component of it goes unused. Then I find it just gets in my way when I want to do something like replace one view with another, or add a new view.

Its the principle of the thing really. Can't you just put up a main frame and then throw up whatever child windows you want, when you want without having to deal with all this doc/view baggage?

Thank for your response.
Mark

David Crow3-Mar-06 7:20

3-Mar-06 7:20

Jethro63 wrote:
Then I find it just gets in my way when I want to do something like replace one view with another, or add a new view.

In this situation, what is the view displaying?

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

Jethro633-Mar-06 8:36

3-Mar-06 8:36

Could be anything. Let's say I'm connected to a specialized piece of equipment and it is sending messages asynchronously through the USB port to my application. I want to offer my user 3 or 4 different ways of viewing these incoming messages: raw hex data, a scrolling list view, a graphical histogram plot, a statistcial listing. The user should be free to open, close and arrange any number and combination of these windows. At the same time, maybe I would like a "Console Window" where the user enters synchronous commands and the response from the device is displayed in the same window. Still another window (like a form view) that contains push button controls, sliders, edit boxes that handle other types of commands to the device or to the application to control its behavior. I might also want the option to turn on a diagnostics window where special program messages get directed to.

I see that all of these windows involve data and I suppose that you could make it fit into the doc/view paradigm if you had a crow-bar and a sledge hammer, but I don't see how it helps me to use a doc/view based approach. I don't use serialization, I am used to saving data in files using old-fashioned read and write commands to an open file pointer. In the end, I always find that the doc/view needs a doc/view template and then I can never figure out how to open up more than one view for the same document data or create an alternate doc/view pair and it all gets way too complicated way too fast.

That's my story. Any suggestions would be welcomed.
Mark

Office Lineman3-Mar-06 14:07

Office Lineman

3-Mar-06 14:07

This is a method for creating an MFC CFormView application with no document--and the form window is not to be resized. If you don't mind the window being resized, don't do the frame/maximize box step. Sorry about the formatting, but it's from a Word doc, and I'm too lazy to clean up Word 2K's crummy HTML output Laugh | :laugh:

1. Create a new MFC AppWizard (exe) project.
	a. MFC AppWizard - Step 1 of 6
		i. Select "Single document" for the application type.
		ii. Uncheck "Document/View architecture support?".
	b. MFC AppWizard - Step 2 of 6 - no changes
	c. MFC AppWizard - Step 3 of 6 - no changes
	d. MFC AppWizard - Step 4 of 6
		i. Set the number of files on the recent file list to 0. (optional - no MRU anyway)
		ii. Press "Advanced..."
			1. Uncheck "Thick frame" and "Maximize box", leaving only "Minimize box" and "System menu" checked. (optional)
	e. MFC AppWizard - Step 5 of 6 - no changes
	f. MFC AppWizard - Step 6 of 6 - no changes
2. Create a CFormView for the application.
	a. Select Insert->New Form....
	b. Enter a form class name in the "Name" field, e.g. "CMyFormView".
	c. Press OK.
	d. Design the form as desired.
3. Adjust command handlers in new CFormView-based class.
	a. Using the ClassWizard, insert a handler for OnInitialUpdate.
	b. Add the following code into the OnInitialUpdate handler where indicated:
		GetParentFrame()->RecalcLayout();
		ResizeParentToFit();
4. Remove ChildView.h and ChildView.cpp from the project.  Delete the files.
5. Remove CChildView references from MainFrm.h
	a. Remove the "#include ChildView.h" directive.
	b. Remove the "CChildView m_wndView" member.
6. Adjust command handlers in MainFrm.cpp
	a. Remove the OnCmdMsg handler and delete its code.
	b. Remove the OnSetFocus handler and delete its code.
	c. Edit the OnCreate handler
		i. Remove the view creation code:
			// create a view to occupy the client area of the frame
			if (!m_wndView.Create(NULL, NULL, AFX_WS_DEFAULT_VIEW, CRect(0, 0, 0, 0), this, AFX_IDW_PANE_FIRST, NULL))
			{
				TRACE0("Failed to create view window\n");
				return -1;
			}
		ii. Remove the docking capability for the toolbar by commenting out or deleting the indicated lines. (optional)
7. Adjust application creation in <appname>.cpp
	a. Include the view class header, e.g. "#include "MyFormView.h".
	b. Edit the InitInstance function
		i. Replace the frame loading code:
				pFrame->LoadFrame(IDR_MAINFRAME, WS_OVERLAPPEDWINDOW | FWS_ADDTOTITLE, NULL, NULL);
			with the following code:
				CCreateContext oCreateContext;
				oCreateContext.m_pNewViewClass = RUNTIME_CLASS(CMyFormView);
				oCreateContext.m_pCurrentFrame = pFrame;
				pFrame->LoadFrame(IDR_MAINFRAME, WS_OVERLAPPEDWINDOW, NULL, &oCreateContext);
				pFrame->InitialUpdateFrame(NULL, TRUE);

Everything should compile okay.  N.B. when you run the application in debug mode, you will receive "Warning: Creating a pane with no CDocument." in the debug output.  It's a nice warning, but that WAS kind of the whole point, right?

--
I've killed again, haven't I?

Jethro6328-Dec-06 5:05

28-Dec-06 5:05

Hi "Office Lineman":

I lost track of this thread and did not discover your response until today. Thank you very much for your instructions. I normally respond right away when somebody takes the time to answer a question that I post, so I feel a bit embarrased that I missed this, especially since it is clear that you spent some time on this response.

I followed your instructions and they worked exactly as I had hoped. I was a bit puzzled by the final segment where the "CCreateContext" structure is brought in. After reading up on this structure, I see that most of its fields can be regarded as optional. This has lead me to an example on the MSDN DVD called "VIEWEX" which expands more on the problem that I originally pointed out: It is not obvious or straight forward how to create an application that consists simply of a main frame which can house a variety of different views, opened or closed in no particular order. I have been searching for a general understanding of all of this and it is difficult to get the answers I am looking for.

Anyway, thanks again for your instructions.
Mark

permutations19-Apr-10 13:07

permutations

19-Apr-10 13:07

This is absolutely awesome. Thank you so much for posting this! I've been going crazy trying to figure it out.

Re: What is IsolatedStorage

Rez_Spain6-May-10 23:07

Rez_Spain

6-May-10 23:07

Man, Maybe this topic is old as f*** but im just so grateful.
THANKS Office Lineman!

What is IsolatedStorage

Chintoo7233-Mar-06 5:47

Chintoo723

3-Mar-06 5:47

Does anyone know what is IsolatedStorage? I have this directory that I am unable to delete:
C:\Documents and Settings\<user>\Local Settings\Application Data\IsolatedStorage\1cz2yllv.kcp\v44qcfut.b25
\Url.b01cm1a5pqdgmvysoo2gnkbuohme03bk\Url.b01cm1a5pqdgmvysoo2gnkbuohme03bk\Files

Is there any way to remove this IsolatedStorage folder?

thanks!

Chintoo7233-Mar-06 5:58

Chintoo723

3-Mar-06 5:58

OK, this link http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemioisolatedstorageisolatedstoragefileclasstopic.asp[^] provides an example to remove the Isolted Storage files. I can use the C++ code, but it seems to require .Net framework. I have only Visual Studio 6 with platform SDK. I dont want to install .NET, does IsolatedStorage have an API outside .NET?

thanks!

copying an array of bytes to another array

chaitanya223-Mar-06 5:24

3-Mar-06 5:24

copying an array of bytes to another byte array of same size

-- modified at 11:24 Friday 3rd March, 2006

RChin3-Mar-06 5:30

RChin

3-Mar-06 5:30

...and your question is?

If I guess correctly, something like this would do nicely:

<br />
char pArray1[] = {1,2,3,4,5};  // Source array<br />
char pArray2[5];               // Destination array<br />
<br />
memcpy(pArray1, pArray2, 5);<br />

I Dream of Absolute Zero

David Crow3-Mar-06 5:49

3-Mar-06 5:49

RChin wrote:
memcpy(pArray1, pArray2, 5);

Or:

memcpy(pArray2, pArray1, 5 * sizeof(char));

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

chaitanya223-Mar-06 5:55

3-Mar-06 5:55

ya thank you, it didnt work for me, i would like to assign source array to new array.

eg:
assinging BYTE sourcearray[212] to BYTE destarray[1024],,,,

as am pieces of bytes in source array, like 108 bytes for the first time and again 104 bytes for the second time.

-- modified at 11:57 Friday 3rd March, 2006

David Crow3-Mar-06 6:28

3-Mar-06 6:28

chaitanya22 wrote:
i would like to assign source array to new array.

eg:
assinging BYTE sourcearray[212] to BYTE destarray[1024],,,,

Use:

memcpy(destarray, sourcearray, 108 * sizeof(BYTE));

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

chaitanya223-Mar-06 5:51

3-Mar-06 5:51

Its an array of Bytes, like i owuld like like to assign source array of bytes to destination array, as am getting chunks of bytes in the source array, so that i would be having all bytes without break.

David Crow3-Mar-06 6:05

3-Mar-06 6:05

memcpy() is the function to use. What about it is not working?

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

chaitanya223-Mar-06 6:09

Re: PARAFORMAT2 Structure

3-Mar-06 6:09

yes, its working, but again am getting the breaks in the data as like in source array. I would like to have continous stream of data.

PARAFORMAT2 Structure

Richard_483-Mar-06 5:10

Richard_48

3-Mar-06 5:10

Hello all,

Here is my code:

void CMSMCitationView::OnMsmformattingJustifytext()
{

//Call the PARAFORMAT2 Structure to mod the paragraph
// format
PARAFORMAT2 pf;

// Modify the paragraph format so that the text
//is justified.
pf.cbSize = sizeof(PARAFORMAT2);
pf.dwMask = PFM_ALIGNMENT;
pf.wAlignment = PFA_JUSTIFY;
CRichEditView::SetParaFormat(pf);

// Verify the settings.
#ifdef _DEBUG
CRichEditView::GetParaFormatSelection();
ASSERT(pf.dwMask&PFM_ALIGNMENT);
ASSERT(pf.wAlignment == PFA_JUSTIFY);
#endif

}

Here is more info about this:
Code compiles and links. When Menu Item (Justify Text) is selected, nothing happens. When other values are used in place of PFA_JUSTIFY, such as PFA_CENTER, center text is the result. Documentation says that if Rich Edit 3.0 is not installed, value PFA_JUSTIFY will align with the left margin. This is my result with PFA_JUSTIFY. I am running Win XP Pro with all the updates installed. Should have at least Rich Edit 3.0.dll already installed. Question is why won't PFA_JUSTIFY do it's thing? How do I determine if at least the RichEdit 3.0.dll is installed?

Thanks for your inputs,

Sveige Smile | :)

RRL

Jeremy Falcon3-Mar-06 7:26

Jeremy Falcon

3-Mar-06 7:26

sveige wrote:
How do I determine if at least the RichEdit 3.0.dll is installed?

From lebans.com...

Version DLL
1.0     Riched32.dll
2.0     Riched20.dll
3.0     Riched20.dll
4.1     Msftedit.dll

Windows XP SP1  Includes Rich Edit 4.1, Rich Edit 3.0, and a Rich Edit 1.0 emulator.
Windows XP 	Includes Rich Edit 3.0 with a Rich Edit 1.0 emulator.
Windows Me 	Includes Rich Edit 1.0 and 3.0.
Windows 2000 	Includes Rich Edit 3.0 with a Rich Edit 1.0 emulator.
Windows NT 4.0 	Includes Rich Edit 1.0 and 2.0.
Windows 98 	Includes Rich Edit 1.0 and 2.0.
Windows 95 	Includes only Rich Edit 1.0. However, Riched20.dll is compatible with Windows 95 and may be installed by an application that requires it.

Jeremy Falcon

Stack overflows

Waldermort3-Mar-06 4:14

Waldermort

3-Mar-06 4:14

What are the common causes for stack overflows? I have a very simple loop

for (long i=0; i<rec.size(); i++) {
    add_list_item(i, 0,0,rec[i].text);
}

which calls the function

void cDisplay::add_list_item(long iLin, long iCol, int iSub,char* text)
{
	LVITEM lvi;
	RECT rect;

	GetClientRect(hList, &rect);
	memset(&lvi, 0, sizeof(lvi));

	lvi.mask = LVIF_TEXT;
	lvi.state = 0;
	lvi.stateMask = 0;
	lvi.pszText = text;
	lvi.iItem = iLin;
	lvi.iSubItem = iCol;
    
	switch(iSub)
	{
		case 0:
			SendMessage((HWND) hList,(UINT) LVM_INSERTITEM, (WPARAM) 0, (LPARAM) &lvi);
			break;
		case 1:
			SendMessage((HWND) hList,(UINT) LVM_SETITEM, (WPARAM) 0, (LPARAM) &lvi);
			break;
	}
	ListView_SetColumnWidth(hList,iCol,LVSCW_AUTOSIZE_USEHEADER);
	InvalidateRect(hList, &rect, TRUE) ;
}

All this does is populate a list-view with some 150 lines. Problem is, on the 32nd call to SendMessage the program crashes due to a sack overflow. I can't see where this is being caused or for what reasons.

But if I call

add_list_item(0, 0,0,rec[i].text);<pre> from the loop, ie put the item on the first line, it runs without a problem.  But this is not what I want.

Re: Stack overflows

David Crow3-Mar-06 4:33