C / C++ / MFC

cppcook19-Jul-06 9:02

cppcook

19-Jul-06 9:02

hey man,
why do you want to do this? Garmin products have features other than navigation?
btw, I have a garmin streetpilot i5 and it works very well. Smile | :)

kitty519-Jul-06 9:11

19-Jul-06 9:11

dinesh_pam wrote:
if( !SetupDiEnumDeviceInterfaces( theDevInfo, NULL, (GUID* &GUID_DEVINTERFACE_GRMNUSB, &theInterfaceData ) && GetLastError() == ERROR_NO_MORE_ITEMS )
{
gHandle = 0;
return;
}

In the above try this so see what the error exactly is:

<br />
// Find the requested interface<br />
if( !SetupDiEnumDeviceInterfaces( theDevInfo, NULL, (GUID* &GUID_DEVINTERFACE_GRMNUSB, &theInterfaceData ) )<br />
{<br />
if(GetLastError()== ERROR_NO_MORE_ITEMS)               <br />
{<br />
printf("**Error: couldn't find device(no more items), (0)\n");<br />
SetupDiDestroyDeviceInfoList(theDevInfo);<br />
gHandle = 0;<br />
return -1;<br />
}<br />
else<br />
{<br />
printf("**Error: couldn't enum device, (%d)\n"), GetLastError());<br />
SetupDiDestroyDeviceInfoList(theDevInfo);<br />
gHandle = 0;<br />
return -1;<br />
}<br />
}<br />

Kitty5

dinesh_pam19-Jul-06 9:29

dinesh_pam

19-Jul-06 9:29

thank you kindly for the reply. The error is couldnt find device. i.e. "**Error: couldn't find device(no more items), (0)"

Is there anyway I could just read the virtual COM port like hyperterminal is doing instead of this?

Dinesh

kitty519-Jul-06 9:45

19-Jul-06 9:45

Not quite sure how to:

dinesh_pam wrote:
Is there anyway I could just read the virtual COM port like hyperterminal is doing instead of this?

However:
Did you include the file that contains the device's GUID?
It's usually a .h file that looks like:

<br />
#ifdef DEFINE_GUID<br />
<br />
// The GUID that is used to identify this device's interface<br />
// {AF1B231E-1180-420b-8CB6-2ED2A53F9F92}<br />
DEFINE_GUID(GUID_DEVINTERFACE_ALTGENERIC, 0xaf1b231e, 0x1180, 0x420b, 0x8c, 0xb6, 0x2e, 0xd2, 0xa5, 0x3f, 0x9f, 0x92);<br />
<br />
#endif<br />

If you don't have a GUID for your device the PC will not be able to create a handle to the device. The handle is what give you the ability to communicate to the device.

Also, make sure that you: #include "INITGUID.H" in that GUID .h file.

Kitty5

dinesh_pam19-Jul-06 10:06

dinesh_pam

19-Jul-06 10:06

Thanks, but all that's done further up in the file.

I'm really frustrated with this. I find it hard to believe such a simple task can be so complicated.. Anybody else help me out please? Unsure | :~

Dinesh

led mike19-Jul-06 10:33

led mike

19-Jul-06 10:33

Well your call to SetupDiEnumDeviceInterfaces does not have matching parenthesis so something very wrong is there.

You are not checking the HDEVINFO return value so you may not even have a valid handle to pass to SetupDiEnumDeviceInterfaces

HDEVINFO hDevInfoSet = SetupDiGetClassDevs(&guid, NULL, NULL, DIGCF_ALLCLASSES );
if( INVALID_HANDLE_VALUE == hDevInfoSet)
{
	DWORD dwErr = ::GetLastError();
	// display error information or whatever
}
else
{ ...}

You are not initializing the SP_DEVICE_INTERFACE_DATA structure which is probably not a problem but you never know.

SP_DEVICE_INTERFACE_DATA devInterfaceData = {0};
devInterfaceData.cbSize = sizeof(devInterfaceData);

Dialog Box DDX problem

kitty519-Jul-06 8:13

19-Jul-06 8:13

Background:
I first created an MDI MFC application called test.

I then created a dialog named: IDD_MANUAL_CDIN.
This does simple data exchange:
User inputs a string in edit box1 (i.e. hello).
User clicks on "SEND" button.
User should see in edit box2 "I typed: hello".

I then created a class for that dialog which is implemented in manual.cpp:

<br />
#include "stdafx.h"<br />
#include "test.h"<br />
#include "manual.h"<br />
<br />
// manual dialog<br />
IMPLEMENT_DYNAMIC(manual, CDialog)<br />
<br />
manual::manual(CWnd* pParent /*=NULL*/)<br />
	: CDialog(manual::IDD, pParent)<br />
	, m_nIn(_T("init"))<br />
	, m_nSent(_T("I sent "))<br />
{}<br />
<br />
void manual::DoDataExchange(CDataExchange* pDX)<br />
{<br />
	CDialog::DoDataExchange(pDX);<br />
	DDX_Text(pDX, IDC_IN, m_nIn);<br />
	DDX_Text(pDX, IDC_SENT, m_nSent);<br />
}<br />
<br />
BEGIN_MESSAGE_MAP(manual, CDialog)<br />
	ON_BN_CLICKED(IDC_BUTTON_SEND, &manual::OnButtonSend)<br />
END_MESSAGE_MAP()<br />
<br />
// App command to run the dialog<br />
void manual::OnManual()<br />
{<br />
	manual manualDlg;<br />
	manualDlg.DoModal();<br />
}<br />
// manual message handlers<br />
<br />
void manual::OnButtonSend()<br />
{<br />
	// TODO: Add your control notification handler code here<br />
	AfxMessageBox(tempSend); //DEBUG<br />
	AfxMessageBox(m_nIn); //DEBUG<br />
	m_nSent += m_nIn;<br />
}<br />

and manual.h:

<br />
class manual : public CDialog<br />
{<br />
	DECLARE_DYNAMIC(manual)<br />
<br />
public:<br />
	manual(CWnd* pParent = NULL);   // standard constructor<br />
	virtual ~manual();<br />
	afx_msg void OnManual();<br />
<br />
// Dialog Data<br />
	enum { IDD = IDD_MANUAL_CDIN };<br />
<br />
protected:<br />
	virtual void DoDataExchange(CDataExchange* pDX);    // DDX/DDV support<br />
<br />
	DECLARE_MESSAGE_MAP()<br />
public:<br />
	CString m_nIn;<br />
	CString m_nSent;<br />
	afx_msg void OnButtonSend();<br />
};<br />

I then changed the toolbar created by the MFC App wizard so that when you click one button it will open a dialog that corresponds to that button.
All this code is in the test.cpp file:
I do:

<br />
#include "manual.h"<br />
BEGIN_MESSAGE_MAP(CSpaceCubeDataRxApp, CWinApp)<br />
	ON_COMMAND(ID_MCD_INPUT, &manual::OnManual)<br />
	ON_COMMAND(ID_APP_ABOUT, &CtestApp::OnAppAbout)<br />
	// Standard file based document commands<br />
	ON_COMMAND(ID_FILE_NEW, &CWinApp::OnFileNew)<br />
	ON_COMMAND(ID_FILE_OPEN, &CWinApp::OnFileOpen)<br />
END_MESSAGE_MAP()<br />

Question:
After compiling I go to type in the string "hello" and click send and nothing pops up in edit box2. I know the "SEND" button function works b/c of the DEBUG AfxMessageBox the I put in it. Nothing is assigned to the variable m_nIn. The data exchange isn't working.

What am I missing?

Kitty5

Michael Dunn19-Jul-06 8:30

Michael Dunn

19-Jul-06 8:30

DDX doesn't happen automagically, you need to call UpdateData() to transfer the data between the controls and variables.

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ

kitty519-Jul-06 8:32

Re: Dialog Box DDX problem [modified]

19-Jul-06 8:32

DUH!

I knew it was something simple...

Kitty5

kitty521-Jul-06 3:10

21-Jul-06 3:10

Ok, I've figured out how to get the dialog boxes to exchange data.
Now I'm trying to figure out how when you have one dialog box open how you can open another one while the 1st box is still open and functioning.

Right now when I have a dialog box open I can only work in the one box and can't click on anything outside it (i.e. clicking on the toolbar to open another dialog box or getting the about box to come up isn't working...)
I guess I'm looking for making these dialog boxes work like child forms in an MDI MFC App.

