C / C++ / MFC

Joaquín M López Muñoz19-Feb-02 6:08

Joaquín M López Muñoz

19-Feb-02 6:08

VC 7.1 will.
Allegedly. I've come to take MS statements with a grain of salt. When I see it I will believe it.

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

Nemanja Trifunovic19-Feb-02 6:10

Nemanja Trifunovic

19-Feb-02 6:10

Joaquín M López Muñoz wrote:
Allegedly. I've come to take MS statements with a grain of salt. When I see it I will believe it.

LOL. Then my answer will be:

No, but VC 7.1 should.

I vote pro drink Beer | [beer]

Tim Smith19-Feb-02 9:51

Tim Smith

19-Feb-02 9:51

Be more assertive. That has been our problem as developers using MS products.

No, but VC 7.1 should. Damnit!

Smile | :)

Tim Smith

I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?

Christian Graus19-Feb-02 11:58

Christian Graus

19-Feb-02 11:58

I would normally agree, but it has been publically stated by Mr Lippman from memory that Loki and Boost compile with no problems on their internal build of VC7. I doubt they would pull it off and then not release it.

Christian

I have come to clean zee pooollll. - Michael Martin Dec 30, 2001

Picture the daffodil. And while you do that, I'll be over here going through your stuff.

Joaquín M López Muñoz19-Feb-02 19:49

Joaquín M López Muñoz

19-Feb-02 19:49

I doubt they would pull it off and then not release it
Keep this for the record, Christian Smile | :)

Mr Lippman has embraced with enthusiasm his new role as MS hypeman --his latest article on MSDN Magazine is a thing to forget-- so I'd take this kind of statements very lightly. To the best of my knowledge, there's no current C++ compiler capable of compiling Loki in its entirety (moreover, Loki's source code is not standard compliant in some minor details), so the assertion of VC++ being able to do the job is a rather strong one. But then again, I'd really love to know they're telling the truth (really).

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

Michael Dunn19-Feb-02 8:29

Michael Dunn

19-Feb-02 8:29

Jamie Hale wrote:
And is anyone else disgusted with the state of the VC6 STL implementation code?

No, you're the only one. Wink | ;)

--Mike--
Fetchez la vache!
My really out-of-date homepage
Sonork - 100.10414 AcidHelm
Big fan of Alyson Hannigan and Jamie Salé.

Steen Krogsgaard20-Feb-02 0:03

Steen Krogsgaard

20-Feb-02 0:03

I've seen a lot of discussion about MS not supporting PTS - what the f*** (pardon my french) is PTS? I use templates regularly and afaik I have never had any need for PTS (or maybe I haven't realized it as I don't know what it is... Smile | :)

)

Cheers
Steen.

"To claim that computer games influence children is rediculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"

Problem with Class View VC++ 6

Jamie Hale20-Feb-02 6:36

Jamie Hale

20-Feb-02 6:36

I'm just starting to understand it, but it goes something like this...

If you have a template

template<typename T>
class Wank {
public:
void Stoo();
};

you can "override" the definition by providing other templates

template<typename T>
class Wank<int> {
public:
void Stoo();
};

template<typename T>
class Wank<T *> {
public:
void Stoo();
};

The first is used when you declare a Wank object with an int parameter - this is called explicit template specialization. The second is used when you declare a Wank object with a pointer parameter - this is called partial template specialization. PTS is used a bunch with STL iterators.

This is just an example. There have been some good articles in CUJ about it, and I have a few books (STL stuff) coming that will hopefully go into much more detail.

J

Mike Gaskey19-Feb-02 5:37

Mike Gaskey

19-Feb-02 5:37

I have a project that I moved over to version six (current w/all updates). Since then I added several new classes. Two of these do not appear in the class browser view. One is a xxxDoc and the other is the xxxView. The xxxDoc did appear for awhile but has disappeared. I have rebuilt the .clw file several times thinking the problem is there. The code gets executed, other classes that call on these have no problem. In fact the only problem I can see is the fact that these do not appear in the class browser view, which means that to locate a function, etc., I have to use the find command. Anyone know of an IDE problem that would cause this?

