|
Which DLLs are reported as missing? If linking statically with the CRT doesn't solve it, you'll need to copy those DLLs over along with your app.
--Mike--
http://home.inreach.com/mdunn/
Sometimes, arming yourself with a big pointy stake just won't do you any good.
|
|
|
|
|
For example, MSVCRTD.DLL, MFC42D.DLL....
|
|
|
|
|
these are the MFC debug DLLs.
if your program is asking for these, then it looks like your program (or something it's linking with) is not statically linking to MFC.
-c
------------------------------
Smaller Animals Software, Inc.
http://www.smalleranimals.com
|
|
|
|
|
Try: Project>Settings and then select "Release" from the drop down combo box and again use the MFC in a statically linked library, this will make ur .exe file smaller. To compile goto Build>Batch build and check "Release" and click build. then goto the Release directory in your project and try that .exe file. Good luck, hope this helps....
Kun
|
|
|
|
|
First if you are going to distribute you application you need to compile it in release mode. The errors you are getting are because the debug version of those dlls are not on the target system, which they would not be if it is not a development machine.
Whether you statically link or dynamically link is up to you, however consider that statically linking increases the size of your redistributable.
If you are distributing this application the wrong thing to do is copy copy a folder, i.e. the debug folder. What you need to do is use an installation program such as Installshield or Wise. These tools help with such issues as registering COM components and ensuring the proper version of the required dlls on in place.
Second, ignore the advise given to you already.
|
|
|
|
|
I get an error "Unhandled exception at address 0x00000005" in my code. This function has already been called once when my program calls it again, and works fine the first time. The error line is on a simple assignment line:
iBytesReceived = 0;
Using the debugger to check the variable right before the assignment yields "CXX0069: Error: expression cannot be evaluated"
MSDN says this about error CXX0069:
"variable needs stack frame
The expression evaluator cannot evaluate the variable because it does not occur in a stack frame. This may be caused by variables declared as part of an inline function."
So, what the heck does all this crap mean 
- John
|
|
|
|
|
Look at 'this', and see if it is NULL. It could be that you've tried to call a method in a pointer to a class that is NULL.
Christian
#include "std_disclaimer.h"
People who love sausage and respect the law should never watch either one being made.
The things that come to those who wait are usually the things left by those who got there first.
|
|
|
|
|
Hi,
I've developed a program that can display an array(16 elements) in graphic mode (just liked plotting a graph). The value of this array can be changed anytime, so I set a loop to keep checking the array and update the display. In this loop, I have to do some sorting, so there are so many for loops and if loop. These loops cause the display very very very very slow. However, these loops must be exist... how can i improve it?????
|
|
|
|
|
I'm no expert, but maybe if the sorting had its own thread it would solve your problem.
|
|
|
|
|
Yes using a seperate thread would give the appearance that the draw was being done more quickly. A means to check if updating is required before doing any sorting or drawing would also help.
Make sure you understand the issues involved with multi-threading before you attempt it.
These are professionals, please don't try this at home.;)
|
|
|
|
|
I know nothing about thread!!!!!!!! Can you give me some examples???????
Thank you!!!!!!!!!!!!!!!!!!!
|
|
|
|
|
16 elements... should not be so slow!
I can't understand why you need a loop to check the array and how this could slow down drawing.
Check the array, sort the elements, then draw them. It should be easy! 
As for the initial check, you may have a flag somewhere that you set when you update the array, thus you can avoid checking at all (if this is possible).
Paolo.
|
|
|
|
|
Are you 100% your sorting algorithm is the problem? Try commenting out the call to sort and see if that speeds up your program. sorting 16 elements shouldn't take any time at all.
|
|
|
|
|
You should do a couple of things.
1. Post some code so people can comment intelligently on what you are doing.
2. Put your array into a binary tree or sorted list, so that it remains sorted at all times.
3. If there are 'many' for loops, you're probably using bubble sort - if you use an STL container it is trivial to use a more efficient sort, not that this should matter for 16 elements ( although you don't say what they are. If they are large items and you sort by making deep copies, this could be the problem )
4. The most likely problem could well be your drawing code, but I cannot comment if I have not seen it.
Christian
#include "std_disclaimer.h"
People who love sausage and respect the law should never watch either one being made.
The things that come to those who wait are usually the things left by those who got there first.
|
|
|
|
|
If i comment out the following codes, my display is much faster:
//Check Alpha Line first
for (int i=0; i
|
|
|
|
|
Hi,
I use CreateFile for use the Comport and LPT.
With Comport : I would like to know how data is in the InputBuffer ?
With LPTport : I would like to use Strobe, Init, Status, ...
and How can I do for read and write a data in PCICard ?
How can I do it ?
Best regards
youssef
|
|
|
|
|
Hi,
I use CreateFile for use the Comport and LPT.
With Comport : I would like to know how data is in the InputBuffer ?
With LPTport : I would like to use Strobe, Init, Status, ...
and How can I do for read and write a data in PCICard ?
How can I do it ?
Best regards
youssef
|
|
|
|
|
can somebody please help?!! what am i doing wrong here:
CDialog m_wndSlider;
m_wndSlider.Create(IDD_SLIDER_DLG,this);
m_wndSlider.ShowWindow(SW_SHOW);
the dialog wont display! (i am using cdialog instead of my CDialog derived class to eliminate these errors. ID_SLIDER_DLG is an empty dialog...
thanks
|
|
|
|
|
You are destroying the CDialog object. 
Since it's a modeless dialog, the MFC object should survive enough to show up. Either make it global or member of a class (maybe CWinApp?).
Cheers,
Paolo.
|
|
|
|
|
Hello,
We have an ActiveX control (T3Result.ocx) and we recently created a separate project dll (T3Resultfrares.dll) containing the French versions of our resource strings. However, everytime we build the ActiveX control, we get this message:
Warning: cannot find "T3Resultfrares.dep"
What is a .dep file? Can I re-create it to get rid of this warning? If not, can I do something to stop the message?
Thanks in Advance!
Derek
|
|
|
|
|
Hello,
We have an ActiveX control (T3Result.ocx) and we recently created a separate project dll (T3Resultfrares.dll) containing the French versions of our resource strings. However, everytime we build the ActiveX control, we get this message:
Warning: cannot find "T3Resultfrares.dep"
What is a .dep file? Can I re-create it to get rid of this warning? If not, can I do something to stop the message?
Thanks in Advance!
Derek
|
|
|
|
|
Hi ,
I need to bitblt some polygon - not rectangle
( i have it as CRgn ).
Probably there's somewhere modified BitBlt function that looks similar to that
[ccode]
BOOL BitBltRegion(
CDC* pDestDC,
int ptVertex[0].x ,
int ptVertex[0].y ,
CDC* pSrcDC,
CRgn reg,
DWORD dwRop );
[/ccode]
or somebody can give me a hint to write it myself
I'd very happy to know , or probably there's
another way ( masks ? )
Thank You
in advance
|
|
|
|
|
I think what you might want to do is create a polygonal region equivalent to the polygon you want to blit, then select that region as the clipping region of your destination device context.
If you blit the rectangle containing the polygon at the right coordinates after this clip region is set, it should to the trick. See CDC::SelectClipRgn.
|
|
|
|
|
Thank You , Tim , works great !
Just not to forget restore original clipping region after that ..
|
|
|
|
|
By the way , does it mean that if I want to work with DCs like with
layers , when u don't see some parts of picture under
topmost layer ( DC ) , u should do the same - use SelectClipRgn ?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
