I have been writing a program to display a gif on the computer screen.  However
when I compile it, the picture does not show up.  Here's the source code:

void Open_Show(HDC DC, int x, int y)
{
  char buf[BUFSIZ];
  FILE *fp;
  if((fp=fopen("c:\\pics\\mybmp.gif", "r+"))==NULL)
  {
    MessageBox(HWindow, "Can't open file!", "Error", MB_OK);
  }
  fseek(fp, 776L, SEEK_END);
  fread(buf, sizeof(char), 1, fp);
  fprintf(fp, "%c");

Does anybody know what's wrong with this code?  

Royous

This function call indicates that your questions have to do with Windows
programming.

Rather bizarre seek to a magic position.  A comment on what you expect this
to accomplish would be in order.  Always check the return value of functions
that supply them.  [OK, maybe not printf()].

You tried to read one [1] count-it "a" single, solitary character.  You did
not check the status of the seek, or the status of the read.  Since you have
no idea if either worked, what do you expect a sensible result to be?

OK, where is the character you are trying to print, and why are you writing
it back to the file you read it from?

0.  Invest in a good lint.  Or at least turn your compiler warnings on.

1.  Post windows programming questions to windows newsgroups.
--
Hypertext C-FAQ: http://www.eskimo.com/~scs/C-faq/top.html
C-FAQ ftp: ftp://rtfm.mit.edu, C-FAQ Book: ISBN 0-201-84519-9
Try "C Programming: A Modern Approach" ISBN 0-393-96945-2
Want Software?  Algorithms?  Pubs? http://www.infoseek.com

'HDC' is not defined. 'DC' is never used.

'BUFSIZ' is not defined.

'FILE' is not defined. (Where is <stdio.h>?)

'fopen()' has not been prototyped.

'HWindow' and 'MB_OK' are not defined. 'MessageBox()' has not been prototyped.

You might want to check the return values of these two functions.

You have not given 'fprintf()' anything to print!

The file is never closed, and the file pointer is lost when the function
returns; this is a bad thing.

Other than that, it's a wonderfully well-written function. Be proud.

--
(initiator of the campaign for grumpiness where grumpiness is due in c.l.c)

Attempting to write in a hybrid which can be compiled by either a C compiler
or a C++ compiler produces a compromise language which combines the drawbacks
of both with the advantages of neither.

<stdio.h> would define BUFSIZ too.

--
-----------------------------------------


-----------------------------------------

...

I would expect GIF files to be in a binary format so you should open them
as binary files, with a mode such as "r+b".

There isn't enough information to decide whether it is appropriate or not.
The main uses of BUFSIZ would be to allocate a buffer of a reasonable
size to pass to setvbuf() or to define a reasonable sized buffer for the
processing of data in a block buffered fashion (where BUFSIZ is hopefully
optimised in some way for the platform in question). The particular
fread() here only reads one byte so BUFSIZ will be large enough to hold it.

--
-----------------------------------------


-----------------------------------------