|
Yes break your file(exe) to dll files
|
|
|
|
|
Is there some recommendations for size and how to do that properly?
Thanks.
|
|
|
|
|
Depends - are you talking about its physical size on disk, or its footprint when in memory?
Converting things like static LIBs to DLLs may actually increase the total size of your end-user distribution, because when you link in a static LIB, you only pull in the functions that you need. But a DLL will contain ALL functions in the library, even if your application only uses 5 out of 80 of them.
If you are talking about your footprint, 80MB may or may not be all that bad, depending on what your application is doing. If it is acting as a database or processing engine, it might not be bad. If it is a fancy text editor working with a 1MB file, it might be.
Peace!
-=- James Please rate this message - let me know if I helped or not!<HR>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles
|
|
|
|
|
Actually my application is a scientific application which combine MFC based front end and calculations in Fortran static library. During the run program doing a quite freqent allocations/deallocation of big arrays for the calculations.
And another concern is a project compilation time. It's take a while to compile.
Could you recommend something about it?
Thanks.
|
|
|
|
|
Since you are not building the libraries (they are [preexting] Fortran libraries), you are seeing app build delays. Correct use of pre-compile headers is likely the best way to improve compilation times. Breaking up larger CPP files into small ones can improve build times if you are making code changes, but might not affect release build times. Other than that - no suggestions.
As far as runtime performance, not constantly throwing away allocated memory (keep it around and reuse it as much as possible) is likely your best option. Your users know the kind of application they are using and should expect it to be a bit of a hog at times.
Peace!
-=- James Please rate this message - let me know if I helped or not!<HR>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles
|
|
|
|
|
On top of what James said regarding app performance, if you're app is creating/destroying a lot of threads, consider creating the threads just once, and then just starting them. Creating/destroying threads can cause quite a bit of overhead.
As far as file size, an 80mb file could take quite a bit of time to initially load. You might want to consider breaking the app into DLLs that load when needed the first time, and stay in memory until the app is shut down.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Hi,
I downlowded The Project "ScanChannelsBDA.src" from:
http://nate.dynalias.net/ScanChannelsBDA/ScanChannelsBDA.html
When I compile the source code I get this error:
Error 1 fatal error C1083: Cannot open include file: 'dshow.h': No such file or directory c:\digital-tv\scan-tv.zip\src\stdafx.h 15
Where can I find "dshow.h" . Please help, I need to compile this project.
Thanks
Lassaad
|
|
|
|
|
Google for DirectShow...
Peace!
-=- James Please rate this message - let me know if I helped or not!<HR>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles
|
|
|
|
|
Hi,
My friend i tried this and much more but I reelly have a big problem to find
"dshow.h"
lassaad
|
|
|
|
|
The header comes with an SDK. Unless you install the SDK and follow its instructions on setting
the development environment to where the header/lib/exe files can be found then the compiler
isn't going to find it.
Mark
|
|
|
|
|
|
Look For Microsoft SDK in your C:\Program Files\Microsoft SDKs\Windows\v6.0A\Include or otherwise download Microsoft SDK
Thanks & Reply
|
|
|
|
|
I am trying to get a random number generator for a Windows Form program in Visual C++. Any ideas?
Bob
|
|
|
|
|
The RTL provides srand(...) and rand(...) for PRNG...
Peace!
-=- James Please rate this message - let me know if I helped or not!<HR>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles
|
|
|
|
|
This is how you do it in C:
#include <time.h><br />
<br />
srand ((unsigned) time (NULL));<br />
...<br />
while (i < 20)<br />
{<br />
q = (positioner) malloc (sizeof (struct broj));<br />
q->element = rand ();<br />
q->next = p->next;<br />
p->next = q;<br />
i++;<br />
}
Hope I helped 
Alessandra
|
|
|
|
|
i want to start my program then go out and when a predifined event happens outside of the program i want to program to press a button on another aplication how can i make my program press buttons within other applications?
|
|
|
|
|
I have implemented this by using the CSocketComm Class[^]. I am basically setting up one application as a server and the other as a client, and sending messages that I can then parse and act on. The two applications talk to each other using the loopback address(127.0.0.1) and a port I specified.
This of course will only work if you have written both applications.
Regards,
Dustin
|
|
|
|
|
In several of my programs I have been using the CSocketComm class[^] in order to send commands between applications, but what I'm not real clear on is how to transfer files. I'm assuming that I will use a CFile or similar on the client side to read the bytes and transfer to the server, which will re-assemble them into another CFile, but I'm lacking in the specifics such as how many bytes to send at a time etc. Does anyone know of a good tutorial that I can read for some help, or is it as simple as I have stated above.
Thanks as always for your help,
Dustin
|
|
|
|
|
Dustin Henry wrote: I'm assuming that I will use a CFile or similar on the client side to read the bytes and transfer to the server...
I think you'd want to use CFtpConnection.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
I won't actually be connecting to an FTP server, just another computer running my server application implemented with the CSocketComm class. I'm doing this so that I can retrieve current data about the system the application will be hosted on. So in escence I need to send the file from application to application and then have the server side application save the file to disk.
Thanks,
Dustin
|
|
|
|
|
Dustin Henry wrote: I won't actually be connecting to an FTP server...
Understood. Sorry 'bout that. 
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
It sounds like you have it.
Send any size chunks you want. Keep in mind the default socket internal buffer size is 8K so
for best performance keep those flushed (recv data as fast as you can ).
A chunk/packet size right around 500 bytes will insure each chunk fits in one TCP packet but the
protocol handles larger chunks. Without increasing the socket buffer sizes, 500 - 8K byte packets
will work well.
|
|
|
|
|
Great! Thanks as always for the advice Mark!
|
|
|
|
|
If you want to achieve high transfer rates you should consider setting you buffer sizes to at least 32K (e.g. read 32K chunks from a file and use a socket send buffer of 32K). Otherwise bulk data transfer will be very likely slower than 100 kB/sec.
Tip: Set the server socket send buffer to the wanted size (SO_SNDBUF and possible also SO_REUSEADDR) after you created it, sockets created from the listening socket will then inherit this settings.
For further reading see Jon Snader's Effective TCP/IP Programming.
/M
|
|
|
|
|
Fly Like An Eagle With MIGHTY POWER.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
