C / C++ / MFC Discussion Boards

Re: multibyte tooltips

Richard MacCutchan23-Mar-10 22:35

Richard MacCutchan

23-Mar-10 22:35

See the link in my answer to your question above.

txtspeak is the realm of 9 year old children, not developers. Christian Graus

Strange problem with pointers

anbluemoon23-Mar-10 18:23

anbluemoon

23-Mar-10 18:23

I wrote something like this :

<br />
MD2Mesh::Frame* md2Frame = (MD2Mesh::Frame*)buffer;<br />
uint8* tmp = buffer + 40;<br />
MD2Mesh::Vertex* vtx = (MD2Mesh::Vertex*)tmp;<br />
md2Frame->vertices = vtx;<br />

The value of "vtx" is changed after the line "mdFrame->vertices = vtx"

U can look at the following debugging table:

vtx

0x00434140 {v=0x00434140 "ÐBÄ" normIdx=0 }

origin::MD2Mesh::Vertex *

after line "mdFrame->vertices = vtx" it becomes like this :

vtx	0x00434140 {v=0x00434140 "@AC" normIdx=0 }	origin::MD2Mesh::Vertex *
md2Frame->vertices	0x00434140 {v=0x00434140 "@AC" normIdx=0 }	origin::MD2Mesh::Vertex *

Do u have any ideas ?

Re: Strange problem with pointers

PaulowniaK23-Mar-10 18:59

PaulowniaK

23-Mar-10 18:59

It looks like you've got some cyclic thing going on.

You're setting vtx to something inside md2Frame. But vtx is cast from tmp which is obtained by manipulating buffer. But buffer is cast to md2Frame, in which you are trying to set this value...

I can't say for certain that's the problem, but wouldn't hurt to sort this out properly first.

Almost, but not quite, entirely unlike... me...

Re: Strange problem with pointers

KingsGambit23-Mar-10 19:18

KingsGambit

23-Mar-10 19:18

What is type of the buffer? Is it uint8*?

What expected by buffer + 40?

See, buffer + 1 would point to next unint8 position in the buffer. Is that what intended?

Re: Strange problem with pointers

Avi Berger23-Mar-10 20:01

Avi Berger

23-Mar-10 20:01

You haven't given us all the types and class/structure definitions involved.

You are also using a mess of casts and potential aliasing issues. You have to know what you are doing and be very careful to get this kind of stuff right.

anbluemoon wrote:
MD2Mesh::Frame* md2Frame = (MD2Mesh::Frame*)buffer;

Apparently, buffer is a SomeType_T *buffer set to the address of a block of allocated memory. What is SomeType_T? How big a block of memory? What is a MD2Mesh::Frame? How big is a MD2Mesh::Frame?

Also if MD2Mesh::Frame is not a pod type, you are dead without properly constructing it via its constructor.

anbluemoon wrote:
uint8* tmp = buffer + 40;
MD2Mesh::Vertex* vtx = (MD2Mesh::Vertex*)tmp;

Your magic number could be subject to breakage due to changes. Additionally, it hides your intent. Also don't forget about alignment issues and padding that the compiler can insert in structs.

md2Frame now points to the beginning of the buffer.
vtx now points inside the buffer.

anbluemoon wrote:
md2Frame->vertices = vtx;

You have now changed part of the contents of the buffer.

vtx has not changed at all. It is however a pointer, and what it points to in the buffer has changed because you wrote code to change it.

Evidently, MD2Mesh::Frame.vertices is 40 * sizeof(SomeType_T) bytes from the beginning of the structure.

Please do not read this signature.

Re: Strange problem with pointers

anbluemoon23-Mar-10 22:47

anbluemoon

23-Mar-10 22:47

Here is data structures:

<br />
typedef unsigned char uint8;<br />
<br />
class MD2Mesh<br />
{<br />
struct Vertex<br />
{<br />
   uint8 coord[3],<br />
         normalIdx;<br />
};<br />
<br />
struct Frame<br />
{<br />
  float translation[3],<br />
        rotation[3];<br />
  char  name[16];<br />
  Mesh::Vertex* vertices;<br />
};<br />
<br />
};<br />

