No. What you need is a different kind of job. That would be better both for you and your prospective employee.
Seriously, ask yourself this question: what is the point of applying to a job with requirements you cannot hope to meet? Even if someone were to provide you with the example you ask for, it's likely the employee will realize it's not your work, and that you cannot be trusted. In the unlikely case he hires you anyway, you won't be able to complete any task, and you'll be fired.
Better spend your efforts in finding a job that fits your abilities!
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
I am writing a program to control some I/O card under Win8.1 environment, however, initialisation winio always fail. There is no problem under WinXP or Win7, so I guess it is caused by Win8.1 UEFI blocked the WINIO.
I can't get precise time, but, with old BitBlt(), not a 800*600 bitmap,
I set tick count array in program, tkCount-tkCount = tkCount - tkCount ... = tkCount - tkCount = 170 ms around.
Then I use new BitBlt() to load 800*600 bitmap, it gives 400ms around.
So I should say it added 230 ms.
Old BitBlt() just transport about 1/5 or 1/6 part of 800*600 bitmap.
I expected to use a 800*600(the screen area) memory DC to hold all parts changes, then BitBlt() to screen.
Now that 800*600 tooks so much time, I don't think a double buffer technique is helpful.
You can use CDC::FromHandle() to get a temporary object for immediate use. Alternatively, you can CDC::Attach() to keep a more permanent CDC object around. You should make sure you release a device context (DC) when you're done using it (FromHandle sort of automatically handles this situation by going out of scope).
If you have CWnds, you can also get a pointer to an existing CDC with CWnd::GetDC().
There is a lot of info on drawing in GDI online, I suggest you read up on it.
I can only assume that something has been corrupted somewhere. But as I said before, it's impossible to guess what. Your only chance is to collect all the information that you can, and report it to Microsoft.
"You may use a custom drawn scroll bar or handle WM_CTLCOLOR when you only need to change the background"
I already tried that ... if I override WM_CTLCOLOR I could color everything, except scrollbars ...
"Searching the web may give you some solutions. The article http://www.drdobbs.com/windows/developing-a-custom-windows-scrollbar-in/184416659[^] is rather old but contains a good introduction and shows how to implement a custom drawn scroll bar."
I saw that article, but is about replacing the original scrollbar with CScrollBarEx control ... well, in this case I will front with 2 issues: hiding the original scrollbar, and second, synchronize the listctrl with CScrollbarEx control ... I think that is the longest road ... and the hardest ...
I thought that trying to use DrawThemeBackground I could change the scrollbars colors ... I am working on that for weeks ... I have to dig in ...
OnDraw is a CView member function. You probably mean some kind of custom / owner draw. But this won't work for the scroll bars of list controls because only the list control content can be changed by this method. The scroll bar is still drawn by the system when necessary and your drawing vanishes.
If handling WM_CTLCOLOR did not work (and I believe meanwhile that it does not work with list controls), the only solution is using a complety custom drawn control or another GUI framework like Qt.
Thank you so much for your attention Jochen !
In the real situation, I used an CGridCtrl, and this control has CGridCtrl::OnDraw to drawing itself ... but there is no difference between this kind of control or CListCtrl, or CListBox ... I had tried to change the color of the scrollbars of these last ones and I didn't succeded ...
After all, CGridCtrl is derived from CWnd, so is the same matter ... Should be a chance to move that code on some handler that is called after the system is redrawing the scrollbars ? ... who knows ...