Thanks - Mike

Re: Problem with Class View VC++ 6

Rage19-Feb-02 5:43

Rage

19-Feb-02 5:43

I know that the class browser has sometimes difficulty to show classes. If you want to make them appear again, just write something in your class (like "int i;"), presse enter, delete it again, or enter a carriage return after the definition and delete it, and you should see your class back again in the class browser.
ex:

class CMyClass : public CDialog
{
-->

class CMyClass : public
CDialog
{
--->

class CMyClass : public CDialog
{

Just do that (do not rebuild or anything), it works again for a moment.i know it is weird, but that´s the only solution I´ve found yet.

RaGe/NewGen

Re: Problem with Class View VC++ 6

Jamie Hale19-Feb-02 6:25

Jamie Hale

19-Feb-02 6:25

Check out the great article on VC++ innards. The demo code has a VC++ plug-in called OpenVC. It adds a little "radioactivity" icon to your tool bar, and when you click it, it rebuilds your workspace and classview.

It is extremely handy - I couldn't live without it. Smile | :)

Re: Problem with Class View VC++ 6

J Patel19-Feb-02 7:02

J Patel

19-Feb-02 7:02

Delete your .NCB file and re-open the project. The add-in referred to by the other poster does this automatically.

HTH

Jignesh

Accessing Dialog Data in MFC

Rage19-Feb-02 5:32

Rage

19-Feb-02 5:32

My Problem is rather complex.

I have created an MFC dialog based Application. There are two windows in
this Dialog, each of them has its own class derived from CDialog - CMainDlg (created by MFC) and CChild (created by adding a Dialog with the Wizard).
I have an CChild member object (name it m_ChildWin) in CMainDlg, in order to be able to open the Child Dialog with m_childwin.CreateWindow(...)

I also have two CListCtrl declared as member variable, one in CMainDlg and one in CChild. I want to access the CListCtrl from CMainDlg with functions from the CChild class. (In fact, CChild is only a setup dialog for CMainDlg).

How do I manage to do this ?

To make things clearer:

class CMainDlg : public CDialog
{
...
CListCtrl m_MainList;
CChild m_ChildWin;

void OnButton
{
m_ChildWin.CreateWindow(...);
}
}

class CChild : public CDialog
{
...
CListCtrl m_SetupList;
void UpdateMainList;
{
How do I update m_MainList from here ?!
}
}

Thanks.

RaGE/Newgen

Nish Nishant19-Feb-02 5:52

Nish Nishant

19-Feb-02 5:52

Rage wrote:
m_ChildWin.CreateWindow(...);

Hmmm. I'd have thought you'd be better off using Create(). In fact neither CDialog nor CWnd has a member function called CreateWindow.

Rage wrote:
How do I update m_MainList from here ?!

In this particular case since the CMainDlg object is your main window [this being a dialog based app], you can use AfxGetMainWnd() to get a pointer to your CMainDlg object [cast it] and now you have access to m_MainList.

Regards
Nish

Nish was here, now Nish has gone;
He left his soul, to turn you on;
Those who knew Nish, knew him well;
Those who didn't, can go to hell.

I like to Jig | [Dance]

on the Code Project

Sonork ID 100.9786 voidmain
www.busterboy.org

Derek Waters19-Feb-02 11:32

Derek Waters

19-Feb-02 11:32

While Nish's answer is strictly correct, I would suggest (from an OO point of view) that this might be a bit safer:

In the CChild class, add a member function called Create, for example, which takes all of the parameters that you would normally need for a Create call and then a CListCtrl pointer as well:

BOOL CChild::Create(CListCtrl *apListCtrl, UINT nIDTemplate, CWnd *pParentWnd)
{
  if (CDialog::Create(nIDTemplate, pParentWnd))
  {
    m_pListCtrl = apListCtrl;
    return TRUE;
  }
  return FALSE;
}

where m_pListCtrl is a CListCtrl * member variable. You can then use this at will without having to rely on calls to AfxGetMainWnd(). Not only does this ensure that the correct list control is used, it means you don't have to make the CListCtrl public in your main dialog class.

------------------------
Derek Waters
derek@lj-oz.com

Rage19-Feb-02 21:57

Rage

19-Feb-02 21:57

first, thanks for your answer...
Of course, it was Create and not CreateWindow ... sorry ..

Derek Waters wrote:
In the CChild class, add a member function called Create, for example, which takes all of the parameters that you would normally need for a Create call and then a CListCtrl pointer as well:

Sorry, i do not see the point in this, since the dialog is called in CMainDlg with m_ChildWin.Create(nIDTemplate,pParentWnd). Maybe I did not get the thing ? Confused | :confused:

RaGE

Problems with IMessageFilter in SDI

Derek Waters20-Feb-02 11:21

Derek Waters

20-Feb-02 11:21

Basically, I was just using the Create call as a way to pass in the extra parameters you need:

m_ChildWin.Create(&m_MyListCtrl, IDD_MY_CHILD_DIALOG, this)

if:

BOOL CChildDlg::Create(CListCtrl *apListCtrl, UINT nIDTemplate, CWnd *pParentWnd)
{
  m_pMyListCtrlPtr = apListCtrl; // Store the list control pointer in the child wnd class for later use.
  return CDialog::Create(nIDTemplate, pParentWnd);
}

so you're intercepting the Create call (but still calling the dialog Create function) to pass in your extra parameters.

As I said, this is just my opinion of how it should be done, feel free to use Nish's method, or any other you can think of.

------------------------
Derek Waters
derek@lj-oz.com

Fredrik Skog19-Feb-02 4:42

Fredrik Skog

19-Feb-02 4:42

I've tried to implement my own message filter (IMessageFilter) in a client that talks to a COM server.
It works if I test it in a simple dialog app, but when I implement it in an SDI app, the filter is never used. Frown | :(

Anyone got any ideas?

Cheers,

/Fredrik

Sonork ID: 100.11430:PhatBoy

Re: Problems with IMessageFilter in SDI

Fredrik Skog21-Feb-02 0:33

Fredrik Skog

21-Feb-02 0:33

Funny, it works in the SDI app if I call AfxOleInit() first.
In the dialog app there is no need for that. Confused | :confused:

Cheers,

/Fredrik

Sonork ID: 100.11430:PhatBoy

Beginner Dialog::OnOK() Question

CreekDawg19-Feb-02 4:28

CreekDawg

19-Feb-02 4:28

Hi,

I have a dialog based application with the standard "Ok" and "Cancel" buttons at the bottom. After the dialog app loads, if I press the 'enter' key, the app closes (the Dialog::OnOK() Event Fires). How can I override this action? In other words, I want to be able to press the 'enter' key and not close the application (not fire the OnOK() event method). How do I do this?

Thanks.

v_krishnan19-Feb-02 4:34

v_krishnan

19-Feb-02 4:34

There are two ways to do this -

1. You can do this by overriding the OnOK function in your dialog class and do NOT call the base class OnOK in that function.

2. In the dialog editor remove the default button property of the OK button.

Hope this helps

Krishnan

Joaquín M López Muñoz19-Feb-02 4:35

Joaquín M López Muñoz

19-Feb-02 4:35

Please see Mike Dunn's C++ FAQ, §7.4.

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo

Roger Allen19-Feb-02 4:37

Roger Allen

19-Feb-02 4:37

Put in your own OnOK(0 for the dialog, and have code liek this:

CMyDialog::OnOK()
{
if (GetFocus() != GetDlgItem(IDOK))
return ; // only allow exit if OK has the focus
}

Roger Allen
Sonork 100.10016

If I'm not breathing, I'm either dead or holding my breath.
A fool jabbers, while a wise man listens. But is he so wise to listen to the fool?
Please step to the rear of the car and make room for more victims. - John Simmons the Outlaw programmer, 1st Feb 2002, in the lounge