At first I tried to do something like :

MD2Mesh::Frame* md2Frame = (MD2Mesh::Frame*)buffer

to get the values from the buffer without initializing the pointer and I managed to get the values of translation, rotation and name but the vertices address didn't point to the "buffer + 40(size of translation + rotation + name)" so i just pass the the address of vtx which is buffer + 40

Re: Strange problem with pointers

Mohan Ramachandra24-Mar-10 21:00

Mohan Ramachandra

24-Mar-10 21:00

Again you forgot to mention the type of buffer?

Windows XP Problems since updating from VS2005 to VS2008

Joschwenk66623-Mar-10 11:12

Joschwenk666

23-Mar-10 11:12

Hallo,

I upgraded from Visual Studio 2005 to Visual Studio 2008, and converted my Project from from VS2005 to VS2008.

But now I get an Error in the following lines:

// Get the current font
	LOGFONT lFont;
	NONCLIENTMETRICS ncm;
	ncm.cbSize = sizeof(NONCLIENTMETRICS);
	VERIFY(SystemParametersInfo(SPI_GETNONCLIENTMETRICS, 
		sizeof(NONCLIENTMETRICS), &amp;ncm, 0));
	lFont = ncm.lfMessageFont;

In Windows XP SystemParametersInfo() returns false, and there are the following Values in ncm after executing the SystemParametersInfo() Function:

Screenshot

When I open my Project in Windows 7, it works without problem. In XP I get an access exeption in msvcr90d.dll when I ignore the failed execution of SystemParametersInfo.

Can someone help me?

Thank you!

Re: Windows XP Problems since updating from VS2005 to VS2008

Iain Clarke, Warrior Programmer23-Mar-10 12:06

Iain Clarke, Warrior Programmer

23-Mar-10 12:06

I would guess NONCLIENTMETRICS has grown... And VS2008 will default WINVER to a later (higher) value, so the size you have compiled is the "bigger" one.

You pass the size of the structure to SystemParametersInfo - and the later OS can handle the earlier structure. But the earlier OS can't handle the later structure.

Doing a little digging...
http://msdn.microsoft.com/en-us/library/ms724506%28VS.85%29.aspx[^]

typedef struct tagNONCLIENTMETRICS {
  UINT    cbSize;
  int     iBorderWidth;
...
  LOGFONT lfMessageFont;
#if (WINVER >= 0x0600)
  int     iPaddedBorderWidth;
#endif 
} NONCLIENTMETRICS, *LPNONCLIENTMETRICS;

You can see my theory is probably right.

XP has no idea what to do with the oversized structure you're giving it...
If you want to be compatible with XP, define WINVER to an appropriate value (0x501 I thiiiink) before including the header files.

Good luck,

Iain.

I have now moved to Sweden for love (awwww).

Re: Windows XP Problems since updating from VS2005 to VS2008

Joschwenk66624-Mar-10 8:22

Joschwenk666

24-Mar-10 8:22

Thank you, VS2008 sets WINVER to Windows Vista. I now set WINVER in the stdafx.h files of my DLLs to WinXP and now it works.

This is the greatest forum in the world! Smile | :)

Re: Windows XP Problems since updating from VS2005 to VS2008

Iain Clarke, Warrior Programmer24-Mar-10 9:32

Iain Clarke, Warrior Programmer

24-Mar-10 9:32

Joschwenk666 wrote:
This is the greatest forum in the world!

This is just a tribute!

