C / C++ / MFC

Re: Dialog Disappear on pressing Escape key

9-Jul-04 1:24

Please check out the reply in your previous thread..
It has a sample implementation. It might help you...
if not, do not know where the prob is..

Antony M Kancidrowski9-Jul-04 2:43

9-Jul-04 2:43

I normally use PreTranslateMessage to prevent unwanted key presses

BOOL CDialogClass::PreTranslateMessage(MSG* pMsg) 
{
  // Have we pressed a key
  if (pMsg->message == WM_KEYDOWN)
  {
    // We only want to ignore the ESC
    if (pMsg->wParam == VK_ESCAPE)
    {
      return TRUE;
    }
  }
	
  return CDialog::PreTranslateMessage(pMsg);
}

Ant.

I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Williams (Little Britain)

NT to XP upgrade

ganesan balachandar9-Jul-04 0:09

ganesan balachandar

9-Jul-04 0:09

Hi All,
We have a set of applications developed in ASP, VB , Visual C++, SQL Server currently running On NT. Now These applications need to be migrated to XP from NT.

Please provide us information on the following
1. Migration\Upgrade strategy.
2. Issues\Risks involved in migration
3. Back up mechanism
4. Data conversion issues.

Any pointers to existing documents/ whitepapers are very useful.

Please guide us in framing the strategy.
Also share your experience while performing such migration.

Thanks and Regards
Balachandar Ganesan.

I want to fully utilize every thing.

Re: NT to XP upgrade

Antony M Kancidrowski9-Jul-04 0:54

9-Jul-04 0:54

1) I would ensure the applications were tested on XP. The test strategy should endevour to test all code paths. Ideally unit testing should be performed and compared against know good results.

2) Issues, I have had problems with the vanilla XP. You may want to specify at least SP1 as the base OS.

3) Are you going to migrate your development environment to XP? If so why would you not set up a test system to ensure things are running smoothly.

4) No data conversion issues to be worried about.

Ant.

I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Williams (Little Britain)

structures

Anonymous8-Jul-04 23:38

Re: structures:::accessing structure of arrays through a class

8-Jul-04 23:38

i have declared a public structure in a class. and want to use the same in another class. Following is the how i tried ---

class Aclass:public CTrayDialog
{
public:
struct mine{
int days[7];
int mins;
}count;
.......
.......
}

In the initDialog of the other class
Bool Bclass::OnInitDialog()
{
.......
Aclass *a = new Aclass;
int x = a->count.days[0]
.....
}

Now x is not getting the correct value.
rather i think i m not correctly accessing the structure count declared in class Aclass.

need some help in these regard, so that i can fix the problem.

Anonymous9-Jul-04 0:49

Re: structures:::accessing structure of arrays through a class

9-Jul-04 0:49

Please some1 reply my question

Maximilien9-Jul-04 0:56

Maximilien

9-Jul-04 0:56

Can't we sleep ?

Maximilien Lincourt
Your Head A Splode - Strong Bad

Re: structures:::accessing structure of arrays through a class

Johan Rosengren9-Jul-04 1:03

Johan Rosengren

9-Jul-04 1:03

How is any1 supposed to be able to answer? You show a declaration, and say that it's not working. What's wrong with the access?

I suspect that your problem might be the difference between classes and instances, that is, if you have different instances of a class, you'll get different values from the "same" element, but it can only be a guess.

Antony M Kancidrowski9-Jul-04 1:12

9-Jul-04 1:12

Where are you setting the data for days in the first place. If it isn't in the class Aclass constructor then the values you are accessing will be the default ones when you create a new instance of the class Aclass and access its data. If the days array has not been initialised they can be anything.

Ant.

I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Williams (Little Britain)

Anonymous9-Jul-04 1:21

9-Jul-04 1:21

No,i m not setting the data in the constructor; i m setting it in member function of Aclass. Is this the reason that i m not getting the value in Bclass?

Maximilien9-Jul-04 1:28

Maximilien

9-Jul-04 1:28

Anonymous wrote:
Is this the reason that i m not getting the value in Bclass?

maybe ...

Maximilien Lincourt
Your Head A Splode - Strong Bad

Antony M Kancidrowski9-Jul-04 2:28

crystal reports alternatives

9-Jul-04 2:28

Anonymous wrote:

.......<br /> Aclass *a = new Aclass;<br /> int x = a->count.days[0];<br /> .....

Since you create a new instance of Aclass in Bclass. This calls the constructor of Aclass. If Aclass constructor does not call the member function that initialised the data for days then it will contain uninitialised data.

You can either call the initialise member in the constructor of Aclass or change the Bclass code to call the initialise member function

.......<br />
Aclass *a = new Aclass;<br />
a->initialisefunction();   // name of the initialise member function<br />
int x = a->count.days[0];<br />
.....

IMO it is better to do the appropriate initialisation within Aclass.

Ant.

I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Williams (Little Britain)

Irish_GUI8-Jul-04 23:29

Irish_GUI

