|
Hi,
I have a problem with the COleDateTime class. I have no idea how to do subtraction and addition for two COleDateTime objects. I am used to the VB type of time and date addition and subtraction. Is there a way to do subtraction and addition as in VB date/time?
By the way is there an equalvalent date/time method in VC that is similar to the one in VB?
Your help is greatly appreciated. 
leonwoo
|
|
|
|
|
Look at the COleDateTimeSpan class and operators +,-,+= and -= defined in COleDateTime.
Tomasz Sowinski -- http://www.shooltz.com
*** Si fractum non sit, noli id reficere. ***
|
|
|
|
|
Im using dinput.h's GetDeviceState to retrieve the
current mouse cursor position.
Why do I get coordinates returned in the billions???
I get the same result using ints and longs for x&y.
All I want are pixel coordinates within the
range of my window app.
Any help would be much appreciated
Thanks,
Rob
|
|
|
|
|
Says MSDN-
> The mouse is a relative-axis device, so the absolute axis positions for mouse axes are simply accumulated relative motion. Therefore, the value of the absolute axis position is not meaningful except in comparison with other absolute axis positions.
Why don't you just handle WM_MOUSEMOVE events instead? Potentially with a SetCapture() first.
Signature space for rent. Apply by email to....
|
|
|
|
|
As far as I know, GetCursorPos() works very well, this gets your position in screen coordinates, you can use ScreenToClient() after that.
Romeo JUNCU
|
|
|
|
|
hi,
the template was not recognized, in my MFC DLL.
typedef struct
{
CString name;
int age;
}MYSTRUCT;
CList<MYSTRUCT,MYSTRUCT&> myList;
what's wrong then?
Extreme programming. Do the No.1
|
|
|
|
|
I believe you must export your struct from your extension dll. Use AFX_EXT_CLASS macro
Best regards,
Alexandru Savescu
|
|
|
|
|
I've created a dialog based multithreaded application in VC++ 6.0. The problem is that, whenever i close my application in "release" build, the memory error appears. I am unable to discover the problem because this error is not appearing in debug build. Can any one suggest me something ???
The error i am getting in release build while closing application is:
The instruction at "0x004165a3 referenced at 0x00000078. The meemory could not be "read"
|
|
|
|
|
http://www.codeproject.com/debug/
or more precisely:
http://www.codeproject.com/debug/survivereleasever.asp
Papa
while (TRUE)
Papa.WillLove ( Bebe ) ;
|
|
|
|
|
I had a very similar experience. In my case, I forgot to fill the iSubItem field of a LVITEM structure. In debug mode, this field is filled with 0xcccccccc or something, but in release builds, it's filled with whatever happens to reside in that memorylocation previously...
If it's not a LVITEM struct, check if you aren't forgetting to initialise a variable somewhere. An overlooked boolean can be enough to crash the program... (happened to me 4 days ago...)
I used this to find the bug:
extern void SendToDebugFile(const char* comment,bool bNew=false)<br />
{<br />
FILE* f;<br />
if(bNew)
f=fopen("Debug.txt","w");<br />
else
f=fopen("Debug.txt","a");<br />
if(f)<br />
{
fprintf(f,"%s\n",comment);<br />
fclose(f);<br />
}<br />
};
Just call this function at specific locations:
SendToDebugFile("Start of function",true);<br />
...<br />
SendToDebugFile("Marker 1");<br />
...<br />
SendToDebugFile("Marker 2");<br />
...<br />
SendToDebugFile("End of function");
The bug will occur between the last marker in the file and the next one. Zoom in on it with more markers.
|
|
|
|
|
You could even rewrite the TRACE macro so it would expand into a call to SendToDebugFile in release builds!
BTW, statements in ASSERT or TRACE macros that gets expanded into void in release builds is a common source of release-doesn't-work bugs. Another is incorrect signatures of message handlers (if you use VC++6.0).
Cheers
Steen.
"To claim that computer games influence children is ridiculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"
|
|
|
|
|
Why not redirect the standard output (stdout) streaming in a file (output.txt)...
For that, add a Program argument:
=> in your projects setting (in release mode)
=> tab "Debug"
=> category "general"
=> and Program argument = ">output.txt 2>&1"
Now you can use printf("All what you want\n") for debugging your app and the output.txt file catch your stream...
Hello World!!! 
from Raphaël
|
|
|
|
|
|
Create new configuration based on Release, but enable debug info generation on C++ and Link tabs of Settings dialog. Execute the program under debugger, try to reproduce error and check the call stack when program crashes.
Tomasz Sowinski -- http://www.shooltz.com
*** Si fractum non sit, noli id reficere. ***
|
|
|
|
|
Hi!!
I've created a dialog based application (Multithreaded)in VC++ 7.0. I've only used MFC thread and CFile clases in this application. After linking this application in Release mode, the size of exe found to be 210 KB.
Is there any way we can reduce the size of MFC apps.???
|
|
|
|
|
http://www.microsoft.com/msj/defaulttop.asp?page=/msj/archive/S572.htm
contains good info though
Papa
while (TRUE)
Papa.WillLove ( Bebe ) ;
|
|
|
|
|
 I have an Access database for students
