|
x^=y;
y^=x;
x^=y;
Yes, it's cute, but it's faster to use a temporary. The xor method is only useful if you're doing it in assembly language and you don't have a free register or a temporary memory location.
ken@kasajian.com / www.kasajian.com
|
|
|
|
|
int x=150;
int y=45;
x=x+y;(195)
y=x-y;(150)
x=x-y;(45)
|
|
|
|
|
x = 15
y =13
x=x + y (15 + 13) = 28
y = x- y (28-13) = 15
x = x-y(28-15)
x = 13
Hence x=13;
y=15.
jigar sheth
|
|
|
|
|
hello guys.....im new to this. I wanna know that how can I get started with waveInOpen?? I am getting confused. What is the right path to get used to it. I just can not be happy taking samples from Internet, I must learn it but not taking it on the big picture, what is the right place.......plz plz help me.
|
|
|
|
|
|
Hi,
i m taking help of this article for design outlook style
Outlookbar-style menu interface[^]
i m using COutlook2Ctrl::OCL_SELECT for trigger with assign Menu Item,in menu item this is disable by CCmdUI,
but please tell me how can i disable this purticular subitem in this outlook tree.
please help me for this.
thanks in advance.
|
|
|
|
|
Generally,singleton pattern is applied by the way that the ctor is private and gives a member funtion named getInstance, but CWinApp's instance is defined as a global object,its ctor is not private.So how MFC realizes the singleton pattern for CWinApp?
|
|
|
|
|
The CWinApp class is not a singleton class.
It doesn't need to be because MFC needs this class has to be created before it internally calls WinMain .
If it was designed as a singleton, you would be able to create it only after WinMain in called and also you would need to write WinMain yourself.
That is why you create a global instance of it and you must create only one as the documentation says.
This is as easy as saying that you can only have one main or WinMain function.
|
|
|
|
|
I Made a test .If i instance another global CWinApp descendant class.In release mode ,there is only one instance in the application ,but not two.How does MFC keep only one CWinApp descendant instance in the application?
|
|
|
|
|
This works in Release mode because the ASSERT macro has no effect in Release mode.
MFC maintains several global functions whose begin with Afx and several global variables whose names begin with _afx .
These are the variables that are used to invoke the various methods in the code.
These variables will be overwritten by the second instance of CWinApp .
So only the last instance of CWinApp will be the valid object.
All the rest will simply occupy space in memory.
|
|
|
|
|
wonderful!I got it ,thank you!
|
|
|
|
|
I recently created a driver installation program, which uses a number of core functions such as UpdateDriverforPlugAndDevice(), using vs2008, in 32-bit operating system everything is working properly. But win32 program can run in x64, but under x64 it does not work. For example UpdateDriverForPlugandPlayDevices() raises an error, I used GetLastError (), and I see an error code. Later I was using a 64-bit system with vs2008 and compiled the x64 program, everything works fine, but the program can not run in win32. The problem is now solved, but I now maintain two versions of the installer 32 and 64; I do not know what a better way, I just run a seperate version of the executable.
|
|
|
|
|
When 32-bit apps try to access certain folders or registry keys in a 64-bit environment, they will be redirected to another path.
For example, drivers are normally copied to C:\Windows\System32\drivers .
When a 32-bit app tries to copy a driver to this location, it will redirected to C:\Windows\SysWOW64\drivers .
This is probably what is going on in you case and so you will have to maintain 2 separate versions of your installer program.
|
|
|
|
|
I get a crash on a Windows Message!
Looked it up in WinUser.h and didn't find anything for it.
This is the MSG number 274.
As it appears when I press close on my Window, my program is receiving a WM_SYSCOMMAND.
This is totally a new thing, I already have a WM_CLOSE.
Can't understand what is triggering it.
modified on Wednesday, July 21, 2010 9:04 PM
|
|
|
|
|
WM_CLOSE is not the last message that an application will receive.
This is normal.
But why is that causing a crash for you?
Perhaps, you could debug after it crashes.
|
|
|
|
|
kindly let us know,Is crash is appearing in Debug Mode or release mode!
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow Never mind - my own stupidity is the source of every "problem" - Mixture
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
Support CRY- Child Relief and You
|
|
|
|
|
I ran code analysis on my project.
It told me I had a memory leak.
I have a Linked List class with an Add function.
The Add function receives parameters, then it creates a node and fills it with those parameters.
I can't understand why their is a leak!
|
|
|
|
|
ok, but how do you remove items from the list ? is it done automatically by the list class destructor ?
Watched code never compiles.
|
|
|
|
|
|
This may sound like a daft couple of questions...
- Are you sure the memory leak is in your class? Try swapping it for one that you know doesn't leak like std::list and run your analysis again.
- Why on earth are you writing your own linked list? std::list will probably do as good a job in most cases.
Ash
|
|
|
|
|
Aescleal wrote: - Why on earth are you writing your own linked list?
Academia.
"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
|
|
|
|
|
Hi all,
I have a problem to set correctly the color background of a CTabCtrl under Windows XP. IT work great under Vista/Seven. But XP still not working after many try.
So you can see 2 print screen (one in Vista and one in XP) you will see that the one on XP don't paint correctly the background windows (right beside the last tab).
http://www.devntic.com/IMAGES/PrintSreenVista.jpg[^]
http://www.devntic.com/IMAGES/printscreenXP.JPG[^]
this is my code to do what you see in these print screen..
I have a Class to manage CTabCtrl --> in this case COnglet (it's Tab in french)
BOOL COnglet::OnEraseBkgnd(CDC* pDC)
{
RECT rect;
this->GetWindowRect(&rect);
::FillRect(pDC->GetSafeHdc(), &rect, static_cast<HBRUSH>(((CDlg_Modele*)m_TabOnglet[0]->ptrEcran)->m_DlgBGColor));
return FALSE;
}
void COnglet::DrawItem(LPDRAWITEMSTRUCT lpDrawItemStruct)
{
CRect rect = lpDrawItemStruct->rcItem;
rect.top += ::GetSystemMetrics(SM_CYEDGE);
....
...
pDC->SetBkMode(TRANSPARENT);
pDC->FillSolidRect(rect, ((CDlg_Modele*)m_TabOnglet[0]->ptrEcran)->m_bgColor);
...
...
pDC->RestoreDC(nSavedDC);
}
Thanks in advance for any help you could provide to me
regard Etienne
PS: sorry, my english is not perfect.
modified on Wednesday, July 21, 2010 3:18 PM
|
|
|
|
|
I gave the class an English sounding name, et voilà
BOOL CMyTabCtrl::OnEraseBkgnd(CDC* pDC)
{
RECT rect;
this->GetWindowRect(&rect);
ScreenToClient(&rect);
::FillRect(pDC->GetSafeHdc(), &rect, static_cast<HBRUSH>(((CDlg_Modele*)m_TabOnglet[0]->ptrEcran)->m_DlgBGColor));
return FALSE;
}
I strongly suggest that you give identifiers English names, unless a customer demands another language in a contract. And even then, try to convince him before accepting.
A simple thing as asking for help might reduce your chances of getting a good response. But there are better reasons, working with developers from different countries being one. Going public with parts of your code being another. I once had an interface file for a complex system completely in Dutch in my hands. Oh my oh my...
|
|
|
|
|
Was it Dutch, Dutch++ or maybe Dutch#?
> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> "It doesn't work, fix it" does not qualify as a bug report. <
> Amazing what new features none of the programmers working on the project ever heard of you can learn about when reading what the marketing guys wrote about it. <
|
|
|
|
|
I'm glad you see the problem
|
|
|
|