|
How is it possible to send the combination of the keys to an application?
I tried using SendMessage, but no matter what i did - it always send only F1, without the CTRL being pressed.
i also tried to send KEY_DOWN of CTRL and then KEY_DOWN for F1, but it didn't work.
Is there anywhere an example that makes it work?
Thanks.
|
|
|
|
|
Try setting the lParam arg in the WM_KEYDOWN message. That lets you specify whether any auxiliary keys like Ctrl/Shift/etc are pressed.
/ravi
My new year's resolution: 2048 x 1536
Home | Articles | Freeware | Music
ravib@ravib.com
|
|
|
|
|
As i understand from MSDN, the lparam indicates the type of key - not with which key it is being pressed.
Anyway, this is not working.
|
|
|
|
|
|
Hi
i need to create a pointer which will have to be global since it will be accessed in many places in my application.
Can somehow please help since i do not know where to place the declaration of the pointer.
Thanks
Krugger
|
|
|
|
|
krugger wrote:
i need to create a pointer which will have to be global since it will be accessed in many places in my application.
Can somehow please help since i do not know where to place the declaration of the pointer.
BAD IDEA!!!
I suggest you write a pointer manager type class and access it through there, otherwise you will have to continually check the status and validity of the pointer every time before you use it. Also, if you are accessing it via multiple threads, you will have to make sure you lock and unlock it before each access. A small manager class with a Get() and Set() fcn will take care of that for you. Then wherever you need the pointer, just #include your manager header.
Also having bald pointers floating around in "global" space is just plain immoral and causes needless coupling and makes for difficult maintenance.
~Nitron.
ññòòïðïðB A
start
|
|
|
|
|
|
OK I suspect you have read Nitron's comment which is valid.
Now if you really want to do this, you have many options
a) Put your pointer in CWinApp if you use MFC
And then everywhere you need it do somehting like this
<br />
CMyApp * pApp = (CMyApp *) AfxGetApp();<br />
void * pMyPointer = pApp->GetPointer();<br />
b) Otherways
Instanciate your pointer in only one c++ file after the #include for instance
void * gpMyPointer;
Then declare your pointer into a .h file this way:
extern void * gpMyPointer;
And include this h file wherever you need it
|
|
|
|
|
If you have a MFC application, a member variable of the application class is probably the best way. Every part of your app can access it as a member of the theApp-object.
"We trained hard, but it seemed that every time we were beginning to form up into teams we would be reorganised. I was to learn later in life that we tend to meet any new situation by reorganising: and a wonderful method it can be for creating the illusion of progress, while producing confusion, inefficiency and demoralisation."
-- Caius Petronius, Roman Consul, 66 A.D.
|
|
|
|
|
In one source (your main maybe)
CMyDataTypeWhatever *g_pData = (initialization stuff?);
In all other sources
extern CMyDataTypeWhatever *g_pData;
HOWEVER, I must reiterate what others have said. Even though unmanaged global variables can be perfectly safe, if you don't know how to even declare a global variable, I doubt you have an understanding of the pitfalls.
Tim Smith
I'm going to patent thought. I have yet to see any prior art.
|
|
|
|
|
Thank you guys. It really helps!!
Krugger
|
|
|
|
|
The safe solution is use a global handle allocated with GlobalAlloc when the app starts. When you need to read or write to the global, lock it with GlobalLock and GlobalUnlock. It prevents you from simultaneous writing, which is the main pitfall of globals in multithreaded apps.
Robert-Antonio
"CRAY is the only computer, which runs an endless loop in just 4 hours"
|
|
|
|
|
When I delete a pointer, p, should I do:
A:
p = NULL;
delete p;
or
B:
delete p;
p = NULL;
~Nitron.
ññòòïðïðB A
start
|
|
|
|
|
|
I was thinkin' B coz if I set p = NULL first, delete will try to delete a *p from NULL, but the *p @ &p will still be there...
~Nitron.
ññòòïðïðB A
start
|
|
|
|
|
Nitron wrote:
I was thinkin' B coz if I set p = NULL first, delete will try to delete a *p from NULL, but the *p @ &p will still be there...
Right.
With the assignment of a new value to your pointer, you are throwing the old value away. And as this value was your only means to access (and access includes delete), you now have a memory leak.
"We trained hard, but it seemed that every time we were beginning to form up into teams we would be reorganised. I was to learn later in life that we tend to meet any new situation by reorganising: and a wonderful method it can be for creating the illusion of progress, while producing confusion, inefficiency and demoralisation."
-- Caius Petronius, Roman Consul, 66 A.D.
|
|
|
|
|
Hi folks,
I have the following problem. Window B must be child w/ respect to Window A. Window A and Window B are on different threads (by the way, A is running on the main process thread). Is it possible to make window B be child of window A in such a sitiuation? if not, how to simulate the correct behaviour, for example being notified of the messages window A receive, and so behave accordingly?
Thanx a lot. You always brighten me 
Andrea
|
|
|
|
|
Hello people,
I am a novice at MFC and I am stumped by a problem. What I have on the screen are few items and I have the ability to select multiple ones. The multiple items are shown by a tracking rectangle border. This mechanism is handled in OnLButtonDown() and LButtonUp() and OnMouseMove() event. My problem is when i just left click anywhere on the screen I want the selected items to be deselected ( this functionality works) However I have to make a call to UpdateWindow() and that causes the entire screen to be redrawn giving me screen flicker . Is there anyway I can only redraw part of the client area ? Sorry for thsi wordy email. I would really appreciate any help.
Thanks
newbee78
|
|
|
|
|
You should specify an update region prior to calling UpdateWindow so that only the part of the window that needs to be redraw is repainted. See the InvalidateRect member function. For more granualar control, you can also look at RedrawWindow, as it allows you combine these calls into one single call.
onwards and upwards...
|
|
|
|
|
Hello There,
Thank you very much. I am on my way
newbee78
|
|
|
|
|
Hi,
I intend to create a hidden ActiveX Control(it is a windowless control) on a UIThread. I tried to create the control using CWnd::CreateControl in the UIThread initInstance but got stuck in filling the parameters.
Finally the question is can an active X control object run & exist without having a dailog on a UIThread.If so how then? (some sample src codes)
Also i intend to use the message loop of the UIThread to get event notification on the control (A latter step)
|
|
|
|
|
DimpleSurana wrote:
CWnd::CreateControl in the UIThread initInstance but got stuck in filling the parameters.
It depends on how the control implements Create(), and/or if the control is derived from CWnd.
~Nitron.
ññòòïðïðB A
start
|
|
|
|
|
well the control extends CWnd
|
|
|
|
|
Then this should work:
m_Ctrl.Create( WS_CHILD|WS_VISIBLE, CRect(0,0,100,100), this, ID_SOMEID );
~Nitron.
ññòòïðïðB A
start
|
|
|
|
|
{Remember i am trying to create this control from a UIThread so a container for holding the control is missing, i am tryin to get the round about way if it exists so}
Okie i was successful in getting my code compiled with the following statement
BOOL CUIStatusThread::InitInstance()
{
// TODO: perform and per-thread initialization here
AFX_MANAGE_STATE(AfxGetStaticModuleState());
myctrl.Create("My window", WS_CHILD|WS_VISIBLE, CRect(0,0,100,100), AfxGetMainWnd(), ID_SOMEID );
return TRUE;
}
but it gives a Debug Assertion Failure in occcont.cpp Line 62 on this statement -
ASSERT(pParentWnd != NULL);
I guess this should make the picture clear for u.
dimple
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
