Posted: Fri Dec 07, 2007 9:08 pm
QB will never require you to change your code because a new version hasn't been released in over a decade. FB is ever-evolving (or ever-mutilating, whichever term you want to use) so I guess it's never going to stay steady until the team manages to nail down some hard plans and STICK TO THEM. IMO, the current compiler needs to be dumped to the side of the road if they want to make it a GCC frontend, but that won't happen. The way it is now, it could never actually BE a GCC frontend; you have to design your compiler to work that way from the ground up, and it wasn't.
I seriously dislike Galleon's effort, but I'm not going to call him juvenile names for making an effort. If people like it, so be it...I'll just never use it.
You can do fullscreen graphics in VB with ease...or at least in VB6. I don't touch vb.net so I can't comment on that, but doing fullscreen in VB6 is as easy as using a couple of simple API calls (EnumDisplaySettings to get the current settings and ChangeDisplaySettings to set new ones; use the CDS_FULLSCREEN constant in dwFlags to set the mode to fullscreen, but it works best with a form BorderStyle of 0). I've been doing it for years.
I seriously dislike Galleon's effort, but I'm not going to call him juvenile names for making an effort. If people like it, so be it...I'll just never use it.
You can do fullscreen graphics in VB with ease...or at least in VB6. I don't touch vb.net so I can't comment on that, but doing fullscreen in VB6 is as easy as using a couple of simple API calls (EnumDisplaySettings to get the current settings and ChangeDisplaySettings to set new ones; use the CDS_FULLSCREEN constant in dwFlags to set the mode to fullscreen, but it works best with a form BorderStyle of 0). I've been doing it for years.