(you're welcome, glad I helped)

Iain.

I have now moved to Sweden for love (awwww).

GetFileToSave and Windows 7

Psychopasta23-Mar-10 10:18

Psychopasta

23-Mar-10 10:18

Hi,

I have some code that is as old as the hills and has always worked. It just gets the name of the file to save using the common control Save As dialog:

BOOL GetFileToSave(HWND hwnd, TCHAR *lpstrFileName, DWORD filter)<br />
      {<br />
      static char szFilter[MAX_PATH_LENGTH], szExtension[12];<br />
      BOOL temp;<br />
      char *file, *path;<br />
      temp = FALSE;<br />
      file = malloc(MAX_PATH_LENGTH);<br />
      path = malloc(MAX_PATH_LENGTH);<br />
<br />
      if (file && path)<br />
            {<br />
            GetFilter(szFilter, szExtension, filter);<br />
            ofn.nFilterIndex         = 1;<br />
            ofn.lpstrDefExt         = szExtension;<br />
            ofn.lpstrFilter         = szFilter;<br />
<br />
            GetPathName(file, path, lpstrFileName);<br />
            ofn.hwndOwner            = hwnd;<br />
            ofn.lpstrFile            = file;<br />
            ofn.lpstrInitialDir      = path;<br />
            ofn.Flags               = OFN_HIDEREADONLY | OFN_PATHMUSTEXIST | OFN_OVERWRITEPROMPT;<br />
            EnableAllWindows(FALSE, 0);<br />
            temp = GetSaveFileName(&ofn);<br />
            EnableAllWindows(TRUE, 0);<br />
            if (temp) strcpy(lpstrFileName, ofn.lpstrFile);<br />
            }<br />
      if (file) free(file);<br />
      if (path) free(path);<br />
<br />
      return temp;<br />
      }<br />
<br />

I have SOME users on Windows 7 only who find that the Save As dialog can take up to 30 seconds before it allows the OK button to be pressed. In this time it seems to work normally, but it just not respond to OK being pressed.

This code works fine on all our W7 machines, and I suspect some problem with the enumeration of the attached drives. BUT, can anyone see any weakness in the code? As I say, only a few users with W7 report this issue, the vast majority don't get this, but I'm open to any suggestions about improving the code.

- Mark

Re: GetFileToSave and Windows 7

David Crow24-Mar-10 2:53

David Crow

24-Mar-10 2:53

Psychopasta wrote:
This code works fine on all our W7 machines, and I suspect some problem with the enumeration of the attached drives.

So have you tried attaching those same drives on the machines that work correctly to see if they start misbehaving?

"One man's wage rise is another man's price increase." - Harold Wilson

"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

"Man who follows car will be exhausted." - Confucius

Re: GetFileToSave and Windows 7

Psychopasta24-Mar-10 5:42

Psychopasta

24-Mar-10 5:42

Hi David,

Thanks! I am trying to track down any hardware problems like that, but my interest here is in whether anyone can spot something we've missed in the code snippet I posted. It has run just fine for 20 years or so, but you know how it is...sometimes you just 'get away with it' and then something else changes and what used to work just fine stops doing so.

BTW, I should have said originally that the actual API function we use is GetSaveFileName. GetFileToSave is our function to fill the structure ofn which is declared elsewhere as

static OPENFILENAME ofn;

The problem is that GetOpenFileName opens the common control Save As dialog, which -in rare cases- will wait about 30 seconds before responding to the OK button being pressed.

Thanks again,

- Mark

RichEdit wrong list numbering with letters

wp7323-Mar-10 8:55

wp73

23-Mar-10 8:55

Hello!

I use CRichEditCtrl ver. 4.1 and try use advanced functions of this control. Unfortunately I have some weird problems. For example when I use numbered paragraphs with letters (PARAFORMAT2.wNumbering = 3 or 4) I get:

a. item 1
b. item 2
...
z. item 26
aa. item 27
ab. item 28
..
yy. item 675
yz. item 676
a'a item 677 - why!? should be "za"!
a'b item 678 ("zb)"
...
a'z item 702 ("zz")

aaa. item 703
.....

When I start list with PARAFORMAT2.wNumberingStart = 677 I got the same error :/
How to fix it? It's MS error? Mayby I must write my own auto-list code Hmmm | :|

I use TOM interface too but error still happen.

Others inconveniences:
1) TOM uses long type to numering of the list (ITextPara::SetListStart), but RichEdit can use max 65535 items ("crxo" with letters numbering). Sometimes it's too few...