8-Jul-04 23:29

Hi, we have found that the last version of crystal reports that was compatible with windows 95 was version 8.5.

Can anyone recommend a good commercial alternative to crystal reports, that works with mfc 7.1

Re: crystal reports alternatives

Antony M Kancidrowski9-Jul-04 6:02

discussion point: pointers, memory allocations

9-Jul-04 6:02

Wow, still developing for an OS that Microsoft has stopped supporting. Now that must take guts. Smile | :)

I also find it strange that you are also developing with .NET MFC for such an old platform.

As alternatives go, BusinessObject who bought out Crystal Decisions do provide other reporting alternatives. I am unsure if they still support Windows 95 though. I guess you may struggle to find 95 support for such products today.

Ant.

I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Williams (Little Britain)

V.8-Jul-04 22:31

8-Jul-04 22:31

View following code. Mind the new and delete parts. (I didn't write it Wink | ;)

)

<br />
Param* param;<br />
Param* oldparam = NULL;<br />
ParamValue paramvalue;<br />
param = new Param;<br />
param->SetName(SETTINGS_COMP_MAXNROFLINES);<br />
paramvalue.SetNbrValue(maxnroflines);<br />
param->SetValue(paramvalue);<br />
oldparam = colSettings.GetParamPtr(SETTINGS_COMP_MAXNROFLINES);<br />
delete oldparam;<br />
oldparam = NULL;<br />
colSettings.SetParamPtr(param);<br />

This code works so mind that. The fact is that oldparam will be allocated with new somewhere in another class. Same with param which will be deleted in another class.
Discussion point:
personally I think this is very bad code. I think it would be better practice to keep new and delete in the same class.

What do you think?

"If I don't see you in this world, I'll see you in the next one... and don't be late." ~ Jimi Hendrix

Re: discussion point: pointers, memory allocations

Johan Rosengren9-Jul-04 1:07

Johan Rosengren

9-Jul-04 1:07

Basically, you are correct in my opinion. I don't do that myself, however - I often use containers where I allocate on demand (outside the class) and delete in the destructor. But the safest method would be making the Param ctor private, having a factory function in whatever class colSettings is.

Stuff like this often leads to religious wars among developers, but rigid discipline in memory management is indeed one good way to robust code.

Re: discussion point: pointers, memory allocations

palbano9-Jul-04 5:19

palbano

9-Jul-04 5:19

V. wrote:
I think this is very bad code

Good thinking Big Grin | :-D

There are so many things [bad] about that code I don't know where to begin. There are several ways it could be changed. Without more context it's difficult to offer direction.

Does Param class have only default ctor or are there any that take parameters? If not why not? Things like that.

"No matter where you go, there your are." - Buckaroo Banzai

-pete

Learning C and getting an Errors on Compile!

Cpach8-Jul-04 20:31

Cpach

8-Jul-04 20:31

I am using Visual Studio.net to develope an do not understand why I am recieving these errors. Please send me an email with explination to suaz4@hotmail.com

Here is my CODE:

<br />
include < stdio.h ><br />
<br />
void main()<br />
{<br />
 printf ("Jamsa's C/C++/C# Programmer's Bible!");<br />
}<br />
<br />

Here is my Errors:

first error LNK2019: unresolved external symbol _WinMain@16 referenced in function _WinMainCRTStartup

first fatal error LNK1120: 1 unresolved externals

You never know until you try. Try and Try I Shall.

Egbro8-Jul-04 20:54

Egbro

8-Jul-04 20:54

You should perhaps include something ?

#include "stdafx.h"<br />
<br />
void main()<br />
{ <br />
   printf("Jamsa's C/C++/C# Programmer's Bible!\n");<br />
}

And make sure you have selected to create a win32 console application

Cpach8-Jul-04 20:59

Cpach

8-Jul-04 20:59

I was I just forgot to make it non HTML. I have modified it showing what is included.

You never know until you try. Try and Try I Shall.

Antti Keskinen8-Jul-04 21:26

Antti Keskinen

8-Jul-04 21:26

You have selected a project in Visual Studio named 'Win32 Application'. The code you are writing is designed for a project called 'Win32 Console Application'. There is a crucial difference there. Windows applications all have an entry point called WinMain. Console applications (like all C/C++ console applications incl. Unix) have a starting function called Main.

The difference here comes from the design of the application. Windows applications link with a standard set of libraries, which already contain the Main function. All this function does, however, is to start a Windows thread and execute the WinMain function there. But, as the build error states: the linker cannot find the WinMain function from any of your code modules. This means that you're using a wrong project template, considering that you're writing standard C code.

So, in short, there's nothing wrong with your code. You're just using the wrong project type as template. Copy the code, and create a new project by using "Win32 Console Application" as the template. It can be found from 'New Project Wizard' that you use to create projects. Then paste the code in this project, use build and run. Should work without problems.

-Antti Keskinen

----------------------------------------------
The definition of impossible is strictly dependant
on what we think is possible.