I don't see in your job description where worrying about fellow employee is your action item. Is there some way that you can clearly delineate between your responsibilities and his? Your tasks and his? Or is this a situation where you think some aspect of DNS (for example) should be done a certain way, reasonable people could differ, and you are making an issue of it unnecessarily? If there is that much difference between you guys, and his and your responsibilities are clear cut, then the results should be evident. If it's not affecting the company all that much, and as long as you're not actually working overtime doing his stuff as well as yours, and the company wants to be charitable to some guy, then is that your business?

in your DLLMain myBitmap = LoadBitmap( hInstance , MAKEINTRESOURCE( IDB_MY_BITMAP); and in your control class, or wherever you need it, do an extern HBITMAP myBitmap; There may be other ways.

Math 5:28 Jesus said if you even look on a woman with lust in your heart you have committed adultery. Elsewhere: "treat the young women as sisters, with absolute purity" Job said "I have made a covenant with my eyes not to look upon a maid [again, with lust]" Colin- there are a zillion places, literally. So the bad news is, we are all adulterers, to one degree or another. The situation is not magically solved by marriage - only new problems occur. Marvin should thank God for his biology. Frankly, I'm more concerned that he's going to a bible study every night. I hope this isn't the International Church of Christ. Maybe Marvin could read Proverbs 5 & 6. Possibly some workbook from Navigators or Intervarsity might be good. (Possibly Jerry Bridges?) Hey, if your Italian car causes you to stumble, take the bus!

http://www.starstonesoftware.com/OpenGL/images/willcode.gif photo of lead author of OpenGL SuperBible :laugh: :laugh: :laugh: :((

here's what I did, but we didn't run this production yet 1) construct one line of valid xml 2) write it to text file , flush buffer This produced a text file that resembled xml, but missing the top-level node. To display it in a web page, I pre-pended a top-level node ( < TOP > ) , and appended a closing node name ( < / TOP > ), and this worked. I think one possible advantage is that it is super fast and simple to write a line of text, and then you can take care of the leading and trailing niceties later when you display the file. Also, this approach ignores the DOM entirely. It is only straight C text files at the time of logging. :rolleyes:

you know, I've had so much trouble with path syntax and checking if GetNode type statements returned null or not, that I started putting together my own short list of XML "stuff", but it hasn't really evolved into a useful tutorial. The hardest thing for me is still that "I just want to get data out like it was Access or a *.ini file, or a flat file", and the XML DOM sometimes seems to make what should be easy , difficult. (once it works it is fantastic) Your tutorial was very helpful to me and my current project - I started out attempting something like what was in C++ Journal in the January issue , where I specify all the structs/variables for our project in XML, and then I generate the C++ code from that, I generate the C++ code in to read all the variables and populate the structs from the XML file, I change an MFC dialog on the fly to get or set variables in the data in my config screen. I started thinking at the beginning - here I have these different ways of formatting what is essentially the same data - I have C++ code, I have *.h include files, I need *.ini files, I need to edit my MFC dialog - why can't I just feed it all off the XML and use that to unify these various data structures? I got it working, but explaining it to our engineers has got me to back off from trying to force them to use the generating features. But it is still very handy to have C++ code plus the min/max validation data, the comments that explain what that variable is, the list of potential values, etc. all in one place. Someday somebody is going to make some money by providing a tool where we can specify data in XML, because when a guy creates a new variable, if he knows what the max/min values are to be, wouldn't be great if he could spell all that out in one place, and then it would be useable in his program, and all the other developers were doing the same thing, and multiple variables weren't created for the same purpose, etc. Oh well, sorry for the long text. I could not live without the tutorials at CodeGuru and CodeProject (at least as a Windows/MFC developer). Your tutorial was very easy to understand and helpful. :laugh:

here are two great links for beginning DOM programming in C++: http://codeguru.earthweb.com/xml/XMLDOMFromVC.html - a basic, great tutorial microsoft http://msdn.microsoft.com/Downloads/samples/Internet/ select xml, and I think the MFC tree control is the XMLTree simple application.

as a first point, why not follow Joseph Newcomer's advice and never use GetDlgItem (or at least, not again this year). Create a member variable in class wizard to go with your control. He has an article about that on this site. That might take care of all your problems, if we're lucky.:)

thanks much, good demo, it does apply, and the comments below it were helpful too.

