|
|
i use the CreateWindow to create The Dialog Box
In The Form, i preset the values in the textbox such as "Testing"
on the InitDialog msg, i change the textbox msg to "Test Completed using SetDlgItemText, then i refresh the window using UpdateWindow.
|
|
|
|
|
try calling Updatedata with aprropriate parameters.
Thanx
TAKE CARE
|
|
|
|
|
I try to call the SetBkColor method of the CProgressCtrl and get the following error:
<br />
Compiling...<br />
FlashDialog.cpp<br />
c:\viewstore\beekb_snapview\testtool\ttmod_atapi\src\flashdialog.cpp(129) : error C2039: 'SetBkColor' : is not a member of 'CProgressCtrl'<br />
c:\program files\microsoft visual studio\vc98\mfc\include\afxcmn.h(477) : see declaration of 'CProgressCtrl'<br />
Error executing cl.exe.<br />
The CProgressCtrl does not have a SetBkColor Method? MSDN clearly specifies it does!  
|
|
|
|
|
You need to look at the documentation that came with VC6.
SetBkColor is a new method in MFC 7.x.
To achieve the same goal, use SendMessage to send the progress bar a PBM_SETBKCOLOR message.
|
|
|
|
|
Hello, Sir:
Now i have some trouble with the FPU. I need test CPU FPU function, it include "FPU Exception Test", "FPU Control Register Test", "FPU Tag word Register Test" and "FPU Calculation Test". And I don't how can test those really. I have studyed IA-32 Intel® Architecture Software Developer’s Manual, and knew some about FPU. Do you know how to "test" such FPU fuction. Do you have a example about those, or give me some advice? I am helpless, waiting...
|
|
|
|
|
How best create CHM visually ?
-by which program?
Does it keeps DHTML ?
|
|
|
|
|
CHM files contain HTML that has been compiled and linked through a table of contents and optional index. You use the Microsoft HTML Help Workshop to do this. Any good HTML editor can be used to create the source files.
Some of the commerical help authoring tools out there may provide more sophisticated design and editting features, but in theory you can get by with Notepad.
Since the IE rendering engine is used, I think any DHTML is also valid. The Platform SDK help uses DHTML, for example.
Brad
|
|
|
|
|
I want create CHM from existing internet files -that was downloaded by IE,
by seconds.
That is- run program - press include file- press complile- result received.
VISUAL CHM is a sample,
but do not works with DHTML.
|
|
|
|
|
Just curious as to how one could create the equivalent of .Net Attributes as used in C# in C++ in a non .Net environment. Any links or pseudo code would be great.
Thanks
|
|
|
|
|
Some programs very dislike DHTML,
for sample Viasual CHM4.0,
(chm creator)
they need to eliminate all DHTML from file to work correctlu with them.
Is there utilities that can remove DHTML from file ?
Thanks.
|
|
|
|
|
Hi
The text on every line from a multi-line editbox should be added to a 'CStringArray'.
This works most of the times, but sometimes not. When there is little typed into the edit box, like 1 character ... the array isn't filled.
(added the code below)
for example:
I've typed in the editbox 'a' then debugged it.
It appears that iLen gets on '1' but iDummy is left on '0'. strTemp is empty too so he doesn't add the text to the array.
Can anyone see the mistake i have made?
<br />
CString strTemp;<br />
CEdit* pEdit = (CEdit*) GetDlgItem(MY_EDIT);<br />
CStringArray m_array;<br />
m_array.RemoveAll();<br />
<br />
for (int i=0; i<(pEdit->GetLineCount()); i++)<br />
{<br />
int iLen = pEdit->LineLength(pEdit->LineIndex(i));<br />
int iDummy = pEdit->GetLine(i, strTemp.GetBuffer(iLen));<br />
strTemp.ReleaseBuffer(iLen);<br />
if ( iDummy != 0 )<br />
{<br />
m_array.Add(strTemp);<br />
}<br />
strTemp = "";<br />
}<br />
|
|
|
|
|
Only suggestion:
If CEdit::LineLength() and CEdit::GetLine behave different concerning the terminating '\0' you may solve the problem by changing strTemp.GetBuffer(iLen) to strTemp.GetBuffer(iLen+1)
Another tipp from the documentation of CArray in MSDN:
"Before using an array, use SetSize to establish its size and allocate memory for it. If you do not use SetSize, adding elements to your array causes it to be frequently reallocated and copied. Frequent reallocation and copying are inefficient and can fragment memory."
MS
|
|
|
|
|
The m_array.RemoveAll(); statement is not necessary as there is obviously nothing in the array to remove.
The int iLen = pEdit->LineLength(pEdit->LineIndex(i)); statement should probably be int iLen = pEdit->LineLength(i); instead.
|
|
|
|
|
Hi all! I'm new to SAPI and I was wondering how you can get your application to use another speech engine other than the MS ones. I installed the Dragon Naturally Speaking 7 engine but it doesn't show up in the speech properties dialog so you can't select it. I've heard that you can use SpEnumTokens() to find all the engines available but am I right in thinking that this only searches in the Microsoft directory in the registry and not any others? Please help me! I'm desperate!!
Thanks for ANY help!
|
|
|
|
|
Hello all,
I am having some troubles with tracing memory leaks in VC++ 6. I have a program which includes a bunch of DLLs, now when I execute it and shut it, it dumps quite a bit of garbage from memory. Usually it states where the object was created, but in this case it doesn't, it only dumps objects. This leads me to believe that the memory leak is generated in one of the linked DLLs.
Is there any trick or program which can figure out where the memory leak comes from? I have no idea where it originates and I'd like to clean it up...
Thanks,
- Fahr
|
|
|
|
|
Did you take a look at the bottom of the "Debug" pane? That shows where they usally come from? (I assume you have done that). Next, do you have access to the dll source code? There is an application that will determine memory leaks, but I cannot think of it right now...
Larry
Larry J. Siddens
Cornerstone Communications
TAME THE DOCUMENT MONSTER
www.unifier.biz
|
|
|
|
|
I have access to the source of all the DLLs. And like I said; it does NOT state the origin of the memory leaks, it must be one of the DLLs, but I can't figure out which one.
Please remember the title of that program! 
|
|
|
|
|
Make sure you build all the dll's in Debug. Run you application in Debug (inside the studio). Exit your application (when you know that the leaks (or suspected leaks occurre)). Open the output pane window, click the "Debug" tab, then go to the bottom. If there are memory leaks (that VS can find) they will be listed. Then if you double click on the source file, it will take you to where the item was created and then not released.
Again, I am assuming that you have done all this.
Larry
Larry J. Siddens
Cornerstone Communications
TAME THE DOCUMENT MONSTER
www.unifier.biz
|
|
|
|
|
Yes, I have done it all.
The point is that I DO see a HUGE list of memory leaks, I have a slight idea from which DLL and even class they come, but it wont give out any source files and/or lines. Only dumps objects...
|
|
|
|
|
Now I'm confused. I have several projects that I check that are built (the whole project including the dll's) and when there is a leak, it will give me the file/line of the offending object even if it is in the dll!
When you compile your project, is the dll a dependency(sp) of the main project?
Larry
Larry J. Siddens
Cornerstone Communications
TAME THE DOCUMENT MONSTER
www.unifier.biz
|
|
|
|
|
No, they're not dependencies. We have multiple actual programs which use the same shared DLLs, so the DLLs are mostly standalone projects alltogether.
You think I can trace the leaks when I include the DLLs in question in the workspace of my project?
|
|
|
|
|
Yep I do. I thought you were already doing that. Do you know how to make them a dependancy? I'm assuming yes.
Larry
Larry J. Siddens
Cornerstone Communications
TAME THE DOCUMENT MONSTER
www.unifier.biz
|
|
|
|
|
I guess just adding them to the workspace will do the trick, no?
If not, then please tell me 
- Fahr
|
|
|
|
|
Yes. But you have to make sure that the main exe project depends upon these dll's. This is done by: In the File View, right click on the "Workspace", Select "Insert Project into Workspace", when the dialog comes up, select the project to insert (the DLL in question), then check the "Dependency of" and select the main exe. When finished, make sure that you have "Debug" selected as the build and do a "Build All". This will compile the files for the DLL and your exe that uses them. Run the puppy and see what happens.
Larry
Larry J. Siddens
Cornerstone Communications
TAME THE DOCUMENT MONSTER
www.unifier.biz
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
