|
The code is correct at first glance --a perfect way of having references to default constructed images. The only possible error I can think of is that the copy constructor of CImage might be buggy. I'd recommend checking this ctor out.
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
Hello,
the development of my "ReSysInfo" System Information Viewer has finished. Now I need many many beta-testers.
Download the beta from:
http://home.tiscali.de/reichl/download/resysinfo_setup.exe[^]
Even if you don't find any bug, I would like to know on which system it has been tested (perhaps send me a compressed generated system report?)
Thank you all in advance!
-Dominik
|
|
|
|
|
m_pszProfileName is set by MFC's APPINIT.CPP to the filename
by which the application was invoked. If the application was
started via a short path name (using GetShortPathName), such
as must be fairly common when passing the filename on command
lines, the application will use the incorrect registry key.
I use SetRegistryKey in my app's OnInitInstance and nothing
else. So now I've got buggy programs. Should I have done
something else? oh.. wait. I just looked. Right, I'm missing
AFX_IDS_APP_TITLE in the string table which MFC uses to reset
m_pszAppName to the correct application name--- which in turn
causes pszProfileName to get later get set correctly.
ARG, I those hidden chains of effects drive me crazy.
Oh well. I guess I'll still hit submit on this....
|
|
|
|
|
Help
How can i open the Serialport or RS232 with Visual C++?
Is there a MFC Class?
Thanks
|
|
|
|
|
Use CreateFile API function. Refer to MSDN for more information.
A. Riazi
|
|
|
|
|
Hi,
I implemented some button class, were I want the buttons face to display like the parent windows background, which in turn is not a solid colour but a colour gradient.
How can I get the parent windows background at the position of the button?
Have I to save it in a bitmap before the creation of the button?
Thanks for help in advance
Thomas
|
|
|
|
|
If you implement buttons with transparent feature (style) all of things handled automatically by windows. In other hand Windows will paint transparent faces without any effort from you.
A. Riazi
|
|
|
|
|
I am sorry, but I tried to use WS_EX_TRANSPARENT style for the button control but it did not work.
|
|
|
|
|
I've got the following prototype:
afx_msg void OnPvcsCtxtEditfile(HTREEITEM hNodeIn = NULL);
However, calling the function from my context menu, I get a bogus value for hNodeIn.
It has a NULL value if I call the function from elsewhere without an argument, but I guess when its called via messaging a value gets set along with it.
Is there anyway I can keep this from happening without adding a function to handle the context menu message that simply recalls the real one?
Thanks
BW
"Gandalf. Yes. That is what they used to call me. Gandalf the Grey. *I* am Gandalf the White."
- Gandalf the White
|
|
|
|
|
brianwelsch wrote:
Is there anyway I can keep this from happening without adding a function to handle the context menu message that simply recalls the real one?
You can add another default parameter,
bool bCalledFromSomewhereElse = true
And then when you post the message, post with false, and handle it accordingly.
- Nitron
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
|
|
|
|
|
Unfortunately as the afx_msg type functions are used through MACRO's and function pointers that have to conform to a prototype you can't define a default value for them. I am surprised you don;t get a horible crash with what you have. Looks like you will have to do it in 2 stages.
Roger Allen
Sonork 100.10016
WHats brown and sticky?
A stick or some smelly stuff!
|
|
|
|
|
Roger Allen wrote:
I am surprised you don;t get a horible crash with what you have
It crashes inside the function, when I try to access that tree item.
Roger Allen wrote:
Looks like you will have to do it in 2 stages.
oh well.
thanks for your help
BW
"Gandalf. Yes. That is what they used to call me. Gandalf the Grey. *I* am Gandalf the White."
- Gandalf the White
|
|
|
|
|
I am getting the following error in afxconv.h:
c:\program files\microsoft visual studio\vc98\mfc\include\afxconv.h(22) : error C2146: syntax error : missing ';' before identifier 'AfxDevModeA2W'
c:\program files\microsoft visual studio\vc98\mfc\include\afxconv.h(22) : fatal error C1004: unexpected end of file found
The error is here:
#ifdef _WINGDI_
LPDEVMODEW AFXAPI AfxDevModeA2W(LPDEVMODEW lpDevModeW, LPDEVMODEA lpDevModeA);
LPDEVMODEA AFXAPI AfxDevModeW2A(LPDEVMODEA lpDevModeA, LPDEVMODEW lpDevModeW);
LPTEXTMETRICW AFXAPI AfxTextMetricA2W(LPTEXTMETRICW lptmW, LPTEXTMETRICA lptmA);
LPTEXTMETRICA AFXAPI AfxTextMetricW2A(LPTEXTMETRICA lptmA, LPTEXTMETRICW lptmW);
I am usinf MFC in a shared DLL with a console app. I have MFC working with CString and all that fun stuff. The problem arises when I #include <afxtempl.h> .
If it's any help, I am trying to integrate CMarkup with my program. The demo project compiles and works fine.
Any advice will help!
Thx!
- Nitron
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
|
|
|
|
|
Take alook at the file which is including the header, you may be missing the ; there.
Roger Allen
Sonork 100.10016
WHats brown and sticky?
A stick or some smelly stuff!
|
|
|
|
|
IT WAS THE LOCATION OF THE Markup.h HEADER FILE!!!!!!!!
I put Markup.cpp and Markup.h in a subdirectory called "xml".
I added the path to my project settings, and it didn't complain. After 4 hours of this, I thought... "lets try to move the files up a directory"
Is it time to go home yet?!?!?!?!!?
- Nitron
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
|
|
|
|
|
My app is a non-MFC .exe file (it opens a dialog box and then do stuff...) and i would like it to act as an activex component for IE.
I've created a CLSID and stored the correct info in the registry. It seems to work fine except for one thing: when the app is downloaded on the first time, everything works fine. But after that, when the app is run from the previoulsy downloaded version, the app launches correctly but IE seems to freeze for about 30 seconds.
Anyone has an idea where this comes from ?
...DaMP...
|
|
|
|
|
Hy,
I ported a small application from Visual C++ 6 to .NET and now on some computers it crashes when it shows a "Save" dialog.
The problem is that i've tried it on about 10 computers and only on 2 of them crashed, on the others works perfectly.
The OS on the "crash" comptuer is NT4 with Service Pack 6.
I was wondering if anybody knows what's happening or heard of similar situations. I've heard of similar problems, but don't know any real answer, so any help is really welcomed.
Thanx in advance.
|
|
|
|
|
OK. I have an application icon that is 32x32 pixels and has 16 million color depth. I open the icon in Visual Studio 6 (and .NET) and it doesn't look correct. I understand that Visual Studio can't edit high color icons, however I need to have these icons displayed on the caption bar of a dialog based application, as well as in a ListView. I tried using LoadIcon to display this correctly and it doesn't work.
By the way, I am trying to displayt his high color icon transparently. The icon in the caption bar has an orange background when its supposed to be transparent. Apparently the LoadIcon only works with 256 color icon images.
Anyone have any suggestions?
Regards,
Brigg Thorp
Software Engineer
Timex Corporation
|
|
|
|
|
Did you look here[^]?
That may help.
- Nitron
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
|
|
|
|
|
I saw this, but I don't think it will help with the caption bar of a dialog based application. I thought Windows XP handled drawing these icons automatically, and would dither them down to the right image if that size/bit depth was not present in the .ico file.
Is there a standard MFC call that will set the icon for the application like the SetIcon call in MFC?
Brigg Thorp
Software Engineer
Timex Corporation
|
|
|
|
|
Don't use LoadIcon() . LoadIcon() is a hold-over from the 16 color 32x32 Win3.1 days. Use LoadImage() .
Also, unless you have rather large title bars, you may wish to use a 16x16 icon. If the 32x32 image is used in the listview, then keep that too. Once again, LoadImage() is smarter about this.
Finally, keep in mind that 24bit color icons occasionally cause problems on systems prior to WinXP - 256 colors are usually enough for such a small image, and work on all versions.
---
Shog9
I see the way the salesmen stare into the sun
I stood and watched them as they fell off one by one...
|
|
|
|
|
Is there away for me to create a function with the same name and the program calls my API instead of the windows API.
Thanks
|
|
|
|
|
Anthony9887 wrote:
Is there away for me to create a function with the same name and the program calls my API instead of the windows API.
I don't think this would be very good practice. Put your similar function in a seperate namespace and access it that way.
i.e.:
instead of the program calling:
::OpenFile(lpFN,lpOpBuf,uStyle);
You would call:
YourNamespace::OpenFile(lpFN,lpOpBuf,uStyle);
- Nitron
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
|
|
|
|
|
Hi,
to make a socket closed gracefully, I set the SO_LINGER on and call shutdown() before closesocket(). But the MSDN said The shutdown function does not block regardless of the SO_LINGER setting on the socket.
does it mean no unsent data will be sent when shutdown() with SD_SEND flag?
Thanks.
Kerry Chou
|
|
|
|
|
My version of MSDN reads for shutdown:
If the how parameter is SD_SEND, subsequent calls to the send function are disallowed. For TCP sockets, a FIN will be sent after all data is sent and acknowledged by the receiver.
To me this says that every send call that has succeeded up to this point is indeed transmitted to the destination.
What even more confirms this is a later section reading:
To assure that all data is sent and received on a connected socket before it is closed, an application should use shutdown to close connection before calling closesocket.
The fact that the call does not block might simply mean it's asynchronous.
|
|
|
|