|
I'm doing some dialogs in Visual Stupido.NET, and I can't seem to find a way to may a simple etched frame. I don't want divider lines, and I don't want captioned group boxes. I want what I used to be able to do in Visual C++ 6.0's resource editor.
Does anyone know if what I want to do is even possible?
So far, I'm not impressed with this new crap from MS...
------- sig starts
"I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
|
Hi everybody.
I'm writing an Activex, that it interact with the serial com, sending commands.
Thats ok.
But I have two questions:
First, I like to know how to adjust the size of the control when someone put it in a form, (in VB or in a Dialog in C++). 'Cause in OnDraw() I draw a BMP, but I want to fix it to an especific size and disabled sizing. I want to fix the size for the desing time, because the control is not visible at runtime.
Then, how can I show a tip, (a short description), in the Property window, (in the bottom of the window) when a property is selected. Where I should write that description in the Activex project??.
Thank you.
Demian.
|
|
|
|
|
can't you handle the WM_SIZE message and just set it back to whatever your size is?
If it's broken, I probably did it
bdiamond
|
|
|
|
|
Greetings,
I have been using dialog based MFC apps for a while and just noticed that, at least in my applications, the exit codes aren't always 0 (even when things seem to be working correctly otherwise.)
If I run any of my dialog apps from the debugger in VS 6.0, and I then close the app with either System->Close, Alt-F4, or the 'X', I see the following messages:
The thread 0xBF4 has exited with code 2 (0x2).<br />
The program 'C:\Documents and Settings\justin.cooke\My Documents\MyProjects\randomNumGen\Debug\randomNumGen.exe' has exited with code 2 (0x2).
If I instead close it with the OK or Cancel buttons, the exit codes are 0, as expected.
What's going on? Does the 2 code just indicate how the app was closed? I was always under the impression that a code other than 0 indicated an error. I tried to find a list of what these codes mean in MSDN and online, but had no luck.
Thanks,
Justin
|
|
|
|
|
Justin Cooke wrote:
I was always under the impression that a code other than 0 indicated an error.
That's a hold-over from the DOS days. Read the docs for CDialog::EndDialog().
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
OK. I've already taken a look at that info. I understand any int can be returned. How do I know what 2 means? In this case, I'm guessing it just means OnClose was called, but how do I know for sure? Is there a list of return codes somewhere? When I'm running with the debugger and I see nonzero codes, how can I tell if they indicate errors?
Thanks for your help,
Justin
|
|
|
|
|
Look in winuser.h, about 3/4 of the way down.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
Thread and process exit codes have no inherent meaning, the code is just a DWORD that can be used for any purpose. As the other poster said, not every app will exit with 0; and if you see a nonzero exit code it doesn't imply an error happened.
--Mike--
Personal stuff:: Ericahist | Homepage
Shareware stuff:: 1ClickPicGrabber | RightClick-Encrypt
CP stuff:: CP SearchBar v2.0.2 | C++ Forum FAQ
----
You cannot truly appreciate Dilbert unless you've read it in the original Klingon.
|
|
|
|
|
OK. Thanks for the info guys. I'll just stop wondering what a nonzero return means, unless I have another reason to suspect a problem.
Thanks Again,
Justin
|
|
|
|
|
Is there a way we can give Windows XP look and feel to applications running under other operating systems beside Windows XP?
|
|
|
|
|
I belive if you have a manifest file and the version of Windows has the newer common controls file you can give it the XP look.
- Aaron
|
|
|
|
|
Only by drawing all the controls and windows yourself.
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke
|
|
|
|
|
I suppose you mean Windows OS's. Take a look at WindowBlinds[^], maybe it fits what you need.
If you want XP look and feel for programs you have the source code, you already are on the right place.
...Plug & Pray... 
|
|
|
|
|
You have to write Custom Manifest file for that!
here is link to achieve same
http://www.codeproject.com/cpp/AddXpStyle.asp[^]
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
|
|
|
|
|
Hello,
I've used code similar to the one written by the author of http://www.codeproject.com/docking/toolbarcombo.asp, I place a combobox at a toolbar, everything works great untill I set the style of the toolbar to flat, and then, when the buttons are set to be 32x32 I see the separator under my combobox. Any suggestions or ideas on how to get rid of that separator?
Thanks in Advance,
D.
|
|
|
|
|
the question has already been asked on the suggestion forum... we're waiting for chris maunder's response...
TOXCCT >>> GEII power
|
|
|
|
|
And when are we expecting to get response from Chris Maunder? 
|
|
|
|
|
|
I think that you misunderstood something, I've provided a URL for the toolbar that I'm talking about, and I think that it doesent deal with Chris Maunder at all.
Greetz,
D.
|
|
|
|
|
from the code of original author :
if (!m_wndToolBar.CreateEx(this, TBSTYLE_FLAT, WS_CHILD | WS_VISIBLE | CBRS_TOP
| CBRS_GRIPPER | CBRS_TOOLTIPS | CBRS_FLYBY | CBRS_SIZE_DYNAMIC) ||
!m_wndToolBar.LoadToolBar(IDR_MAINFRAME))
know toolbar has been set to the style of flat,
in addition, m_wndToolBar.SetButtonInfo(nIndex, ID_COMBO, TBBS_SEPARATOR, 255);
know the combox control's syle is separator,in fact ,when you set that button in toolbar :below 32*32,also exist separator,only not obviously,
because the style is set such that,if you dont want that you can chage the style
|
|
|
|
|
Thanks for the reply!
Well, my point is that I don't want to change the style (I've to keep the TBSTYLE_FLAT) and still to get rid of that separator in 32x32 TB Buttons.
Is this possible or not?
Thanks!
|
|
|
|
|
Does anybody know how to enable the windowless activation in VC6 CDialogs?
The problem: My activex control uses windowless activation to draw bitmaps with transparency. Now I've placed two of these activex controls in the activex test container app so that they are overlapping. The result is as wanted: The first control is visible through the transparency of the second control. Inside a MFC app, the overlapping region is just clipping.
I've read, that VC6 isn't supporting windowless activation. Is that right and how can I fix this?
Please help me out...
|
|
|
|
|
Hi guys I've found that a child window send a WM_PARENTSNOTIFY when a Right click is received only if the control is not defined WS_EX_NOPARENTNOTIFY but by default all the controls are defined WS_EX_NOPARENTNOTIFY.
DO you have an example how to define a control not WS_EX_NOPARENTNOTIFY ?
Best Regards
Doc
|
|
|
|
|
This requires basic knowledge of binary operations, AND, OR, XOR and one's complement.
To remove the WS_EX_NOPARENTNOTIFY style, you must specify a DWORD containing all the extended styles you want for your child control, then passing the DWORD as the first parameter of CreateEx() call. For a list of extended styles, either read them from the 'winuser.h' file in the Platform SDK, or visit MSDN in this link.
Alternatively, you can create the control, then request for it's extended styles through GetWindowLong( hwnd, GWL_EXSTYLE ) (Win32) or CWnd::GetExStyle (MFC). Both will return the DWORD of the extended style bit field. You can then use any operations in the following list to change the styles:
To toggle a flag (if enabled -> disable, if disabled -> enable), use exclusive-OR as in dwExStyle ^= WS_EX_NOPARENTNOTIFY.
To always disable a style flag, use AND and one's complement as in dwExStyle &= ~WS_EX_NOPARENTNOTIFY.
To always enable a style flag, use inclusive-OR as in dwExStyle |= WS_EX_NOPARENTNOTIFY.
Probably the 'AND and one's complement' requires a bit more clarification ?
Well, first, one's complement is an operation that inverts a bit sequence. Consider a sequence called '00010000'. Using one's complement on this would result '11101111'. Basically, all 1's become 0's and vice versa. Now, the WS_EX_NOPARENTNOTIFY is precisely a sequence like this: lots of zeros, and a single 1 somewhere. Using one's complement on it will result an inverse bit sequence (lots of 1's and a single zero somewhere).
If you AND this with the original style flag, the original bit field (style flag) will dictate the result for every other flag EXCEPT for the WS_EX_NOPARENTNOTIFY. As the second operand (one's complement of WS_EX_NOPARENTNOTIFY) of the AND operation has a 0 there, the result will always be 0 for that flag, no matter what the original bit field's value was. All other flags in the field are left as they were. If they were 0, they remain 0, if they were 1, they remain 1. This happens because the second operand has all other bits as 1's.
Hope this will help.
-Antti Keskinen
----------------------------------------------
The definition of impossible is strictly dependant
on what we think is possible.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
