|
I could give one idea. But any way you are going to implementing that. So do like which you feel happy.
I think tool bar is good for that. In a tool bar if we add some check buttons we can get that environment (I think). But may not exactly like that. Or else if we need same exactly like photo shop Layers control, then I prefer we should prepare one activex control which will have two check button options and which can hold one picture and one lable. and it should have the respective events implimented. those controls need to be added to that tool bar. If you show the tool bar in vertical then the look will be same. Am I correct?
Thanks. Have a nice day. 
Nice talking to you. 
|
|
|
|
|
If I understood you correctly then this listbox[^] should be useful to you.
At least you could add some additional functionalities that you need to this control by yourself.
"Success is the ability to go from one failure to another with no loss of enthusiasm." - W.Churchill
|
|
|
|
|
Hi,Guys
I want to change my console based program into a SDI program. And I have adready make it can work.
But there is one critcal thing left, I don't know how to output the messages used to be displayed in the console to the SDI view.
Can anyone kindly give me some hint or a sample?
Thanks in advance!
|
|
|
|
|
Hello.
I think the simplest way to do it is by creating a dialog based application. (I've done the same thing myself).
For the "console", create a listbox and send the console output to it.
|
|
|
|
|
Thanks very much for your reply!!
Actually instead of listbox, I have tried to use ListView under SDI, and it works fine.
But now I want to switch to CRichEditView, and not sure if there will have some overflow problem.
Once again thanks very much!!
|
|
|
|
|
Hello.
I haven't used it, so I can't tell...
Good luck.
|
|
|
|
|
Hi,
Thanks all the same
|
|
|
|
|
You don't have to simulate it, you can create a real console window using AllocConsole(). You can get a handle to it using GetStdHandle() and then write messages using WriteConsole()
|
|
|
|
|
hi
I have the following problems while debugging an MFC application.
I am using VS 6.
1)If i set the breakpoints and debug ,in the variables window it displays the value {???} for some variables.Is it unicode or something like that?
2)Most of the values of the variables are displayed in Hexadecimal form(even though i turned it off in options of variable window ),how to see the usual integer values?
3)The flow suddenly breaks into Disassembly(which i don't understand too much).is there anyway to get around this problem?
Thanx in advance
Early to bed and early to rise,work like hell and advertise
|
|
|
|
|
1) the question mark typically means it cannot resolve the address for the variable.
2)odd, that should work.
3) breaking away from your code to disassembly typically means it is in code that is outside your program and the source is not provided elsewhere. This can happen with many runtime functions or library code. There is no way to prevent it unless you make sure you do not step edit into something that is outside of your app code.
|
|
|
|
|
Hi.
Look at the answer from douglasjordan, above. I just want to complete his answer on your 3:rd point:
If you shift window in the workspace (with ctrl-tab), then you will get back to your code. Look at the green arrowhead (or possibly the line above it). That's where your program called the function that was shown i assembler.
|
|
|
|
|
Further on the third point, you should have an option to display the Call Stack in a window (most likely View->Debug->Call Stack, or Alt-V,D,C). The current level will be highlighted. Trace down the call stack to the first routine that you recognize, and double-click there. This should pop up a window with your source code so that you can see where the offending call is being made.
The nice thing about the call stack is that you can display different variables in the Watch Window, depending on where you are in the call stack. As you double-click to display a function at various levels in the Call Stack, Visual Studio reverts to that function's context, so you can display local variables.
The Call Stack window also shows the parameters that are passed to functions, so you can see if something was sent that "broke" stuff.
Bob Ciora
|
|
|
|
|
I am working with a dialog based application having 9 (nine) edit field arranged in 3X3 matrix form. The dialog is also having three buttons (OK, Cancel and Process). I want the program do as follows:
1. When the user presses an arrow key (left, right, up and down) while in any edit field the focus should move to desired edit field only (not to OK or any other button)
2. Capture the keboard input (like ALT, CTRL etc. to be processed diffrently when in the focus is in edit field).
I came to know that dialogs with buttons and any other controls cannot capture keyboard input. Is it true?
Please help.
pani
|
|
|
|
|
By using CreateDialog this is fairly simple from a c based app that has a message loop dispatcher - you merely intercept the desired messages and call the dlgproc directly versus dispatching it to the message que where the default handler will take care of them and not forward. It will not be easy from a c++ class based app without access to the message dispatcher.
|
|
|
|
|
I am using (not very seasoned in) VC++6 and MFC to create the dialog based application.
Pani
|
|
|
|
|
You can override PreTanslateMessage in the Dialog class...
Inside which you can check for the desired message.
Eg:
if(pMsg->message == WM_KEYDOWN)
{
if(pMsg->wParam == VK_UP)
{
//TODO:
//Logic to set the focus
}
}
For the keys like Control,you can get the state by using GetKeyState function
Eg:
if((GetKeyState(VK_CONTROL) & 0x8000)
{
//TODO:
}
|
|
|
|
|
Thanks!
It worked fine.
Pani
|
|
|
|
|
Thanks for the vote 
|
|
|
|
|
pani68 wrote: 1. When the user presses an arrow key (left, right, up and down) while in any edit field the focus should move to desired edit field only (not to OK or any other button)
2. Capture the keboard input (like ALT, CTRL etc. to be processed diffrently when in the focus is in edit field).
What about handlling WM_CHAR Notification
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
Sorry. It doesn't work.
Pani
|
|
|
|
|
pani68 wrote: Sorry. It doesn't work.
No probs, But Dreamz already correctlty answered your question
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
Hi,
I use Windows XP.
I created a new desktop named desktop2, switched to it using SwitchDesktop API and created a explorer process there using CreateProcess API.
Everything is fine, but the windows shortcut key is not working in the new desktop. If I use Win+E to get the explorer, explorer opens in the default desktop, not in the new one.
What can I do to get rid of this problem?
Thank you.
- NS -
|
|
|
|
|
I have this code:
DWORD dwFlags = OFN_HIDEREADONLY | OFN_OVERWRITEPROMPT;<br />
static char BASED_CODE szFilter [] = _T("All Files (*.*)|*.*||");<br />
CFileDialog dlg (false, _T(".*"), _T(""), dwFlags, szFilter, (CWnd *) this, sizeof(OPENFILENAME));<br />
<br />
if (dlg.DoModal() == IDOK) {<br />
}
For some reason, when it reaches the DoModal, it bails without showing a dialog and I used the GetDlgExtendedError function to find out and it throws an error called CDERR_DIALOGFAILURE which says
The dialog box could not be created. The common dialog box function's call to the DialogBox function failed. For example, this error occurs if the common dialog box call specifies an invalid window handle.
I use these same file dialogs elsewhere in the same project and copied and pasted the code and the those dialogs work fine, but this one refuses. I can step through and the window handle is indeed invalid but I don't know why. I'm doing it the exact same here as I am in the other location but it doesn't work here for some reason. Is the problem in front of my face and I am just not seeing what's wrong?
|
|
|
|
|
If you've copied the same code snippet and it works everywhere else, then ponder what's different. The "this" pointer you're passing...is "this" actually a window derivative? The error messsage suggests that this might be the problem, though, it doesn't state it with certainty.
You may want to try a Debug build, linking MFC in a static library, and stepping directly into the CFileDialog code. If I couldn't figure the problem out by analysis, then this is what I'd do. Step through MFC until the error is generated.
Bob Ciora
|
|
|
|
|
You found my error, the troubled code was in my document class which isn't based off of CWnd. I knew I had to have done something wrong since I triggered a debug assertion but I only got that generic error so I didn't know. I'm kicking myself that I didn't calmly examine what was actually different between the two, I was too frustrated with the error to think rationally. I just changed NULL'd the pointer and it works fine, thanks.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
