|
waldermort wrote: Why are there two definitions?
The simple answer: When you have multiple teams working on adding support for similar features, and they don't communicate well, you end up with overlapping functionality.
This is also part of the reason why there are sections of MFC that deal with return values for errors, others that throw exceptions, and still others that require you to check GetLastError periodically.
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
|
|
|
|
|
UNICODE is used by the Windows headers to switch between the A and W versions of APIs
_UNICODE is used by the CRT headers to switch between MBCS and Unicode versions of the string functions (this is how _tcsxxx macros work)
You should always define both or neither of those symbols
--Mike--
Visual C++ MVP 
LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
|
|
|
|
|
I want to add the regsvr32 command as a post-build event in my makefile.How do i do it?
Is it possible to specify post-build events in makefiles?
a small example will be appreciated
|
|
|
|
|
Hello,
I have a program that takes a command line argument and then converts it to a unicode string (with MultiByteToWide) for use in NetLocalGroupEnum (not shown in the program extract below).
The strange thing is that when I have a printf (line 18 below) at the start of the program, it seems to work fine (It prints the converted string).
But when I remove the printf the string conversion is not correct anymore. I must be doing something wrong with 'sizeof' or with the MultiByteToWideChar function.
01 #pragma comment( lib, "netapi32.lib" )
02 #include <stdio.h>
03
04 #include <stdlib.h>
05 //#include <string.h>
06 #include <windows.h>
07 #include <atl\atlbase.h>
08
09 #include <lmcons.h>
10 #include <lmaccess.h>
11 #include <lm.h>
12 #include <sddl.h>
13
14 int main(int argc, char** argv)
15 {
16 char buf[256];
17
18 //printf("Test\n\n");
19
20 if (argc < 2) {
21 printf("Usage:lgenum2 <servername>");
22 exit(EXIT_FAILURE);
23 }
24
25 LPWSTR servername = new WCHAR[sizeof(argv[1])+1];
26
27 MultiByteToWideChar (
28 CP_ACP, // code page
29 0, // performance and mapping flags
30 (char *) argv[1], // address of character string
31 -1, // number of characters in string
32 servername, // address of buffer for new string
33 wcslen(servername) // size of buffer
34 );
35
36 wprintf(L"Multibyte to Widechar:%s\n",servername);
37 printf("-------\n\n");
38 exit(EXIT_SUCCESS);
39 }
Thanks for any help
Francis
|
|
|
|
|
fvandun wrote: LPWSTR servername = new WCHAR[sizeof(argv[1])+1];
26
27 MultiByteToWideChar (
28 CP_ACP, // code page
29 0, // performance and mapping flags
30 (char *) argv[1], // address of character string
31 -1, // number of characters in string
32 servername, // address of buffer for new string
33 wcslen(servername) // size of buffer
34 );
The above should be written as:
size_t wStrSize = strlen(argv[1] + 1);
LPWSTR servername = new WCHAR[wStrSize];
MultiByteToWideChar( CP_ACP,
MB_PRECOMPOSED,
(const char*)argv[1],
-1,
servername,
wStrSize);
That should fix your problem.
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
|
|
|
|
|
Thanks Zac,
I substituted your lines.
But now when I print my MultiByte string with wprintf, it has a lot of garbage characters at the end:
D:\Dev\CPP\Projects>t1 01234567890123456789
Test 01234567890123456789
Multibyte to Widechar:01234567890123456789▄♠n\?2?2???????????????????????????????????????????????????????????
??????????????????????????????????????????????????????????????????????????????????????---------------------------------------
Any more suggestions?
Thanks
Francis
|
|
|
|
|
Add a call to memset after the WCHAR string is created:
LPWSTR servername = new WCHAR[wStrSize];
memset(servername, 0, sizeof(WCHAR) * wStrSize);
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
|
|
|
|
|
Still no luck.
With printf statement on line 17, I get the garbage at the end:
D:\Dev\CPP\Projects>t1 0123456789012345678901234567890
Multibyte to Widechar:012345678901234567890123456789??+ s6?
...
???????????????????????????????????????\???????????????????
---------------------------------------
Without printf statement on line 17: OK
D:\Dev\CPP\Projects>t1 0123456789012345678901234567890
Multibyte to Widechar:012345678901234567890123456789
---------------------------------------
01 #pragma comment( lib, "netapi32.lib" )
02 #include <stdio.h>
03
04 #include <stdlib.h>
05 //#include <string.h>
06 #include <windows.h>
07 #include <atl\atlbase.h>
08 #include <wchar.h>
09 #include <lmcons.h>
10 #include <lmaccess.h>
11 #include <lm.h>
12 #include <sddl.h>
13
14 int main(int argc, char** argv)
15 {
16 if (argc < 2) {
17 printf("Usage:lgenum2 <servername>");
18 exit(EXIT_FAILURE);
19 }
20 size_t wStrSize = strlen(argv[1]+1);
21 //printf("");
22 //printf("Test %s,%u\n", argv[1],wStrSize);
23
24 LPWSTR servername = new WCHAR[wStrSize];
25 wmemset(servername, 0, wStrSize);
26 MultiByteToWideChar(
27 CP_ACP, // code page
28 MB_PRECOMPOSED, // performance and mapping flags
29 (const char*)argv[1], // address of character string
30 -1, // number of characters in string
31 servername, // address of buffer for new string
32 wStrSize); // size of buffer
33
36 wprintf(L"Multibyte to Widechar:%s\n",servername);
37 wprintf(L"---------------------------------------\n");
38 exit(EXIT_SUCCESS);
39 }
For completeness, here are my VC Express environment settings:
DevEnvDir=D:\Progs\VStudio8\Common7\IDE
INCLUDE=D:\Progs\VStudio8\VC\INCLUDE;D:\Progs\MsPSDK2003R2\Include;D:\Progs\MsPSDK2003R2\Include\atl;C:\sybase\OCS-12_5\include;
LIB=D:\Progs\VStudio8\VC\LIB;D:\Progs\VStudio8\SDK\v2.0\lib;D:\Progs\MsPSDK2003R2\Lib;C:\sybase\OCS-12_5\lib;
LIBPATH=C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
Path=D:\Progs\VStudio8\Common7\IDE;D:\Progs\VStudio8\VC\BIN;D:\Progs\VStudio8\Common7\Tools;D:\Progs\VStudio8\SDK\v2.0\bin;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;D:\Progs\VStudio8\VC\VCPackages;D:\Progs\EMC/lib;D:\Progs\EMC/bin;D:\Python24\.;C:\Program Files\Windows Resource Kits\Tools\;D:\oracle\product\10.2.0\client_1;D:\VERITAS\NetBackup\bin\;C:\qip;C:\qip\utils;C:\qip\lib;C:\sybase\CFG-1_0\bin;C:\sybase\OCS-12_5\dll;C:\sybase\OCS-12_5\lib3p;C:\sybase\OCS-12_5\bin;D:\Perl\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\Adaptec Shared\System;C:\Program Files\UltraEdit;D:\usr\bin;D:\usr\32-bit;D:\usr\32-bit\utils;C:\Program Files\NMapWin\\bin;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;D:\usr\reskit;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin;C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE;D:\Progs\ZipGenius 6\;D:\usr\bin;D:\Progs\EMC\VISUAL~1;C:\PROGRA~1\EMC\EMCVIS~1;C:\Program Files\UltraEdit;c:\qip\cli;D:\Progs\EMC/lib;D:\Progs\EMC/bin;D:\Python24\.;C:\Program Files\Windows Resource Kits\Tools\;D:\oracle\product\10.2.0\client_1;D:\VERITAS\NetBackup\bin\;C:\qip;C:\qip\utils;C:\qip\lib;C:\sybase\CFG-1_0\bin;C:\sybase\OCS-12_5\dll;C:\sybase\OCS-12_5\lib3p;C:\sybase\OCS-12_5\bin;D:\Perl\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\Adaptec Shared\System;C:\Program Files\UltraEdit;D:\usr\bin;D:\usr\32-bit;D:\usr\32-bit\utils;C:\Program Files\NMapWin\\bin;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;D:\usr\reskit;C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin;C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE;D:\Progs\ZipGenius 6\;D:\usr\bin;D:\Progs\EMC\VISUAL~1;C:\PROGRA~1\EMC\EMCVIS~1
VCINSTALLDIR=D:\Progs\VStudio8\VC
VS80COMNTOOLS=D:\Progs\VStudio8\Common7\Tools\
VSINSTALLDIR=D:\Progs\VStudio8
|
|
|
|
|
Do'h! Part of it was a typo on my part:
size_t wStrSize = strlen(argv[1] + 1);
should read as:
size_t wStrSize = strlen(argv[1]) + 1;
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
|
|
|
|
|
Thanks!
That did it.
Francis
|
|
|
|
|
Hi,
Can a namespace extension be installed on a limited users account? To install one only accesses the HKEY_CURRENT_USER part of the registry (as far as I remember) so does this mean that they can be installed?
Thanks in advance
Dave Kerr
codechamber@hotmail.com
http://www.codechamber.com
|
|
|
|
|
Hi there guys, I am currently trying to achieve a seemingly simple task in VC++ 2005. I have made a very simple form in Microsoft Access which I wish to serve as the beginnings of something greater. I created a db in MS Access named links.mdb containing on table-> Table1. Table1 contains 1 column, "Links", and i wish to read these strings into variables in my Visual C++ Windows Forms Application.
What I have done so far...
In Visual C++, I clicked on Data->Add new data source, and followed the wizard to add the microsoft access database to my application by the name, "linksDataSet". I can see the table in my left hand "Data Sources" pane in VC++. All I need to know is how to access my database from here so that I can read these strings stored in my table. Also, would be possible to schedule my application to log on to a http server and retrieve these links every time the application is executed? How would I go about doing this?
Thank you very much for your time
Regards
Linden.
|
|
|
|
|
the sounds like you are using managed code - are you posting in the correct forum or are really using VC++/MFC?
cje
|
|
|
|
|
Hi
Can anyone tell me the best way to obtain the windows directory and drive
thanks
Simon
|
|
|
|
|
Look up SHGetFolderPath in the documentation and use the flag 'CSIDL_WINDOWS', this will get you the path to the windows folder (typically c:\windows).
Always use SHGetFolderPath for special folders like My Documents, Program Files and so on. It's a bit of an ugly function so I'd wrap it in something a bit cleaner that returns a string.
Dave Kerr
codechamber@hotmail.com
http://www.codechamber.com
|
|
|
|
|
|
|
UINT GetWindowsDirectory(
LPTSTR lpBuffer, // buffer for Windows directory
UINT uSize // size of directory buffer
);
G_S
|
|
|
|
|
Hi:
Does anybody know of a good tutorial or getting started resource for using the "Spy++" tool that comes with Visual Studio?
I have a problem with a MFC application which I suspect may be traced if I can look at the Windows messages being shot through my application. However, every time I fire up Spy++, I end up throwing up my hands in dispare.
Specifically, I would like to know how to identify which window I should be watching from the enormous list of windows that are listed in the "Windows" window. Its not obvious and I often find that the name of my application appears embedded in three or more of the entries in the listing. Then, I would like to know how to isolate messages that are being directed to specific windows and possibly even narrow this to specific controls.
Do people find "Spy++" useful? Or are there better ways to debug problems?
Thank you,
Mark
|
|
|
|
|
Spy++ is a great tool
First of all start the application directly meaning not executing it through VC++.
Second a better approach is to list processes it is simply easier to find your exes name then open up the tree you'll see all the threads if mulitple scan the threads for the window/control your looking for
right click the window/control you want and click messages you'll see messages that window/control receives to isolate messages click on logging options on the toolbar or just click CTL+O
there you have what kind of message tracing you want.
G_S
|
|
|
|
|
Thanks G_S. I did try starting my program away from the IDE and it certainly was easier to isolate my application and also its sub-controls and lok at only the messages I was interested in.
Alas, I still have not figured out what keeps repainting my custom control...
Cheers,
Mark
|
|
|
|
|
Hi Mark,
By far the best way to debug (although this depends on preference and opinion) is to just the visual studio debugger, and step through code that you need to test line by line.
Get familiar with breakpoints and 'step in/step out' for functions. The debugger is powerful enough for you to walk through code as it is executing, line by line, make changes on the fly and compile them back into the running program. If you notice a line of code didn't work the correct way, you can change the line, compile the changes, tell the debugger to step back to that line and execute it again. You can keep on doing this until you've got the code correct.
This line by line debugging will also greatly ease your use of spy- because when you step over a line of code you'll probably only end up sending one windows message (or none at all), and you won't get the floods of mouse messages.
Try using Winspector Spy (a free tool on the net), it corrects some of the most common quibbles with spy++. In terms of using spy itself, the most useful feature is under 'Search>Find Window'. You can drag the Finder tool over the window you want to spy on and it selects it for you automatically; very useful if you need to find a window such as a statusbar which may not have a caption.
When watching windows, go to the 'logging options' and make sure you're not logging mouse messages, paint or nc (non-client) paint messages, otherwise you tend to get a continuous flood of nonsense.
So whilst watching a window you are debugging step-by-step, you can generally see what's going on. The only limitation of the step-by-step debugging is that it doesn't do windows messages well, because they go through a message pump etc which makes stepping in and out of those functions very complicated. For checking dodgy code though, the debugger should be your first check, get comfortable with it, it's an extremely powerful tool.
Hope this helps Mark
Dave Kerr
codechamber@hotmail.com
http://www.codechamber.com
|
|
|
|
|
Hi Dave:
Thanks for your response. I guess I should have been a little more specific about the kind of problem that I am having. I've been using Visual Studio for years and, yes, the line-by-line debugger, stepping in, stepping over, breakpoints and the various watch windows is always my first recourse when debugging and testing.
My problem is that I suspect that there are windows messages being issued that I am unaware of and might be working against me. Sounds like conspiracy theory, I know, but the Reader's Digest version of my problem is that I am trying to customize a control. It is user drawn. In "DrawItem", I am painting the control's background a certain colour, when I step through and view this procedure, I can see that the "DrawItem" procedure is indeed painting the background. But as soon as I allow the program to continue, some other entity is un-painting my background. I assume that this is a Windows message that I had not anticipated. This is why I would like to see what messages are being issued.
Am I correct in assuming that it is the WM_PAINT message that is eventually calling the "DrawItem" procedure? Or have I misunderstood?
Anyway, that is my story. I do not know if Spy++ would help me here or not but I have been spinning my wheels here since late last night and I am willing to try anything at this point.
Thanks,
Mark
|
|
|
|
|
Hi Mark,
OK- I thought it was a much more general question, I didn't mean to sound patronising to someone who's been using studio for years!
First things first- make sure you are handling the WM_ERASEBKGRND message and returning FALSE- otherwise during the drawing sequence the system will try and erase the control's background. This sounds like the most likely problem.
If it's more complicated custom drawing you're doing, such as list items in list controls, then look in the documentation for how to set the background. For example as far as I can remmeber with things like tree controls, to customise the tree items background, you handle the custom draw notification, but don't erase the background, you set the background colour in the passed device context to what you want, and then the system erases it for you.
So if the background is being unpainted, check for the WM_ERASEBKGRND message and make sure you handle it, and for tree/list/more complicated controls, make sure that to change the background you're setting the correct variable in the device context.
If none of this works and spy doesn't pick up any cheeky little messages being boosted around without your knowledge, then it might be worth posting the explicit problem somewhere and seeing if it's been encountered before...
Good luck,
dave
Dave Kerr
codechamber@hotmail.com
http://www.codechamber.com
|
|
|
|
|
Thanks Dave. That sounds like a likely suspect. I am not currently handling WM_ERASEBKGRND.
Cheers,
Mark
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
