|
the VC6 installation error happended several times when I install it:
Setup was unable to create a DCOM user account in order to register "c:\Program Files\Microsoft\Visual Studio\Common\Tools\VS-Ent98\Vanalyzr\Valec.exe"
At last of installation process, setup said: failed.
But VC6 still can be used  .
BTW: When try to update VC6 with service pack, service pack setup says: Can not find any VC products.
What is the problem? how to fix it?
|
|
|
|
|
|
google it. The answer is the first result.
|
|
|
|
|
Hi,
I want to change the shape and color of a MFC dialog box?
Any feedback on this would be appreciated. I know this is probably a very common
question, just dont know how to do this.
Much appreciated,
garyc
|
|
|
|
|
A window is always rectangular.
Any other shape can be created using a region.
There are several functions in GDI that help you create regions - Region Functions[^]
Here is a simple example with source code to create a region from a bitmap and apply to a window.
Fish Region[^]
Background color can be set by handling the WM_CTLCOLORDLG[^] message.
|
|
|
|
|
Much appreciated.
I never knew how they did this and now I know.
Thanks,
Garyc
|
|
|
|
|
you can add this with ClassWizard,or in the sources code to add it by yourself.
just like this:
C***Dlg.h
afx_msg HBRUSH OnCtlColor(CDC* pDC, CWnd* pWnd, UINT nCtlColor);
C***Dlg.cpp
BEGIN_MESSAGE_MAP
......
ON_WM_CTLCOLOR()
......
END_MESSAGE_MAP()
HBRUSH C***Dlg::OnCtlColor(CDC* pDC, CWnd* pWnd, UINT nCtlColor)
{
HBRUSH hbr = CDialog::OnCtlColor(pDC, pWnd, nCtlColor);
switch (pWnd->GetDlgCtrlID())
{
case IDC_STATIC1:
case IDC_STATIC2:
pDC->SetTextColor(RGB(255,0,0));
break;
case IDC_STATIC3:
case IDC_STATIC4:
pDC->SetTextColor(RGB(0,0,255));
break;
}
return hbr;
}
Best Reguards !
by Koma
http://blog.csdn.net/wangningyu
|
|
|
|
|
Much apreciated guys for your contributions.
Thanks,
Garyc
|
|
|
|
|
Hi,
I need help to write a multi thread simple class,
I know this should be simple but I face some difficulties,
any help will be appreciated.
Implementing single-write, multiple-read multi thread synchronization (using windows synchronization primitives like mutex, semaphore etc.).
Thanks in advance,
Eyal
modified on Saturday, October 17, 2009 7:11 AM
|
|
|
|
|
Hi Eyal!
In what problem did you run, what have you done so far, which multithreading tutorials have you read?
Have a good weekend
/M
|
|
|
|
|
Hi Moak,
Just faced with this question in a C++ questioner/quiz.
I read information/tutorials on multithreading mutex but I haven't deal yet with the answer.
looking for the right answer.
Best,
Eyal
|
|
|
|
|
|
cmk,
Thank you very much,
Eyal
|
|
|
|
|
The code I'm using needs HWND but I just have no clue how it works and how to initialise it.
In my SoundManager class I have:
bool OggPlayer::InitDirectSound( HWND hWnd )
{
//code
}
and then in mainGame:
void MainGame::Initialise()
{
HWND hwnd = NULL;
op.InitDirectSound(hwnd);
op.OpenOgg("music.ogg");
op.Play();
//random code
}
Obviously I need to pass hwnd into InitDirectSound but at this point I'm just guessing and setting it to null.
Any help explained in layman's terms would be appreciated.
|
|
|
|
|
What kind of application have you built?
Is it an MFC application?
If it is you can get the main application window handle using AfxGetMainWnd()->m_hWnd.
If it is a dialog application and your writing the code in the dialog class, you can directly use m_hWnd.
|
|
|
|
|
No MFC involved.
I'll try using m_hWnd... when I figure out how to use it >_>
|
|
|
|
|
GLGunblade wrote: I'll try using m_hWnd... when I figure out how to use it >_>
This is just the handle to your application's main window (whether app, or dialog). Windows needs it to discover who makes the call to an API function. You don't need to figure out how to use it so much as use the value that is returned by a CreateWindow() call, or in a Dialog application the handle that Windows sends you on every callback.
|
|
|
|
|
Sorry but still stuck, I'm pretty much a n00b programmer.
By using it I mean I just have no clue on handles or what not or where to put m_hWnd, it comes up as undeclared identifier. Everytime I've coded I've never really bothered with this and if some piece of code included it i just stuck it in and hoped it worked.
I have no CreateWindow call and I have no idea where in my program (which isn't really my program) windows sends a handle.
|
|
|
|
|
GLGunblade wrote: which isn't really my program
Cannot ask the author?
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
He wasn't available at the time and since I wanted this done asap and wasn't probably wouldn't see him till Tuesday i thought i'd ask.
Though I've got it working. Thanks for the help guys
|
|
|
|
|
GLGunblade wrote: I have no CreateWindow call and I have no idea where in my program (which isn't really my program) windows sends a handle.
I would suggest that you get hold of a book on Windows programming to get an understanding of the basics; Charles Petzold has written some very good ones.
|
|
|
|
|
i'll keep that in mind and take a look, thanks
|
|
|
|
|
Hi,
I am wondering if any of the experts can give me some insights into the Different behavior
of the RichEdit when the object is Connected
By DDX_CONTROL as opposed to Create
1) The Font is Different
2) GetTextExtent for calculating the Length
of a line works differently (maybe
this has to do with font)
3) The Background Color is different
with DDX_CONTROL it seems be in
reverse video (when I right
it goes away)
thankx
|
|
|
|
|
I can't answer 100%, but I'll help a bit.
The difference is not DDX_Control. That just helps you associate a variable in your dialog with a window.
The difference is:
a) A control "built" in to the dialog resource, and created automatically as part of the dialog creation,
and
b) A control you create manually, later.
So, to answer your points...
1) Different Fonts.
At creation time for the dialog, it sets the font (WM_SETFONT) of the child windows (ie, your rich edit) to the same font as the dialog is set to use.
When you create a window manually later, this step does not happen.
2) Different extent sizes.
Almost certainly the same issue. Text size comes from fonts.
3) Inverse background colour.
Not sure, but I bet the text is inially selected, or something along those lines. Try dragging the mouse over text - I bet it goes inverse too.
Points 1 & 2 would be the same for a button, or an edit control... Nothing to do with the rich edit control at all.
Hope that helps!
Iain.
I have now moved to Sweden for love (awwww).
If you're in Scandinavia and want an MVP on the payroll (or happy with a remote worker), or need contract work done, give me a job! http://cv.imcsoft.co.uk/[ ^]
|
|
|
|
|
I guess I can send EM_GETCHARFORMAT to the rich edit control after the DDX_CONTROL connects it to the object
and find out the font
I can then set it with the EM_SETCHARFORMAT message
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Java | [Coffee]](https://www.codeproject.com/script/Forums/Images/coffee.gif)
(