2) ITextDocument::BeginEditCollection/EndEditCollection is not implemented, I can use only Undo(tomSuspend)/Undo(tomResume)

3) I can only use #. #) (#) # for list style numbering

Best regards
W.

Re: RichEdit wrong list numbering with letters

wp7324-Mar-10 3:15

wp73

24-Mar-10 3:15

Very simple project (C++ VS 2003) with this error

I use:

PARAFORMAT2 pf;
memset(&pf, 0, sizeof(pf));
pf.cbSize = sizeof(pf);
pf.dwMask = PFM_NUMBERING | PFM_NUMBERINGSTYLE | PFM_NUMBERINGSTART;
pf.wNumbering = 3;
pf.wNumberingStyle = 0x200 | 0x8000; //0x400
pf.wNumberingStart = 677;
mvEditor.SetParaFormat(pf);

problem displaying unicode filenames in a list box

sashoalm23-Mar-10 7:25

sashoalm

23-Mar-10 7:25

I have a project which was started as ANSI, and the project can't be converted to unicode for the foreseeable future. However, I have to display some unicode filenames in a list box by calling the unicode versions of the Win32 functions. But I have a problem.

LPCWSTR strFile = L"Some chinese or arabic unicode text, like that - يتشخيتختصضخيتضختصت.doc";
MessageBoxW(0, strFile, 0, 0);
SendDlgItemMessageW(GetSafeHwnd(), IDC_LISTBOX_FILES, LB_ADDSTRING, 0, (LPARAM) text);

The code above will show the message box with the correct unicode text, but it will display "????????.doc" in the list box. I tried changing the font of the list box but it didn't fix it.

There is sufficient light for those who desire to see, and there is sufficient darkness for those of a contrary disposition.
Blaise Pascal

Re: problem displaying unicode filenames in a list box

Eugen Podsypalnikov23-Mar-10 22:19

Eugen Podsypalnikov

23-Mar-10 22:19

What is the text here ? Smile | :)

virtual void BeHappy() = 0;

Simple Treeview in MFC 2008

D.Manivelan23-Mar-10 3:54

D.Manivelan

23-Mar-10 3:54

Hi friends,
I need immediatly simple treeview in cview full sample code, plz help me.

Thanks and Regards,
D.Manivelan,

Re: Simple Treeview in MFC 2008

Maximilien23-Mar-10 4:12

Maximilien

23-Mar-10 4:12

Create a new project (either MDI or SDI) with the wizard and at one of the last step of the wizard, you can select what type of view you want to use as the default view of your application.

or, if you already have an application with a default CView class, you could create a CTreeCtrl object in the view and use it.

for example :

class YourView : public CView
{
  // lots of default stuff...
  
  CTreeCtrl m_YouTree;
  afx_msg int OnCreate(LPCREATESTRUCT lpCreateStruct );
  afx_msg void OnSize(UINT nType, int cx, int cy);

};

and

int YourView::OnCreate(LPCREATESTRUCT lpCreateStruct )
{
	if (CView::OnCreate(lpCreateStruct) == -1)
		return -1;

	CRect rect;
	GetClientRect(rect);
	m_Tree.Create(WS_CHILD|WS_VISIBLE, rect, this, 1234);

	m_Tree.InsertItem(_T("root"), TVI_ROOT);

	return 0;
}

void YourView::OnSize(UINT nType, int cx, int cy)
{
	if ( m_Tree.GetSafeHwnd() )
	{
		CRect rect;
		GetClientRect(rect);
		m_Tree.MoveWindow(rect);
	}
}

Max.

Watched code never compiles.

Re: Simple Treeview in MFC 2008

Iain Clarke, Warrior Programmer23-Mar-10 8:33

Iain Clarke, Warrior Programmer

23-Mar-10 8:33

Member 4482742 wrote:
full sample code