Thanks,

Kitty5

-- modified at 9:17 Friday 21st July, 2006

David Crow19-Jul-06 9:29

19-Jul-06 9:29

kitty5 wrote:
void manual::OnManual()
{
manual manualDlg;
manualDlg.DoModal();
}

Is this right? I've never seen a dialog's method bring up another instance of itself.

Why do you not have two CEdit member variables in manual, one for each of the edit controls?

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

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

kitty520-Jul-06 3:47

20-Jul-06 3:47

DavidCrow wrote:
kitty5 wrote:
void manual::OnManual()
{
manual manualDlg;
manualDlg.DoModal();
}

Is this right? I've never seen a dialog's method bring up another instance of itself.

I copied exactly what the MFC App wizard did for the AboutBox that it provides.

DavidCrow wrote:
Why do you not have two CEdit member variables in manual, one for each of the edit controls?

Yes, one for each edit control... Actually, I changed the "Variable Type" to CString and the "Category" to Value (This was all done when you right click on the edit box and click on "Add Variable".

Did I do something wrong?

Kitty5

David Crow20-Jul-06 4:22

Problem with the pow( ) function [modified]

20-Jul-06 4:22

kitty5 wrote:
I copied exactly what the MFC App wizard did for the AboutBox that it provides.

Unlikely. That code would most likely resemble:

void CMyDialog::OnManual()
{
    CAboutDlg about;
    about.DoModal();
}

Note how the two dialog objects are different.

kitty5 wrote:
Yes, one for each edit control... Actually, I changed the "Variable Type" to CString and the "Category" to Value (This was all done when you right click on the edit box and click on "Add Variable".

Did I do something wrong?

I personally do not use CString for edit controls. That's what CEdit was designed for. Use its SetWindowText() method, rather than UpdateData(), and you'll have far less problems.

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

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

KaKa'19-Jul-06 7:29

KaKa'

19-Jul-06 7:29

Hi,

I am using Visual C++ 2005 to write code a win32 console application.

There was an error message about the power function when I compiled the code. It is: error c2668: 'pow' :ambiguous call to overloaded function.

The statement is:

tempDistance += pow((data[selectedInstance][k]-data[j][k]),2);

I used various headers like: cmath and math.h
but the error message remained the same.

What is the cause of the error? I've checked the syntax and it seems correct.

-- modified at 13:30 Wednesday 19th July, 2006

David Crow19-Jul-06 7:34

19-Jul-06 7:34

KaKa` wrote:
There was an error message about the power function when I compiled the code. It is: error c2668: 'pow' :ambiguous call to overloaded function.

Apparently there's more than one pow() function. Which one do you want to use?

"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank

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

toxcct19-Jul-06 7:35

toxcct

19-Jul-06 7:35

how is defined the data matrix (what type) ?

i think it contains values other than int, that's why the compiler doesn't know which function to call (pow(int, int) or pow(double, double) ?? ).

TOXCCT >>> GEII power

[VisualCalc 3.0 updated ][Flags Beginner's Guide new! ]

pgav19-Jul-06 7:37

pgav

19-Jul-06 7:37

I'm thinking that it could have something to do with your data types... are all your variables "int", or are you mixing types?

Patrick

cppcook19-Jul-06 7:42

cppcook

19-Jul-06 7:42

If you couldn't figure out the problem, why don't you write your own pow() function? It's simple...

Zac Howland19-Jul-06 8:41

Zac Howland

19-Jul-06 8:41

cppcook wrote:
If you couldn't figure out the problem, why don't you write your own pow() function? It's simple...

Simple for integer exponents ... not so simple for decimal exponents.

As for the original post, my guess is that you are mixing types (that is, raising a double by an integer power). While there is nothing wrong with that, pow is usually defined:

From MSDN:

double pow(
   double x,
   double y 
);
double pow(
   double x,
   int y
);  // C++ only
double pow(
   int x,
   int y
);  // C++ only
float pow(
   float x,
   float y 
);  // C++ only
float pow(
   float x,
   int y
);  // C++ only
long double pow(
   long double x,
   long double y
);  // C++ only
long double pow(
   long double x,
   int y
);  // C++ only
float powf(
   float x,
   float y 
);

Try explicitly casting your types:

double base = 3.0;
int power = 5;
int result = pow(base, (double)power);

If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week

Zac

Ambiguous call

Ennis Ray Lynch, Jr.19-Jul-06 8:47

Ennis Ray Lynch, Jr.

19-Jul-06 8:47

Is a result of implicit casts being available. Explicitly case each parameter to the datatype to use that matches one of the pow formal parameter lists.

A man said to the universe:
"Sir I exist!"
"However," replied the Universe, "The fact has not created in me A sense of obligation."

-- Stephen Crane

NrmMyth19-Jul-06 12:20

NrmMyth

19-Jul-06 12:20

If you know nothing about function overloading just cast both parameters to (double) and it will compile.

tempDistance += pow(((double)data[selectedInstance][k]-data[j][k]),2.0);

Edit Box alignment problem

KaKa'26-Jul-06 22:21

KaKa'

26-Jul-06 22:21

Thanks all for the replies.......i used the simple way and cast both parameters to double and it can work now.

cppcook19-Jul-06 7:24

cppcook

19-Jul-06 7:24

Hi everyone,

I have an Edit box in a dialog with multiline property and four scroll bar properties checked. A text file is read into the edit box. The file is tab spaced structured data file (40 rows, but with thousands of columns). The problem is the edit box will break the row in the original file into several rows and display it. This makes the data looks unstructured and disordered. I know this is because the row is too long so the Edit box wraps words automatically. But can we avoid this?

thanks,

gavin

Re: Edit Box alignment problem

David Crow19-Jul-06 7:32