I've the same problem in Firefox. The quick red ProgramFOX jumps right over the Lazy<Dog>. My latest article: Understand how bitwise operators work (C# and VB.NET examples) My group: C# Programmers Group

Band-Aid.

Most start-ups in Silicon Valley used to do that till the issue of liability (in case an employee crashed into someone else on the way home) came up.

That's part of the reason I switched to Linux on the desktop - tools. It's not that tools are better, it's that they are smaller, more focused and simpler, and you achieve more complex tasks by combining several of them, and since each brick is very good and polished, the resulting construction is so too. This yields IMO a better user experience for developers and power users - they can perform more complex tasks easier than in Windows.

Noticing it for the first time on my phone... It sure works a lot better for a mobile device like this!

It's from the Old English "sceaphierde", or a "guard of sheep". However the language changes as you know: are you suggesting that Public Servants do their work publicly, or that they act like our servants rather than masters? :) Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water

Fortunately the adult supervision where I work are all former hardware engineers, so we won't have any of that software nonsense any time in the near future. Software Zen: delete this;

I've been called on for being demanding before :D Good UI is hard, and no framework is perfect. I certainly haven't found any that I'd proudly recommend. However, this doesn't change that a lot of MFC's design decisions are still stuck in the past, and that makes it harder. That's not the problem. I don't see a way how to "modernize" MFC (in terms of tools like resource editor and wizard, resource handling, and general we-could-do-this-for-you-ness.) -- at least not without losing a large part of backwards compatibility. Which would also suck. While I still use MFC for application framework (i.e. pulling up a main window and a dialog), everything else I write happily with a collection of rather simple routines and a subclassing library I'm fairly proud of*. For chewing through the tricky details of a form, MFC gives me claustrophobia (and ATL/WTL feels unwieldy, somehow). Joe Woodbury wrote: The recent changes to MFC were extremely poorly designed and implemented Ack! I didn't have any experience with BCG, and when I first toyed around with it for the first time, I felt like poking my eyes out. It fits the theme of window-dressed neglect, as you describe. To clarify: I'd still love to see a "better MFC" over a completely new framework. There's just so much baggage in MFC that I don't see that happening from a technical stance. (E.g. throwing out the BGC detour would probably alienate to many users.) *) FWIW, the basic ideas are: augment Windows API, don't replace it. A "Message Handler" can handle multiple messages from multiple windows, and each window can have multiple of those message handlers. Oh, and it lives as long as either one of the windows exists, or you have a reference to it. FILETIME to time_t | FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy

That's great! :laugh: It's an OO world. public class Naerling : Lazy<Person>{ public void DoWork(){ throw new NotImplementedException(); } }

Thanks. It's one of those you either get in a few seconds or not. About a year ago, I got 3 CCCs in a couple of weeks, and haven't got close to one since. Cheers, Peter Software rusts. Simon Stephenson, ca 1994.

I play some "soothing nature sounds" or Hip-hop music.

Thanks very much for this - really useful insight. As developers intellectual property law and copyright is probably the area we're most likely to run into legal quagmires so it's helpful to canvas people's experience on this - good luck if you do build that new version! My Blog: http://www.dwmkerr.com

I agree, I only use regions to group the logical blocks of items inside of a class. I.e Private fields, properties, ctor, methods. This is especially useful inside a large class with multiple properties + methods. You should never use regions inside a method, and many refactoring tools such as Stylecop and ReSharper, actually prevent it.

I received a message asking 'Why' which I think has been deleted. The why is that I would like to present the resources from an exe or dll, but also show the resources in any modules that are loaded. So for example, if you wanted the icons in the windows picture and fax viewer, you see that the process is explorer.exe, but it doesn't contain the resources, it's the shimgvw.dll (from memory) module that contains the resources - so in some cases a recursive search would be useful.

That's great, thanks!

DaveKerr wrote: so as I understand it, I can use Activator.CreateInstance to get the COM object, but I cannot use reflection You can, as long as the component supports IDispatch you can use the CustomMarshaller assembly (you'll commonly find it in c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727). The following code sample displays the members of DirControl.DirList.8.0 using reflection: using System; using System.Collections.Generic; using System.Text; using System.Runtime.InteropServices; using System.Runtime.InteropServices.CustomMarshalers; using System.Reflection; namespace ComMarshaller { [ ComImport, Guid("00020400-0000-0000-C000-000000000046"), InterfaceType(ComInterfaceType.InterfaceIsIUnknown) ] public interface IDispatch { void Reserved(); [PreserveSig] int GetTypeInfo(uint nInfo, int lcid, [MarshalAs( UnmanagedType.CustomMarshaler, MarshalTypeRef = typeof(TypeToTypeInfoMarshaler))] out Type typeInfo); } class Program { static void Main(string[] args) { Type type = Type.GetTypeFromProgID("DirControl.DirList.8.0"); object o = Activator.CreateInstance(type); IDispatch disp = o as IDispatch; if (disp != null) { Type tp = null; disp.GetTypeInfo(0, 0, out tp); MemberInfo[] mi = tp.GetMembers(); foreach (MemberInfo minfo in mi) { Console.WriteLine(minfo.Name); } } Console.WriteLine("Done"); Console.ReadKey(); } } } Remember, this needs CustomMarshaller.dll added as a reference in your application. "WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes. My blog | My articles | MoXAML PowerToys | Onyx

Aren't Group Boxes actually Statics, not Buttons? That should help you a little, but I don't have answers for the others.

You could use the CWnd::Detach method to detach the existing CWnd object and then use CWnd::Attach on the returned window handle to attach your CDialog derived class. «_Superman_» I love work. It gives me something to do between weekends.

Please clear you question :confused: