C / C++ / MFC

3-Mar-06 10:20

It's clear how to set right and left margins in an instance of CEditView. Is there a way to effectively set a top margin?

--hsm

Richard_483-Mar-06 11:29

Richard_48

3-Mar-06 11:29

In the PARAFORMAT2 Structure there is a member called dySpaceBefore. You will need to build a function to call this member using the dwMask member. The value must always be > than or = 0. The Size of the spacing is in twips. You may be able to set up something similar in the PARAFORMAT structure if you are using later versions of Visual C++. Go to MDN.COM and do a search for PARAFORMAT OR PARAFORMAT2. I think there is an example there somewhere..??

regards,

RRL

Richard_483-Mar-06 11:35

Richard_48

3-Mar-06 11:35

sorry. I ment msdn.com not mdn.com also, if you ar running v.s. 6.0 PARAFORMAT may be the structure to use...

RRL

Hugh S. Myers3-Mar-06 12:42

3-Mar-06 12:42

Much thanks, I'll take a look.

--hsm

Hugh S. Myers3-Mar-06 13:06

3-Mar-06 13:06

I just looked. Two problems occur to me; first, this is for a CRichEditView, not a CEditView. The other problem is that this would allow control of the space above a paragraph--- not the space above the page. Perhaps I'm missing something?

--hsm

Hugh S. Myers5-Mar-06 6:55

MFC & inner class question...

5-Mar-06 6:55

For those with the same problem, a tentative answer is to set the rectangle in the CEdit control:

void CPGNTextView::SetTopMargin()<br />
{<br />
	CEdit &theEdit = GetEditCtrl();<br />
	CRect r;<br />
	theEdit.GetRect(&r);<br />
	TRACE("t=%d l=%d b=%d r=%d\n",r.top,r.left,r.bottom,r.right);<br />
	r.top = TOP_MARGIN;<br />
	theEdit.SetRect(&r);<br />
	TRACE("t=%d l=%d b=%d r=%d\n",r.top,r.left,r.bottom,r.right);<br />
}

And then to do it again in WM_SIZE and WM_SETFONT handlers. Seems like overkill, but the CEdit control loses this information every chance it gets so you just have to help it along so to speak.

--hsm

Alberto_Canabal3-Mar-06 7:30

Alberto_Canabal

3-Mar-06 7:30

Is there a way I can do something like this:

<br />
class MyClass<br />
{<br />
...<br />
private:<br />
class MyInnerClass: public CWnd<br />
{<br />
...<br />
//{{AFX_MSG(MyInnerClass)<br />
afx_msg int OnCreate(LPCREATESTRUCT lpCreateStruct);<br />
afx_msg void OnShowWindow(BOOL bShow, UINT nStatus);<br />
//}}AFX_MSG<br />
...<br />
};<br />
...<br />
};<br />

??
I've been trying for a while, and the code doesn't even compile (if I declare the class outside the first one, everything works OK, but I want the class to be inner). I suspect it's a matter of names for the message maps, but can't figure out the right one...
Thanks!
Alberto.

Blake Miller3-Mar-06 7:59

Blake Miller

3-Mar-06 7:59

Why do you feel the inner class is necessary?

I would probably have done this instead:

class MyInnerClass: public CWnd<br />
{<br />
...<br />
//{{AFX_MSG(MyInnerClass)<br />
afx_msg int OnCreate(LPCREATESTRUCT lpCreateStruct);<br />
afx_msg void OnShowWindow(BOOL bShow, UINT nStatus);<br />
//}}AFX_MSG<br />
...<br />
};<br />
<br />
class MyClass<br />
{<br />
...<br />
private:<br />
MyInnerClass* m_InnerClass;<br />
...<br />
};

And avoid the entire problem.

People that start writing code immediately are programmers (or hackers), people that ask questions first are Software Engineers - Graham Shanks

Alberto_Canabal6-Mar-06 0:06

Alberto_Canabal

6-Mar-06 0:06

It's what I've done, but I feel the inner class is necessary for preventing unnecesary access to it.
I just wanted it to be sort of "private", and it seemed to me it was the best way (ok, i admit it...I'm a java programmer).

Thanks for the answer (sorry for my english)...
Alberto

Blake Miller6-Mar-06 5:36

Blake Miller

6-Mar-06 5:36

If you really want to hide the internals of your class, then
make a forward declaration like this:

class MyInnerClass;

then use it privately in some other class:

class SomeOtherClass
{
...
private:
MyInnerClass* m_MyInnerClass;
...
};

and then declare the MyInnerClass in the source file along with its implementation as the same source file as SomeOtherClass and only SomeOtherClass will ever be able to actually 'use' the MyInnerClass.

Or, just declaring the pointer to it like the original example, that pretty much prevents ANYTHING else from using the MyInnerClass anyhow.

People that start writing code immediately are programmers (or hackers), people that ask questions first are Software Engineers - Graham Shanks

C^hris L^osinger3-Mar-06 8:21

C^hris L^osinger

3-Mar-06 8:21

have you tried:

//{{AFX_MSG(MyClass::MyInnerClass)

?

Cleek | Image Toolkits | Thumbnail maker

Alberto_Canabal6-Mar-06 0:02

Alberto_Canabal

6-Mar-06 0:02

I've tried it, and didn't work (maybe I missed something elsewhere).
Thanks.

[Message Deleted]

johni__boy3-Mar-06 6:33

johni__boy

3-Mar-06 6:33

[Message Deleted]

David Crow3-Mar-06 6:38

David Crow

3-Mar-06 6:38

johni__boy wrote:
Can anybody help me please to find out the bugs in the folowing code . The code doesnt contain any syntax errors but still it doesnt run .

It would be more appropriate if you found the problematic code (i.e., bug), and then ask us what is wrong with it. Asking us to search through a bunch of code to find out what is wrong is not what we (most of us at least) are here for. Narrow your code down to just a few statements and you'll get way more help. Smile | :)

For starters, calling findnumber() with NULL as the second argument will result in a problem when you go to dereference the pointer. The code you have to add a new number to the list is wrong.

"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

johni__boy3-Mar-06 13:30

johni__boy

3-Mar-06 13:30

thanks for your comments, probably you are right.
The second argument by calling findnumber() is not Null but it is used to access to the structure :
typedef struct entry
{
int number; // our entry
int freq; // how often we've seen it

struct entry *next; // pointer to the next item
} entry_t;

I don't understand how is the second line of the input text is loaded in the buffer and what number we are adding to the list.

IdUnknown3-Mar-06 17:56

IdUnknown

3-Mar-06 17:56

johni__boy wrote:
The second argument by calling findnumber() is not Null but it is used to access to the structure :

Initially you set entrylist = NULL; so the first time you call the findnumber function the second argument is NULL. So in the findnumber function you should first check to see if the second argument named "list" is NULL, and if it is, you should return NULL.

Now, look at the last two lines of this block and imagine adding the first node into an empty list.

else
{
// no, create new one.
entry = (entry_t*)malloc(sizeof(entry_t));
entry->freq = 1;
entry->number = number;
entry->next = entrylist;
entrylist = entry->next;
}

1. again, initially entrylist is NULL
2. you create a memory block to hold a node and the next pointer is pointing to entrylist which is NULL. ok
3. entrylist should point to entry not entry->next.

I don't know if there are other problems, but that's what I see without compiling the code. You should learn to use breakpoint, the stack trace, and the watch window because these problems can be easily spotted.

basementman3-Mar-06 7:24

basementman

3-Mar-06 7:24

looks like homework to me.... Sleepy | :zzz:

onwards and upwards...