|
OOps, Shake, not expand, you could alter the top and left of the rect before moving the window, oh well, you get the point  SHouldn't give advice when passing through paint fume filled lobbies...
|
|
|
|
|
imariano wrote:
SHouldn't give advice when passing through paint fume filled lobbies...
Too funny! Thanks for the reply, I'll give that a shot 
|
|
|
|
|
I was reading thru the GDI region docs a couple of days ago, and saw that you can select a HRGN into a DC. MSDN says "After a region is selected into a device context, the application can perform various operations on it" however AFAICT all the region APIs take a HRGN to operate on, instead of operating on whatever is currently in a DC.
So, riddle me this... what does selecting a region into a DC actually do?
--Mike--
"I'd rather you just give me a fish today, because even if you teach me how to fish, I won't do it. I'm lazy." -- Nish
Just released - 1ClickPicGrabber - Grab & organize pictures from your favorite web pages, with 1 click!
My really out-of-date homepage
Sonork-100.19012 Acid_Helm
|
|
|
|
|
Michael Dunn wrote:
what does selecting a region into a DC actually do?
It is basically like calling SelectClipRgn. It makes the current clipping rgn for the DC the region that you select into the DC.
Build a man a fire, and he will be warm for a day
Light a man on fire, and he will be warm for the rest of his life!
|
|
|
|
|
What the heck does that mean? I've never seen this error before, but Explorer.exe is crashing and reporting it, then when VC++ tries to debug it, the whole system goes unstable. What is a "First-chance Exception"? I don't understand the reference.
"When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
|
|
|
|
|
From what I recall, first chance exceptions are "expected" failures within the Windows API (eg: at the network and file system layers). Here's[^] a link that may (not) shed more light on the subject.
/ravi
Let's put "civil" back in "civilization"
http://www.ravib.com
ravib@ravib.com
|
|
|
|
|
Thanks, Ravi! That does shed some light on it, and adds it to a list of clues I've been accumulating until a pattern appears. The first chance exception refers to an error state available to the debugger; for a few weeks now my server has had stability problems, and when attempting to shut down the system, has reported that certain processes could not be shut down as they were being debugged. This occurs when the debugger is not running, and this episode appears to be related. Thanks for the tip!
"When in danger, fear, or doubt, run in circles, scream and shout!" - Lorelei and Lapis Lazuli Long
|
|
|
|
|
When I UpdateData(TRUE) to set the value in my Calendar Control to its corresponding CTime object it arbitrarily adds a fixed number of days to the selected date. Example:
If the the user selected November 5, 2002 the date that would be stored in the CTime object would November 12, 2002. Likewise if they choose December 8, 2002 the date that would be stored would be December 20, 2002.
Fairly annoying. Any ideas?
|
|
|
|
|
I thought the following would read in blocks of 15 floats from a binary file but after a bunch of correct reads all the output numbers are giberish, numbers like 1E-20 type stuff..
I have to use stdio routines like fread, I have written the same code with fstreams and it works fine. I am missing some stdio quirk or something.. It seems to get hosed when the _cnt variable in the FILE structure becomes < then the size of 15 floats (60).. I believe it has to do with the buffering of the file, which is the system 4096 size.
float CPDATA[15];
do{
fread((char*)CPDATA,sizeof(float)*15, 1, thO->fd);
//outfile read info to a file
outfile<<ftell(tho->fd)<<" ";
for(int i=0;i<15;i++)
outfile<
|
|
|
|
|
Anonymous wrote:
fread((char*)CPDATA,sizeof(float)*15, 1, thO->fd);
Just an idea, try with fread((unsigned char*)CPDATA,sizeof(float)*15, 1, thO->fd); instead...
- Anders
Money talks, but all mine ever says is "Goodbye!"
|
|
|
|
|
Hello,
I need to display the progress during a file open (serialization) process. I have looked for some examples of how to do this and havent found any. Has anyone worked on this? The easiest approach might be to use the file size and the number of bytes read?
Ted
|
|
|
|
|
That's the easiest approach:
m_wndProgress.SetRange32(0, nFileSize);
m_wndProgress.SetPos(0);
while()
{
m_wndProgress.SetStep(nReadSize);
m_wndProgress.StepIt();
}
Here's a cool way to add the progress bar to the status bar: Showing progress bar in a status bar pane[^]
"The greatest danger to humanity is humanity without an open mind."
- Ian Mariano
http://www.ian-space.com/
|
|
|
|
|
if you have a file, foo.cpp, which contains the implementations of some (C-style, not classes) functions used elsewhere in the app, and a header file, foo.h, which defines those functions, would you #include "foo.h" inside foo.cpp ?
assume there's nothing in foo.h that foo.cpp needs: no constants, struct definitions, etc. foo.h simply provides an external definition of the functions in foo.cpp.
strictly, i think it's unnecessary, because the functions aren't really dependent on the external definitions - that association doesn't happen until the linker gets involved and it needs to match what callers of foo's functions think those functions are to the functions that the linker has available.
on the other hand, it seems logically 'right' to associate them somehow.
opinions?
-c
“losinger is a colorizing text edit control”
-- googlism
|
|
|
|
|
if foo.h defines those functions as 'extern "C"', you actually have to #include the header with the functions, or else the compiler will define them as C++ functions, and you'll get linker errors.
carry on, my wayward sons.
-c
“losinger is a colorizing text edit control”
-- googlism
|
|
|
|
|
You don't have to even #include an .h (in C or C++) if you define the prototypes of any functions used in your implementation file
I, personally, include the header for readability. And besides, you can write the functions in any order since all their prototypes are defined ahead of time.
Of course, if you want "C" linkage you have to define them as extern "C".
"The greatest danger to humanity is humanity without an open mind."
- Ian Mariano
http://www.ian-space.com/
|
|
|
|
|
Why then would foo.h exist at all ?
Shouldnt foo.cpp be foo.c to distinguish itself ?
IMHO if you use .cpp as an extension you should hold the relevant .h header as per normal usage.
But if it's C you should name it as such as well.
Sure it won't make any differences to compiling but it becomes easier to have conventions to follow.
Regardz
Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining.
Said by Roger Wright about me.
|
|
|
|
|
Include foo.h in foo.c so that the compiler validates how you've declared the functions (foo.h) with how you've defined them (foo.c). Since the other parts of your software that use the functions in foo.cpp use the function prototypes in foo.h, this helps ensure that the callers and the callee agree on the type and order of parameters.
The only time I omit a header file for each source file is when there is a single header (ex: library.h) for multiple source files (library_part1.cpp, library_part2.cpp, etc.).
Software Zen: delete this;
|
|
|
|
|
foo.h exists so that the rest of the app can get at the functions in foo.cpp.
and, only the functions it exports are C, foo.cpp may use C++ internally.
-c
“losinger is a colorizing text edit control”
-- googlism
|
|
|
|
|
Gary R. Wheeler wrote:
so that the compiler validates how you've declared the functions (foo.h) with how you've defined them
but it doesn't do this. it doesn't care if MyFunc is defined differently than the implementation. try it.
-c
“losinger is a colorizing text edit control”
-- googlism
|
|
|
|
|
Including foo.h would make sure there aren't any conflicts between declarations and actual functions. Of course the linker will eventually catch any typos in either file.
|
|
|
|
|
markkuk wrote:
Including foo.h would make sure there aren't any conflicts between declarations and actual functions.
actually, it wouldn't. because you can overload functions in C++, the compiler will ignore any differences. and that's the basis of the problem - the compiler really doesn't care. the only reason to include foo.h would be for my own benefit (ignoring the extern "C" linkage stuff)
-c
“losinger is a colorizing text edit control”
-- googlism
|
|
|
|
|
If you also put the extern "C" on the actual functions, then the compiler will do the check for differences. When I setup a C++ source file that I want to have extern "C" functions, I always also add this to the actual functions to make sure that there is a match. If I leave off the extern "C" on the actual function and it doesn't match the prototype, I won't get an error until linking.
Best regards,
John
|
|
|
|
|
Hmm. I think I see where the confusion lies. With C++ and overloading, you're right. Having foo.h does not guarantee that the implementation in foo.cpp will be verified by the compiler, unless you use the 'extern "C"' construct. I believe Visual C++ compiles sources named .C as if they are 'extern "C"' by default.
In any case, I think it's better stylistically to have a header file than not. Other people looking at the code will expect to see it. If you don't include the header file, then other folks reading the code will have to look at each use of the function(s) to see how they are used. Also, I normally consider the header file to describe the controls for a black box (the 'interface' to the black box) while the source file is the 'implementation' of the black box. I then document changes to the interface in the header file, and changes to the implementation in the source file.
Just my $0.02.
Software Zen: delete this;
|
|
|
|
|
Hi!
I'm still working on my assignment to modify my chat program to have the capability to transfer files as well as messages.
I put a button on the client side, and when the person clicks on it, the file dialog box is supposed to open, and the person can choose the file to send.
I get the dialog box, the program gets the file path.. reads the file ok.. and now it is being sent to the server.. (I've made progress!)
However, the server gives an error, "An attempt was made to access an unnamed file past its end". 
If anyone knows what the error means exactly, or can give any suggestions about it... please respond.
Thank you..
|
|
|
|
|
How are you reading and writing the file? If you are chopping it up and sending it you may be reading into the file past its end same as when you receive the file.. could you post some code?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
