Thread: GDI+ Support in Dev C++

  1. #1
    Yes, my avatar is stolen anonytmouse's Avatar
    Join Date
    Dec 2002
    Posts
    2,544

    GDI+ Support in Dev C++

    Does anyone know if Dev C++ supports GDI+? Or does using GDI+ limit the code to one compiler?

    If anyone wants to check, look for <gdiplus.h>.

    A web search doesn't bring up much.

    Thanks.

  2. #2
    Registered User Dante Shamest's Avatar
    Join Date
    Apr 2003
    Posts
    970
    I never could get GDI+ to work with Dev-C++ either.

  3. #3
    Yes, my avatar is stolen anonytmouse's Avatar
    Join Date
    Dec 2002
    Posts
    2,544
    Thanks.

  4. #4
    GDI+ eh, what's so good about it?

  5. #5
    erstwhile
    Join Date
    Jan 2002
    Posts
    2,227

    Re: GDI+ Support in Dev C++

    Originally posted by anonytmouse
    Does anyone know if Dev C++ supports GDI+?
    I had problems with MinGW, too. I haven't tried for a while, though....
    Originally posted by anonytmouse
    Or does using GDI+ limit the code to one compiler?
    No, it can be made to work with borland compilers (eg. bcc5.5 - use implib to create the lib, ms headers).
    Originally posted by Mithoric
    GDI+ eh, what's so good about it?
    Gdiplus.
    CProgramming FAQ
    Caution: this person may be a carrier of the misinformation virus.

  6. #6
    Thanks Ken. On that page it says it works with XP and Win64.. Sort of OT but will programming for 64bit be that much different? It just means that the CPU will process 64bit of data each cycle right? So will variables remain at the current sizes or will they be bigger..

  7. #7
    Yes, my avatar is stolen anonytmouse's Avatar
    Join Date
    Dec 2002
    Posts
    2,544
    Thanks Ken, I don't mind using it if Borland can handle it.

    >>On that page it says it works with XP and Win64<<

    It is a redistributable for other platforms.

    >>So will variables remain at the current sizes or will they be bigger<<

    sizeof(type *) == sizeof(size_t) == sizeof(ptrdiff_t) == sizeof(time_t) == sizeof(WPARAM) == sizeof(LPARAM) == sizeof(INT_PTR, LONG_PTR, etc) == sizeof(HANDLE, HICON, HWND, etc) == 8 bytes == 64 bits.

    Most other types remain the same including short, long, int, DWORD, etc.

    Therefore, you can no longer stuff a pointer into a long or DWORD.
    Last edited by anonytmouse; 03-10-2004 at 11:26 PM.

  8. #8
    Whaa?? How will we pass pointers around then?

  9. #9
    erstwhile
    Join Date
    Jan 2002
    Posts
    2,227
    Getting ready for 64bits. This page, in particular, should answer your last question.
    CProgramming FAQ
    Caution: this person may be a carrier of the misinformation virus.

  10. #10
    Well it doesn't seem to bad actually. I'll have to think about porting my controls and program to 64bit this year I guess..

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Errors including <windows.h>
    By jw232 in forum Windows Programming
    Replies: 4
    Last Post: 07-29-2008, 01:29 PM
  2. failure to import external C libraries in C++ project
    By nocturna_gr in forum C++ Programming
    Replies: 3
    Last Post: 12-02-2007, 03:49 PM
  3. Dev C++ 64bit support
    By code2d in forum Tech Board
    Replies: 6
    Last Post: 01-03-2007, 05:23 AM
  4. Dev-cpp - compiler options
    By tretton in forum C Programming
    Replies: 7
    Last Post: 01-06-2006, 06:20 PM