help.. because it can be the most boring thing to do. i really don't know anything to help it other than my curiosity. yes curiosity helps but i need to
- grasp what the code does.. fast!
- without breaking my head. (is this a joke? i'm asking myself)
- get it done only with a cup of coffee.. lol (joke? yes/no? hmm)
If I've got a piece of 'foreign' code I really have to understand, I usually make a copy of it and refactor it to my coding style and naming conventions. Doing this carefully, and stepping through the result in the debugger, usually gives me enough understanding to either use the code or rewrite it.
A good first step that's worked for me is to comment the code.
First a header for each method that explains what the method does. Next comments on the variables of the class, explaining what they do and how they're used. It also helps to comment unclear blocks of code once you figure out what they do, so you don't have to solve the same problem again later.
I sent the LVM_SETITEMPOSITION msg to the desktop icons' ListView, and the specified item changed the position, but I press 'F5' for refurbishing the desktop, its position had restore, why, why, i'm mad.
You could start by placing your code between <pre></pre> tags as described in point 7 here[^]. I also notice that you have a printf() and an exit() call within your timer event. Neither of these belong in a Dialog, I suggest you reread the MSDN section on Dialog Box Programming[^].