In case your PO are new to scrum too, they'll be happy with anything you can provide them with. The introduction on wikipedia is quite nice and will provide enough material for half an hour or so :-D As Scrum is based on the Agile development methodology, a good excuse might be that it encourages thinking of and improving the development process while development is under way - so it don't have to be perfect at the start.

If they happen to know the theory, they are worth a lot - even if they don't know how to use a keyboard. One can use such people to extend his own knowledge and get new ideas. If they are only good at self-marketing, one can even learn from that! :) One can't learn anything from arrogant folks, though.

Thank you for the info!

Hi, please don't hit me for mentioning MS Word. I was wondering if there was any master document / export script combination (that creates acceptable HTML output) available which could be used for writing articles. Does anybody use such a thing? If no, how do you do the automated spell checking?

Ok, it just happened again. :( If I had written an auto-updating tool I'm proud of I probably would like it to run as often as possible. Also they may have business goals (such as 3 updates per week) to ensure the effort put into the updater was worth it. :-D

Hi, can anybody point me in a good direction on how this template works? I have not had any luck with the microsoft and boost documentations on this. I thought it may be used to detect class interface members as in Interface Detection[^], at least that is what I take from the name. Many thanks!

You must redirect the CWinApp application data storage from the registry to your ini file. See the MSDN documentation on CWinApp::m_pszRegistryKey and CWinApp::m_pszProfileName. By freeing m_pszRegistryKey and setting m_pszProfileName to an appropiate path you will be able to use CWinApp::GetProfileString CWinApp::GetProfileInt CWinApp::WriteProfileInt CWinApp::WriteProfileString on an ini file instead of the registry. When I switched my application to use an .ini file, this took me a while to find out. However, it's not likely we are the first people to face this issue ... there must be an example somewhere. :~

I guess with seekg you are looking for the position -1 from the end. Therefore you are missing the byte. Additionally look here: http://www.codeproject.com/KB/files/filesize.aspx[^] http://www.cplusplus.com/reference/iostream/istream/seekg.html[^]

Hi, I got similar code in one of my projects, there are two differences that may be of importance: 1) I always apply pXMLDoc->put_async(VARIANT_FALSE) to the IXMLDOMDocument's. Probaby you have to check if the documents are fully loaded before you operate on them otherwise. 2) When calling transformNodeToObject(...), I don't give the document pointer but a node pointer as argument:

IXMLDOMElement* pElemInterface = NULL;
pXMLDoc->get_documentElement(&pElemInterface);

IXMLDOMNode* pNodeInterface = NULL;
pElemInterface->QueryInterface(IID_IXMLDOMNode, (void **)&pNodeInterface);
pElemInterface->Release();

pXMLDoc->transformNodeToObject( pNodeInterface, vOutput );

It has been a while since I coded that so I can only guess there should have been a reason for this. In VBS, using the document directly works fine. Hope that helps ;)

No, that would be a Kibibyte.

This can be fixed easily: #define false true There ya go ...

I dont think it should not crash at all unless you are trying to access or invoke any members of ref. (Though its technically very unlikely ;) to have an object at address 0x00 - its just an address like any other).

Hi Henri, I was faced with a similar question some time ago and decided to use CFileFind(er?) and put the results into a ListBox. That seemed to be the simplest approach because I only wanted to select a file from a list anyway. Regards, Andreas

I wrote a test application (the code works in VC++ 8, and i stays 0 in VC#), but it seems that I had a mental blockade to enter i = i++; It took me two i = i+1; until I could force my fingers to do that. Is the result really undefined by ANSI or whoevers specification?

Well, I don't create XSLTs on a daily basis, only once a month. Each time I have to go back to look at already created ones to see how to do it. It just doesn't seem natural to me, especially dealing with variables and parameters. When I look at XSLTs in bigger projects that have been worked on for a while (by other people) - it makes XSL to look like a self-obfuscating language. People tend to put the whole application into one file (doesn't matter if it got 10.000 lines), do not properly group things, use copy & paste and the rest is done by the overhead of tags and symbols through XML. It makes me think XSL is generally treated as throw-away code, like prototypes going into production.

From time to time it is necessary for me to code xslt. Each time is a horror. the horror the horror

Have you looked at CListCtrl::GetItemRect(...)?

Hi, I'm not exactly sure why you are using wchar_t (*me2_ptr)[14] = &me; and its equivalent for the int. However, look at things like this: me2_ptr - is a pointer on a pointer on a wchar_t *me2_ptr - is a pointer on a wchar_t **me2_ptr - is a wchar_t pval - is a pointer on a pointer on a int *pval - is a pointer on a int **pval is a int If you call operator<< on a pointer on a wchar_t it assumes its target is a c-string and delivers the string itself. If you call operator<< on a pointer on a int it just delivers the value of the pointer. This is just the way operator<< is implemented.

Hi, this one is for the MFC aces: I got a rather complicated CListCtrl (owner draw and owner data) with a 100 entries, though I don't think that should matter for this issue. Calling SetItemState(...) takes me about 30 ms on my rather new PC (maybe half the time in release mode), when it has to alter an item state. When the item state stays the same, it returns instantly. Calling SetItemState(-1, ...) takes about the same time as any other SetItemState(...) call, even if it alters all items. It doesn't really make a difference if the ListCtrl is SW_SHOW or SW_HIDDEN and setting ListCtrl.SetRedraw(false) doesn't help either. When just a couple of items are changed at the same time, I get a noticeable break. Has anybody experienced something similar or knows a work-around? (I'm just asking before starting to write test cases) Thanks in advance, Andy

Right. One can probably do awful things using commas given the right modulation of commas and semicolons - even outside variable declarations and for-statements.