and want to get record on paper for one student redirected (sent) to
MS Word
can anybody suggest how to do this
|
|
|
|
|
CComvariant var;
CCombstr bstr;
How to convert this var to c-style string safely.Any macro is there.Pl also tell me for converting from bstr to c-style string.
|
|
|
|
|
Actually Mike and Nish have wrote an article which "probably" answers that very question...
Index page...check it out... 
http://www.codeproject.com/string/CPPStringGuide2.asp[^]
Cheers!
"An expert is someone who has made all the mistakes in his or her field" - Niels Bohr
|
|
|
|
|
There are some ATL conversion macros declared in ATLCONV.h.
You will need to declare USES_CONVERSION; in the function that will be using the conversion macros. THis macro declares a few variables on the stack.
Then you can use OLE2T(bstr) to convert your bstr to your C-Style string. There are a slew of macros to convert from (A)Ansi to (W)widechar, to (bstr)bstr including (c)constants and whatever else. The convention is to use the format that you are going from like (A)ansi then a 2 followed by the format converting to like a (BSTR)bstr. Your final macro would be A2BSTR().
Good Luck
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!
|
|
|
|
|
Hi!
I am creating a dialog with the Create member function.
So, I would like to change the window styles (like WS_CAPTION, WS_CHILD, ...) before or after creating the dialog!
I want to do like something:
CMyDlg dlg;
dlg.???(...);
dlg.Create(CMyDlg::IDD);
dlg.???(...);
dlg.ShowWindow(SW_SHOW);
How can I change the window styles, before or after creating the dialog and display it on the screen?
Daniel 
---------------------------
Never change a running system!
|
|
|
|
|
Daniel S. wrote:
How can I change the window styles, before or after creating the dialog and display it on the screen?
I don't think you can change the dialog windows styles before creating it...but you could do it during creation using CreateIndirect() or after using SetClassLong() with GCL_STYLE as a parameter. If my memory serves me correctly and you like doing things the hard way (like me somtimes) you could prolly initialize a WNDCLASS with all the desired WS_??? styles and the call CreateWindowEx() and them somehow the following...
MSDN:
The CreateDialog function uses the CreateWindowEx function to create the dialog box. CreateDialog then sends a WM_INITDIALOG message (and a WM_SETFONT message if the template specifies the DS_SETFONT style) to the dialog box procedure. The function displays the dialog box if the template specifies the WS_VISIBLE style. Finally, CreateDialog returns the window handle to the dialog box.
Just some suggestions... 
Cheers!
"An expert is someone who has made all the mistakes in his or her field" - Niels Bohr
|
|
|
|
|
Use the ModifyStyle and ModifyStyleex member functions.
The first parameter is the styles that you would like to remove from the window, the second parameter is the style that you would like to add, and the third parameter is related to if you changed a style that affects the borders of the window.
Look in MSDN for more details.
Good Luck.
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!
|
|
|
|
|
In my experience, some things don't work with ModifyStyle and ModifyStyleEx.
For example, making the title bar like a toolbar works whereas completely removing it doesn't. The bizzare thing is that for the latter, the window behaves (when you click on it with a mouse) as though the title bar does not exist even when it is still visible (in W2k anyway?!)
it drove me nuts!
Adam.
www.beachwizard.com/travelogue[^]
"I spent a lot of my money on booze, birds and fast cars. The rest I just squandered"
George Best.
|
|
|
|
|
<code>
include "stdafx.h"
#include <iostream.h>
#include <windows.h>
#include <tchar.h>
#define ErrorHandler(s) _ErrorHandler(s, __FILE__, __LINE__)
void _ErrorHandler(LPCSTR lpszLocation, LPCTSTR lpszSrcFile, UINT nSrcLine)
{
LPVOID lpMsgBuf;
DWORD dwError = GetLastError();
FormatMessageA(
FORMAT_MESSAGE_ALLOCATE_BUFFER |
FORMAT_MESSAGE_FROM_SYSTEM |
FORMAT_MESSAGE_IGNORE_INSERTS,
NULL,
dwError,
MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT), // Default language
(LPSTR) &lpMsgBuf,
0,
NULL );
// Process any inserts in lpMsgBuf.
cout<<"ERROR @ "<<lpszLocation<<" : "<<'('<<dwError<<')'<<(LPCSTR)lpMsgBuf;
cout<<"SOURCE @ Line = "<<nSrcLine<<", File = "<<lpszSrcFile<<'\n';
// Free the buffer.
LocalFree( lpMsgBuf );
}
BOOL SetFileOwner(LPCTSTR lpszFileName, LPCSTR lpszAccount, LPCSTR lpszGroup)
{
PSECURITY_DESCRIPTOR pSD;
PSID pSID, pSIDGroup;
DWORD cbSID = 1024;
LPSTR lpszDomain;
DWORD cchDomainName = 80;
PSID_NAME_USE psnuType;
// Initialize a security descriptor.
pSD = (PSECURITY_DESCRIPTOR) LocalAlloc(LPTR,
SECURITY_DESCRIPTOR_MIN_LENGTH); // defined in WINNT.H
if (pSD == NULL) {
ErrorHandler("LocalAlloc");
goto Cleanup;
}
if (!InitializeSecurityDescriptor(pSD,
SECURITY_DESCRIPTOR_REVISION)) { // defined in WINNT.H
ErrorHandler("InitializeSecurityDescriptor");
goto Cleanup;
}
// Retrieve the SID for User.
pSID = (PSID) LocalAlloc(LPTR, cbSID);
psnuType = (PSID_NAME_USE) LocalAlloc(LPTR, 1024);
lpszDomain = (LPSTR) LocalAlloc(LPTR, cchDomainName);
if (pSID == NULL || psnuType == NULL ||
lpszDomain == NULL) {
ErrorHandler("LocalAlloc");
goto Cleanup;
}
if (!LookupAccountName((LPSTR) NULL, // local name
lpszAccount,
pSID,
&cbSID,
lpszDomain,
&cchDomainName,
psnuType)) {
ErrorHandler("LookupAccountName");
goto Cleanup;
}
if (!IsValidSid(pSID))
{
ErrorHandler("IsValidSid");
goto Cleanup;
}
// Sets the owner to the SD
if (!SetSecurityDescriptorOwner(pSD, pSID, FALSE)) { // not a default SID
ErrorHandler("SetSecurityDescriptorOwner");
goto Cleanup;
}
// Retrieve the SID for Group.
cbSID = 1024;
pSIDGroup = (PSID) LocalAlloc(LPTR, cbSID);
if (pSIDGroup == NULL) {
ErrorHandler("LocalAlloc");
goto Cleanup;
}
if (!LookupAccountName((LPSTR) NULL, // local name
lpszGroup,
pSIDGroup,
&cbSID,
lpszDomain,
&cchDomainName,
psnuType)) {
pSIDGroup = (PSID)LocalReAlloc((HLOCAL) pSIDGroup, cbSID, LPTR);
lpszDomain = (LPSTR) LocalReAlloc((HLOCAL) lpszDomain, cchDomainName, LPTR);
if (pSIDGroup == NULL || lpszDomain == NULL) {
ErrorHandler("LocalReAlloc");
goto Cleanup;
}
if (!LookupAccountName((LPSTR) NULL, // local name
lpszGroup,
pSIDGroup,
&cbSID,
lpszDomain,
&cchDomainName,
psnuType)) {
ErrorHandler("LookupAccountName");
goto Cleanup;
}
}
if (!IsValidSid(pSIDGroup))
{
ErrorHandler("IsValidSid");
goto Cleanup;
}
// Sets the group to the SD
if (!SetSecurityDescriptorGroup(pSD, pSIDGroup, FALSE)) { // not a default SID
ErrorHandler("SetSecurityDescriptorGroup");
goto Cleanup;
}
// Use the new SD as the file's security info.
if (!SetFileSecurity(lpszFileName, OWNER_SECURITY_INFORMATION | GROUP_SECURITY_INFORMATION, pSD)) {
ErrorHandler("SetFileSecurity");
goto Cleanup;
}
return TRUE;
Cleanup:
FreeSid(pSID);
FreeSid(pSIDGroup);
if(pSD != NULL)
LocalFree((HLOCAL) pSD);
if(psnuType != NULL)
LocalFree((HLOCAL) psnuType);
if(lpszDomain != NULL)
LocalFree((HLOCAL) lpszDomain);
return FALSE;
}
int _tmain(int argc, TCHAR *argv[], TCHAR *envp[])
{
if (argc < 4) {
cout<<"ERROR @ main : Not enough parameters\n";
return 0;
}
TCHAR tszFileName[MAX_PATH];
char szUserName[256];
char szGroupName[256];
_tcscpy(tszFileName, argv[1]);
#if defined(_UNICODE) || defined(UNICODE)
if (!WideCharToMultiByte(CP_ACP, 0, argv[2], -1, szUserName, 256, NULL, NULL)) {
ErrorHandler("WideCharToMultiByte");
return 0;
}
if (!WideCharToMultiByte(CP_ACP, 0, argv[3], -1, szGroupName, 256, NULL, NULL)) {
ErrorHandler("WideCharToMultiByte");
return 0;
}
#else
strcpy(szUserName, argv[2]);
strcpy(szGroupName, argv[3]);
#endif
if (!SetFileOwner(tszFileName, szUserName, szGroupName)) {
cout<<"Operation Failed!\n";
return 0;
}
cout<<"Operation Succeeded!\n";
return 0;
}
</code>
=======================================================================
This program can set file and dir owner for "administrator"
or "administrators", but can't set for other user, else return
the "ERROR_INVALID_OWNER(1703L)"...
Why??? Please help me ~!!!
=======================================================================
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