thanks much I'm using MSXML v4 (current) the quoted text is working . . . although come to think of it, I always use BSTR's when convering from CStrings (doing this in MFC) xslt transformation - I have not yet had the courage to do that in C++ code About stepping throught the list . . . actually, what I am trying to do is very,very similar to the MSDN example where they recursed through a node set and displayed all the nodes in a CTreeCtrl . . . maybe I'll go back and try to figure out the recursion that needs to be done. If I can recurse through the node tree and keep track of which nodes are child to which, it might be less complicated than I am making it.

I'm generating some C code from XML, and now I want to generate sub Structs. I know I can do the following (a child node of same name as parent node), value value But what I'm having problems with is getting the top-level structs with SelectNodes, and then getting sub-level structs with SelectNodes (or other select commands). I've been doing things like: //StructList = xDB->m_pDomDocument->getElementsByTagName("Struct"); StructList = xDB->m_pDomDocument->selectNodes("//Struct"); and have not gotten lucky yet. X|

I wish we could rate these posts like you can at CodeGuru - what a helpful post!:laugh:

hey Paul, check out www.LewRockwell.com sometime. You might like the guy from Zimbabwe who writes for them - he appears about every 2 weeks or so.

I've been inserting the reference project into the new project, then dragging and dropping the resources into the new project. (and then break the link) One cool thing is that it seems to copy whatever bitmaps, etc that you need as well. I'm not even sure why it works, but it's slick. You have to join projects, though. You can break them apart later. --------------------------------------------------------------------------------- I wish I had a way to have multiple *.rc files for a project - when we are using Visual Source Safe, one guy wants to change his dialog somewhere, but he has to check out the main rc file, and it locks us all out of it. (and he leaves it checked out and we are stuck for a while) I started playing around with doing #include's into the resource file to let us split it up, but didn't get too far.

hey, you'd probably like http://www.joko.sn/archalbum.html try Youssou Ndour and Baba Maal Lord knows I can't dance (to it or anything else), but it's pretty uplifting . . . :laugh:

for pure gui's, Borland Builder is SO easy to use, especially compared to MFC (like I hate all these cute CButton classes, ColoredBUtton classes, resizeable dialog classes that I am using from Code Project - actually I love them and am deeply grateful to the guys for providing them, but all that stuff is trivial in Borland. What value is it to my business that it takes a day to make a button colored? Why not use an easier tool? I don't care that it goes through VCL, as long as it works. But I've never convinced a client to use Borland instead of MFC, and I've not used it much for database work, and will defer to the opinions of the other user who'd had tons of trouble with Active X, database connectivity, and debugging in general. I had stuck with the pure-vcl stuff, and it was always so easy to do threads, display AVI's , do sound, do controls (that work intuitively without grief). Maybe your boss would find VB more appealing - for quick gui development, VB is great. Borland is $50 for the student edition - would be worth the try.:rolleyes:

check this out http://asktheheadhunter.com/crocs.htm He thinks Dice is worthless. (he also thinks resumes are next to worthless, believe it or not. That hasn't been my experience.)

there's some licensing you can do - for example, the MSHFlexGrid (in Visual Studio etc) is a licensed control - there is a special procedure that must be gone through to use it on a machine that does not have VB or Visual Studio installed. I don't know how to license a control, but I do have experience with this particular control and the hoops we had to do to get it to work. (on a pc that had not had the licensing procedure run, it displays as a blank box)

I've been doing either this (in InitDialog) [ccode] BOOL returnCode = SetWindowPos( this->GetActiveWindow(), 0, 0, ::GetSystemMetrics(SM_CXMAXIMIZED), ::GetSystemMetrics(SM_CYMAXIMIZED), SWP_SHOWWINDOW); [/ccode] or this: [ccode] CRect rect; rect.top = 0; rect.left = 0; rect.right = ::GetSystemMetrics(SM_CXMAXIMIZED); rect.bottom = ::GetSystemMetrics(SM_CXMAXIMIZED); this->GetActiveWindow()->MoveWindow(rect,TRUE); [/ccode] If you do anything with OnSize, remember that it is called twice - once before InitDialog, and then again after InitDialog, and you can't move controls until InitDialog runs because they don't exit yet. (you didn't ask this, and I think I'm telling it correctly. You might also be interested in the EasySize class for moving dialog controls around as you resize a dialog - it is very helpful. (search this site if you are interested)