When the function returns, the 'size' variable will have a numeric value the size of the data stored to the buffer. If you ever use something like this in a loop, you need to remember to reset the variable to the size of your buffer before calling RegQueryValue each time. It is sometimes easy to overlook the [in, out] specification on a parameter :doh:

Mike Danberg wrote: As far as the problem with the third tab error, you can't access a control on the other tab. It's exactly the same as having a dialog that's not open yet. The control isn't there, so you can't access it. Hope that helps. Can't really tell you much more since I don't know exactly what you're doing. Well....I was trying to find a way to make sure the dialog "was there" so I could access the control. Here's more on the problem (fixed now btw) just for information...I couldn't post a code snippet as it is a work project (IP and all that crapola ya know). It is a power pnael interface for a test station and one tab is a "health monitor" and the two other are two seperate "power" panels for powering up power supplies. The health monitor needs to inactivate monitor controls for power supplies that are not powered. the logic was there for them to safely not run, but I wanted to make the controls visibly disabled to show that they weren't evens selectable while power supplies were not powered up (checkboxes). However, OnSetActivate() was just the trick I needed (and didn't know). I overrode that function and now when that tab is pressed (instead of during the other tab's processing), I can deactivate the controls. Thanks. :) There are only 10 types of people in this world....those that understand binary, and those that do not.

Are you making any calls to ShowWindow(), or does the dialog template have the WS_MINIMIZE style? "When I was born I was so surprised that I didn't talk for a year and a half." - Gracie Allen

KingTermite wrote: hang on..moving window now in my way).... LOL - brilliant. And you're welcome :-) Christian I have drunk the cool-aid and found it wan and bitter. - Chris Maunder

Yes, I did read the documentation, the problem is that Microsoft documentation isn't always as solid as it could be. Once you've "done it", then you see in retrospect how to "do it", but that doesn't mean the documentation just explains every nuance. Far from it usually. That was why I said up front that I knew it was possible if I inherited the class, but wanted to make sure there wasn't a proprety or something like that I was missing. I'll keep that in mind about the ildasm.exe....I remember you showing me that on the COM DLL problem I had last week. There are only 10 types of people in this world....those that understand binary, and those that do not.

Ok...I got it (what a pain)! I want to post the answer here for posterity in case somebody else has a similar problem in the future. For the record, I found the answer in a book a co-worker lent me (COM and .NET Interoperability by Andrew Troelsen). The VB function signature: Public Function MyFunction(varNames() As String) As String() showed up as this in the assembly like this: .method public hidebysig newslot virtual instance string[] marshal( safearray bstr) MyFunction([in][out] string[]& marshal( safearray bstr) varNames) runtime managed internalcall { .custom instance void [mscorlib]System.Runtime.InteropServices.DispIdAttribute::.ctor(int32) = ( 01 00 15 00 03 60 00 00 ) // .....`.. .override COMInterface._COMClass::MyFunction } // end of method COMClass::MyFunction The problem was this assembly (and intellisense) was telling it it had to be a safearray and apparently it just wouldn't take a string[]! Not even if it was instantiated on initializaation like: string[] varNames = new string[] {"One", "Two" }; The intellisense was telling me it had to be a "System.Array", not a string[]! What needs to be done is not a "cast", but intantiating a System.Array and set it equal to the string array that was initialized and then pass in the ref to that array. This was the way to get it working was: COMInterface.COMObj oCOMObject = new COMInterface.COMObj(); string[] sNames = new string[] { "ProjectName" }; // 1 element array System.Array oTemp = sNames; string[] sValues = new string[1]; System.Array oTempVals = sValues; oTempVals = oCOMObject.TheCOMFunction( ref oTemp ); It wasn't intuitive....but now, in retrospect, it makes sense. Apparently you have to use the "System.Array" type for the "safearray" that it expects in the assembly, and since it doens't like you to cast it from string[] to System.Array, you have to just create an instance and set it equal. There are only 10 types of people in this world....those that understand binary, and those that do not.

You never said bolded dates - those are different from selected dates, hence even the different property names. If you had specified that before, I could've told you immediately; of course, if you had looked at the class members like I mentioned you should do before - i.e., read the documentation - it should'be been obvious. There is a big difference between bolded and selected dates, though. -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

Christian Graus wrote: Glad it worked out, I've worked out something too. I'm in the C# forum, not the ASP.NET forum. You therefore are probably working on a GUI app and you have no aspx files, no HTML. Sorry, my bad. Yes, its a C# app....I guess that is why no aspx files. :) Christian Graus wrote: Just out of curiosity, is this app for internal use only ? If not, why are you using C#, does your target audience all have the .NET runtime, or will you only distribute on CD, or do you consider the business lost to people unwilling to download the runtime to be negligible ? This will be an internally used app, so distributing the .Net runtime will not be an issue in this case. If the computers don't already have it, the runtime will be included with the install eventually. Our company does primarily embedded software and test software for host computers to test that embedded software. So we don't have mass produced PC software....so that's never been an issue for us. We sell the entire test sets, computer and all....so if we develop something in .Net, then the software, framework and all will already be on the computer when it is sold to the customer as a "test set". This allows us to develop, as long as customer has not dictated something special, in whatever environment/language we want (although 90% is currently in C/C++ right now). We have just a few groups that are trying to get a little more cutting edge and trying to bring some new technologies into the arena. There are only 10 types of people in this world....those that understand binary, and those that do not.

Ok...I believe I solved the problem...thought I'd post it back to the group in case it may enlighten anyone else someday. BE CAREFUL your workspace (dsw) files do not become corrupted. Unfortunately, VS doesn't seem to detect and/or warn you of "weird" dsw file. I had hdd problems last week and aparently the dsw file got corrupted. Since these workspace files go back and forth from computer to computer (whichever one I'm on) via version control system, it was giving the problem on whichever computer I was at. I deleted and started a new workspace and all is back to normal. Files load up as they should now. There are only 10 types of people in this world....those that understand binary, and those that do not.

Yes, it was going to be shared by more than one exe. We talked at more length with the designer of some other code (drivers) being used which was part of the reason we thought we needed it in a seperate DLL anyway. It turns out the restrictions were not as deep as we thought and we can stick with the static libraries we already have for the monitors. Thanks for the input all, regardless. There are only 10 types of people in this world....those that understand binary, and those that do not.

Check this, it's probably not exactly what you are looking for but pretty close. Give it a shot: Your first C# control[^] -Nick Parker

No wrapper necessary. I'd like to just them as they are...just in the DLL. The static libs are fine as they are...I'd just like to have open one time, in one instance in memory instead of building them in to every test program I'm going to write which uses them. Appreciate your advice. There are only 10 types of people in this world....those that understand binary, and those that do not.

I just finished Tom Archer's Inside C#[^] and I thought it was a great read. It covered basic OO design concepts, and how they apply to the C# language. Great for beginners, and has enough substance for an intermediate-type guy like myself. Definitely worth a look... -Mike Zinni "No shit it's tough. If it wasn't, everybody and their sister would be an engineer and then you wouldn't have a job."

In VS.NET, it's at Edit, Advanced, Untabify selection. Software Zen: delete this;

Nobody seemed to know, but I was able to figure it out with a little help from this article right here at Code Project: http://www.codeproject.com/cs/menu/MenuImage.asp I am reposting my DrawItem as it is now to show the correct way to do so in case anyone else runs into the same question. // DrawItem override for the AddSmiley context menu item owner draw private void DrawAddSmileyMenuItem(object sender, System.Windows.Forms.DrawItemEventArgs e) { MenuItem mi = (MenuItem)sender; // Default menu font Font menuFont = SystemInformation.MenuFont ; SolidBrush menuBrush = null ; // Determine menu brush for painting if ( mi.Enabled == false ) { // disabled text menuBrush = new SolidBrush( SystemColors.GrayText ) ; } else { if ( (e.State & DrawItemState.Selected) != 0) { // Text color when selected (highlighted) menuBrush = new SolidBrush( SystemColors.HighlightText ) ; } else

Windows Forms (at least in .NET 1.0) does not allow that. You'll need to use a library such as Lutz Roeder's CommandBar for .NET[^]. Cheers, Arun

For finer control over richtext, you can serialize the contents to a file or string and then parse it individually using the RT file format, you can get the format from wotsit[^] - Kannan