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.

I never could get GDI+ to work with Dev-C++ either.

Thanks.

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

Quote:

---

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....

Quote:

---

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).

Quote:

---

Originally posted by Mithoric
GDI+ eh, what's so good about it?

---

Gdiplus.

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..

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.

Whaa?? How will we pass pointers around then?

Getting ready for 64bits. This page, in particular, should answer your last question.

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..