Sorry you'll have to do a lot of your own work.

But have a look at CTreeView. It should do a lot of what you want!
http://msdn.microsoft.com/en-us/library/th0y74x7%28VS.80%29.aspx[^] (just first link I hit)

http://www.codeproject.com/KB/tree/#TreeView%20Controls[^] may also be worth a look.

Iain.

I have now moved to Sweden for love (awwww).

Staticly linking MFC in VS2008 app produces compiling errors

josip cagalj22-Mar-10 23:03

josip cagalj

22-Mar-10 23:03

Hi, I made an app in MFC VS2008 which works ok, but there are some PC's where my app just wont work (you allready know this story right..) so I decide it would be for the best to staticly link MFC. This produced some errors while compiling:

1>mysys.lib(my_messnc.obj) : error LNK2001: unresolved external symbol __imp____p__iob
1>libmysql.lib(dbug.obj) : error LNK2019: unresolved external symbol __imp____p__iob referenced in function __db_push_
1>libmysql.lib(net.obj) : error LNK2001: unresolved external symbol __imp____p__iob
1>mysys.lib(safemalloc.obj) : error LNK2001: unresolved external symbol __imp____p__iob
1>mysys.lib(my_init.obj) : error LNK2001: unresolved external symbol __imp____p__iob
1>libmysql.lib(dbug.obj) : error LNK2019: unresolved external symbol __imp__fprintf referenced in function __db_enter_
1>libmysql.lib(net.obj) : error LNK2001: unresolved external symbol __imp__fprintf
1>mysys.lib(safemalloc.obj) : error LNK2001: unresolved external symbol __imp__fprintf
1>mysys.lib(my_init.obj) : error LNK2001: unresolved external symbol __imp__fprintf
1>libmysql.lib(dbug.obj) : error LNK2019: unresolved external symbol __imp__vfprintf referenced in function __db_doprnt_
1>libmysql.lib(dbug.obj) : error LNK2019: unresolved external symbol __imp__getpid referenced in function _DoPrefix
1>OLDNAMES.lib(getpid.obi) : error LNK2001: unresolved external symbol __imp__getpid
1>libmysql.lib(dbug.obj) : error LNK2019: unresolved external symbol __imp__perror referenced in function _DBUGOpenFile
1>libmysql.lib(dbug.obj) : error LNK2019: unresolved external symbol __imp__freopen referenced in function _dbug_flush
1>mysys.lib(my_error.obj) : error LNK2019: unresolved external symbol __imp____p__pctype referenced in function _my_error
1>mysys.lib(my_error.obj) : error LNK2019: unresolved external symbol __imp____p___mb_cur_max referenced in function _my_error
1>strings.lib(Int2str.obj) : error LNK2019: unresolved external symbol __imp__ldiv referenced in function _int2str
1>OLDNAMES.lib(getpid.obi) : error LNK2001: unresolved external symbol __imp___getpid

if anyone can Help please do so. I've been googling and still couldn't find the right way. Thanks in advance, and sorry for my bad language!

Re: Staticly linking MFC in VS2008 app produces compiling errors

CPallini22-Mar-10 23:26

CPallini

22-Mar-10 23:26

I guess the libraries you're using link dynamically with the runtime.
Why don't you deploy the required DLL's instead of linking the project statically?
Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Re: Staticly linking MFC in VS2008 app produces compiling errors

josip cagalj23-Mar-10 0:02

josip cagalj

23-Mar-10 0:02

First let me thank you for replaying.
I have following requirements I need to keep. I need to distribute my exe to multiple machines with no knowledge about OS installed. I've tried on several local computers and where app didn't work I've get different error messages. So by static linking MFC I hope I'll be able to get it to work!

Re: Staticly linking MFC in VS2008 app produces compiling errors

CPallini23-Mar-10 0:07

CPallini

23-Mar-10 0:07

However, if my previous guess was correct, you have to either get new (statically linked with the runtime) binaries of the libraries you use or compile yourself such libraries.
Smile | :)

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