Click here to Skip to main content
15,922,894 members
Home / Discussions / C / C++ / MFC
   

C / C++ / MFC

 
GeneralRe: Using WM_USER, WM_APP or RegisterWindowMessage Pin
CPallini10-Dec-10 0:21
mveCPallini10-Dec-10 0:21 
GeneralRe: Using WM_USER, WM_APP or RegisterWindowMessage Pin
Rajesh R Subramanian10-Dec-10 0:25
professionalRajesh R Subramanian10-Dec-10 0:25 
GeneralRe: Using WM_USER, WM_APP or RegisterWindowMessage Pin
CPallini10-Dec-10 0:23
mveCPallini10-Dec-10 0:23 
JokeRe: Using WM_USER, WM_APP or RegisterWindowMessage Pin
Rajesh R Subramanian10-Dec-10 0:30
professionalRajesh R Subramanian10-Dec-10 0:30 
AnswerRe: Using WM_USER, WM_APP or RegisterWindowMessage Pin
Gary R. Wheeler11-Dec-10 1:31
Gary R. Wheeler11-Dec-10 1:31 
GeneralRe: Using WM_USER, WM_APP or RegisterWindowMessage Pin
yccheok12-Dec-10 18:51
yccheok12-Dec-10 18:51 
GeneralRe: Using WM_USER, WM_APP or RegisterWindowMessage Pin
Gary R. Wheeler13-Dec-10 11:45
Gary R. Wheeler13-Dec-10 11:45 
QuestionPassing Array To Function & Displaying Array Contents. Pin
Mike Certini9-Dec-10 18:41
Mike Certini9-Dec-10 18:41 
AnswerRe: Passing Array To Function & Displaying Array Contents. Pin
Cedric Moonen9-Dec-10 20:25
Cedric Moonen9-Dec-10 20:25 
GeneralRe: Passing Array To Function & Displaying Array Contents. Pin
Mike Certini10-Dec-10 8:10
Mike Certini10-Dec-10 8:10 
GeneralRe: Passing Array To Function & Displaying Array Contents. Pin
Stefan_Lang14-Dec-10 6:54
Stefan_Lang14-Dec-10 6:54 
AnswerRe: Passing Array To Function & Displaying Array Contents. Pin
Niklas L10-Dec-10 21:13
Niklas L10-Dec-10 21:13 
QuestionApplication crashes only in release mode (possible heap/stack corruption) Pin
XTAL2569-Dec-10 11:05
XTAL2569-Dec-10 11:05 
AnswerRe: Application crashes only in release mode (possible heap/stack corruption) Pin
mbue9-Dec-10 11:49
mbue9-Dec-10 11:49 
AnswerRe: Application crashes only in release mode (possible heap/stack corruption) Pin
Luc Pattyn9-Dec-10 12:19
sitebuilderLuc Pattyn9-Dec-10 12:19 
GeneralRe: Application crashes only in release mode (possible heap/stack corruption) Pin
XTAL2569-Dec-10 13:11
XTAL2569-Dec-10 13:11 
GeneralRe: Application crashes only in release mode (possible heap/stack corruption) Pin
Luc Pattyn9-Dec-10 13:16
sitebuilderLuc Pattyn9-Dec-10 13:16 
GeneralRe: Application crashes only in release mode (possible heap/stack corruption) Pin
XTAL2569-Dec-10 17:48
XTAL2569-Dec-10 17:48 
GeneralRe: Application crashes only in release mode (possible heap/stack corruption) Pin
Luc Pattyn9-Dec-10 22:47
sitebuilderLuc Pattyn9-Dec-10 22:47 
GeneralRe: Application crashes only in release mode (possible heap/stack corruption) Pin
XTAL2569-Dec-10 23:21
XTAL2569-Dec-10 23:21 
AnswerRe: Application crashes only in release mode (possible heap/stack corruption) Pin
Rajesh R Subramanian9-Dec-10 17:26
professionalRajesh R Subramanian9-Dec-10 17:26 
AnswerRe: Application crashes only in release mode (possible heap/stack corruption) Pin
XTAL25612-Dec-10 12:09
XTAL25612-Dec-10 12:09 
QuestionC Casting Problem Pin
Andy2029-Dec-10 8:14
Andy2029-Dec-10 8:14 
I have seen the term Fixed_32 for a data item with MSB = 1 and LSB = 1/2**31 ;
Max = 1.0 and Min = -1.0 with units of semicircles (used for Latitude and Longitude)

I did think this was a float to the IEEE-754 Floating-Point Representation.
However the 3rd party that is reading some data via a message structure cannot see the same value.
I mistaken the term Fixed_32 as a standard float but it is a 32 bit int in the message.

The scalling is:-

#define	BEARING_SCALING          	4.65661287307739E-10 

typedef struct ReceiveMessage
{
    unsigned int msgNumber;      // Msg number
    int             msgPosLat;      // Msg latitude
    int             msgPosLong;     // Msg longitude
    unsigned int msgQuality;     // Msg quality
}positionData

#define	BEARING_SCALING          	4.65661287307739E-10 
However I get a crash when I try to load the value (the Latitude was declared as a double and I tried to cast to the int and vice versa.

Code:

// Note 180 is used to scale up from semicircles to degrees
double lat = 55.55;
positionData.msgPosLat = (int)(lat/(BEARING_SCALING * 180));

// and the other way for reading:-

 lat = (double)( positionData.msgPosLat) * BEARING_SCALING * 180;


What is going wrong please, is it the oder of casting or do I need to use fix point stuff?
AnswerRe: C Casting Problem Pin
Luc Pattyn9-Dec-10 9:01
sitebuilderLuc Pattyn9-Dec-10 9:01 
GeneralRe: C Casting Problem Pin
Andy2029-Dec-10 10:41
Andy2029-Dec-10 10:41 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.