|
WndProc() does not get all messages. Like with MFC, PreProcessMessage() handles everything from the message loop, and only dispatches whatever is deemed necessary, to WndProc(). I have had to override PreProcessMessage() to do more fundamental window manipulation.
Also, apparently for convenience, you can call a windowed control/form's SetStyle() method with ControlStyles.EnableNotifyMessage set to true, so you can catch the WndProc messages in OnNotifyMessage(). However, it won't catch anything WndProc doesn't already get.
As for custom window styles and extended styles (WS_* and WS_EX_* stuff), which are not to be confused with control/class styles (what GetStyle() and SetStyle() deal with), you need to override the CreateParams property, and set your styles there. There is an example on the CreateParams help page.
In general, you will have to do a lot of custom drawing to achieve what you are trying to do. Main menus are normally automatically placed right below the caption, and displace the client area downwards, so you will have to roll your own. Hope some of this helps.
Cheers
|
|
|
|
|
I heared that vb.net code converted to c#.net then to
microsoft intermediate language, is this correct?
|
|
|
|
|
no, it goes direct to msil.
"When the only tool you have is a hammer, a sore thumb you will have."
|
|
|
|
|
Hello
Well i am new to C# and dont know much about it. i designed a form and tried to call it on menuitem. when i click menu item for very first time, the forms appears, but once i have closed the form and try to reclick the menu item again the error message occurs
" An unhandled exception of 'System.ObjectDisposedException' occurred in system.windows.forms.dll
Additional information: Cannot access a disposed object named "Emp"".
plz guide me in this regards
Arkr
|
|
|
|
|
Can you post the code for "menuitem" click?
Sounds like the variable is getting garbage collected between the first and second uses.
Cheers,
Simon
"The day I swan around in expensive suits is the day I hope someone puts a bullet in my head.", Chris Carter.
animation mechanics in SVG
|
|
|
|
|
Suppose EMP is the form, which i want to be appeared when menuitem is clicked, i simply create the instance of the Emp class
private Emp emp = new Emp();
and call
private void menuItem_Click (object sender, System.EventArgs e)
{ emp.Show();
}
Is it OK?
|
|
|
|
|
That should be fine.
This way, you'll have access to public methods/members of the Emp form variable.
You can also control when it should close/hide.
Cheers,
Simon
"The day I swan around in expensive suits is the day I hope someone puts a bullet in my head.", Chris Carter.
animation mechanics in SVG
|
|
|
|
|
Hello,
I am a begginer in c#. I have one textbox. In this textbox user can enter any kind of data in xml format. The xml file format can be any type. What is the simple procudure to validate the xml file entered by user. what is the easy procudure to write simple xml editor(if user types open tag it should automically display close tag) using c#.
thanks in advance,
chito
|
|
|
|
|
Does someone knows how to load a PCX Image with a library or something else?
Trully, if there evil in this world,
It lies within the heard of mankind
Shock The Dark Mage
shock@romhack.net
Main Project: Aeru IRC - http://www.sf.net/projects/aeruirc
|
|
|
|
|
Even though this applies to all .NET languages, I figured I'd ask it here since those VB.NET guys don't really get it, right guys?
Anyway, I was messing around with the managed DirectX classes the other day and got curious. I noticed in the assemblies that there's actually static methods on the assembly, not on a class. Well, this interested me so I dug deeper and saw that no external modules are P/Invoked but unmanaged code is embedded in the assembly. The only thing I can come up with is that they were written in MC++.
Then I started to wonder if the managed DirectX assemblies contained enough code to run that DX9 wasn't required. I tried it on a WinXP machine with the "factory-installed" DX8.1 and it worked! Of course, DX9-specific functionality may not work, but the basic stuff did.
So my question is, does anyone know how far back version support for the managed DirectX assemblies go, or do these contain enough information that DirectX doesn't even need to be installed. I'm kind of doubting it, but it'd be nice.
This will work great for our Web-deployed app that uses a "touchless installation", i.e. doesn't require an install. All dependent assemblies not in the GAC are downloaded automatically by Fusion, a component of .NET often overlooked. If MDX9 works this way, this paves the way for some awesome easter eggs...er, 3D object support.
"Well, I wouldn't say I've been missing it, Bob." - Peter Gibbons
|
|
|
|
|
Can anyone tell me, is there any advantage to using aximp/tlbimp for creating Interop DLLs over letting VS.NET do its stuff (by customising the toolbox to add a COM object)?
Is aximp mainly for those not using VS? Is VS using aximp to "do its stuff"?
Just wondering... what is the relationship, if any?
Paul
Pleasently caving in, I come undone - Queens of the Stone Age, No One Knows
|
|
|
|
|
aximp.exe is a simple cmdline that in the end just calls the System.Windows.Forms.Design.Aximporter.GenerateFromFile(string typelibfilename) method from the System.Design.dll namespace.
There is strictly no point in using this cmdline instead of letting VS.NET do it. After all, that's the same reason why you choose to compile C# code with the IDE instead of the cmdline.
|
|
|
|
|
Thanks SR.
This is exactly what I expected but I saw aximp mentioned in an article or two and it started to niggle at me. Figured someone here would know and I'd be able to forget all about it  .
Paul
Pleasently caving in, I come undone - Queens of the Stone Age, No One Knows
|
|
|
|
|
Actually, there's a couple reasons: overriding the default namespace, generating source code, and providing a key pair (although you can do the latter via project options in VS.NET, but it's often forgotten). It's *rare* one has to do this, but I did have to for a couple ActiveX controls that were poorly written in the first place (but we needed them...drats).
"Well, I wouldn't say I've been missing it, Bob." - Peter Gibbons
|
|
|
|
|
Exist in .NET something like WindowFromPoint ??
W.
|
|
|
|
|
[DllImport("user32.dll")]
private static extern IntPtr WindowFromPoint(Point point);
From Eric Gunnersons Win32Window library on GotDotNet.com
Who is this miscrosoft, and what devilish plans have they for us?
|
|
|
|
|
I'm sure that others have noticed this behaviour, but I have searched all over for a resolution to no avail, so I'll post it here.
When using windows XP visual styles (via manifest file) with a TabControl there are numerous display issues.
The most well-known is the fact that the TabPage background is not correctly painted with the WinXP gradient - this I actually don't care about as my tab pages are filled with either listviews or picture boxes, so the background is irrelevant. This issue has of course been addressed here on the CP already.
The major problem for me is that of you select anything other than a top alignment for your tabpages in conjunction with using winXP visual styles the tabs themselves are drawn totally messed up, along with the text on tabs mysteriously dissapearing.
The app I am developing is heavily reliant on tabcontrols, using a mixture of regular (align=top) controls, with a few left-aligned tabcontrols. Resorting the top-aligned controls throughout will simply waste far too much desktop space, so is not an option.
So here's where I'm at - it's either ditch WinXP visuals, or draw the tabs myself. I really don't want to have to resort to losing the XP look, so drawing the tabs myself is the way I'd like to go. The problem with this is that I simply cannot find an overridable method that allows me to paint the actual tabs (painting the tabpages is no problem), and at this stage the thought of writing my own TabControl from scratch is almost enough to make me turn to the drink.
Can anyone help?
|
|
|
|
|
Furty wrote:
So here's where I'm at - it's either ditch WinXP visuals, or draw the tabs myself. I really don't want to have to resort to losing the XP look, so drawing the tabs myself is the way I'd like to go. The problem with this is that I simply cannot find an overridable method that allows me to paint the actual tabs (painting the tabpages is no problem), and at this stage the thought of writing my own TabControl from scratch is almost enough to make me turn to the drink.
No dont drink! How about using the MagicLibrary's Dockin Controls. I have found the are almost a substitute for MDI forms and the TabControl.
Who is this miscrosoft, and what devilish plans have they for us?
|
|
|
|
|
Ah, come on. Drinking in moderation never hurt anyone and has even helped to churn out some interesting code form time to time. 
Just wanted to vouch for Magic. We use them a lot at work and I and my colleagues have even suggested many improvements to the author. There's not very good documentation, but after "suggesting" that every third-party control libraries "require" it and throwing the NDoc project I help with at him and offering to help with the documentation process, docs will soon be on the way.
Other than that, you can't really find a better *free* library - or even a commercial library for that matter.
"Well, I wouldn't say I've been missing it, Bob." - Peter Gibbons
|
|
|
|
|
Heath Stewart wrote:
Drinking in moderation
moderation being the keyword. A bender on Wednesday night rendered me useless till yesterday.
Heath Stewart wrote:
There's not very good documentation
I agree, was a bit difficult to gather at first, but you tend to get the hang of it.
Heath Stewart wrote:
Other than that, you can't really find a better *free* library - or even a commercial library for that matter.
I agree again  COmmercial quality for free I just wish I was a commercial programmer. 
Who is this miscrosoft, and what devilish plans have they for us?
|
|
|
|
|
About 2 hours before I posted the orginal message here I downloaded v1.71 of Magic - the problem is I really do need to have some left-aligned tabs (vertical) as well as standard tabs. The thing with the base library control is, you can specify OwnerDrawFixed, but I just can't find ouy how to actually paint the tabs..
|
|
|
|
|
Magic will do vertical tabs (note, not "left-aligned" - that has to do with text alignment). He even has an example of it in his sample application.
As far as owner drawing, you basically have to take the PaintEventArgs.Graphics property and go at it. Take a look at the System.Windows.Forms.ControlPaint class. It has a lot of helpful functions to draw things like borders and glyphs. It can simplify your UI and keep it consistent with Windows.
"Well, I wouldn't say I've been missing it, Bob." - Peter Gibbons
|
|
|
|
|
Unfortunaltely, MagicTab has a problem with focus on complicated controls. I use MagicTab, control inherited from DataGrid on it, and some inherited controls on this inherited DataGrid. Keyboard works ok, but after mouse click focus "goes" from my controls to DataGrid. May be it's my mistake, but these objects on Microsoft Tab works ok ... 
Sincerely
AW
|
|
|
|
|
Controls placed on MagicTab (instead of DataGrid) works ok.
Simplified controls (with no sub-controls on them) works ok.
Sincerely
AW
|
|
|
|
|
if you could only...code one language for the rest of your natural life...what would the language be ? ..as for me... i think C#....cause its the only one i really know lol..
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
