Hi Dark, As Phil wrote a little earlier David Greenwood released a long list of changes in version 4.0 around three or four years ago. Unfortunately I can not lay my hands on that particular e-mail, but I can say a lot of the changes were pretty substantial. Its not a simple case of David just rewriting Lone Wolf 3.0 in a new programming language and calling it version 4.0. There were some definite changes he had in mind back then, and I'm sure if he wants to make version 4.0 a success he'll be certainly adding most if not all of those advertised changes in version 4.0.
As to your point about work arounds for Visual Basic 6 it is true for the moment, but I've been a programmer for nearly a decade. I can say from experience that basing your code on a deprecated language and technology in the hopes it will remain compatible or will always serve your needs is never a good idea. Yeah, Visual basic support still works now, but if you have an oppertunity to rewrite using the current APIs or languages for the target platform its always a good idea to do so. There are plenty of reasons for switching. For example, when I began learning Visual Basic .NET the intro of the book I was reading did a side by side comparison between VB 6 and VB .NET. I don't have the time to explain them all here, but what the author basically did was point out various issues and real world problems VB 6 developers ran into with the language and how VB .NET addresses those issues. Its things like that an end user such as yourself wouldn't necessarily take into consideration, but a developer might well have good cause to switch from VB 6 to VB .NET. Bottom line, if Jim Kitchen, Aprone, or anyone else feels Visual Basic 6 fits there needs that's fine. However, I'm just a little tired of seeing people complain about Microsoft's decision to remove Visual Basic 6 support from Windows 7 and later versions when they don't even know Microsoft's reasons for it. Before you start calling them lazy perhaps you should consult MSDN and other resources to get Microsoft's side of the issue rather than firing off your opinions half-cocked. Its certainly not as simple or as straight forward as you make it sound. Basically, what I'm saying here is there are two sides to every issue and I think Microsoft at least deserves to be treated with respect and as professionals who know what they are doing. Cheers! On 12/11/11, dark <[email protected]> wrote: > Hi Phil. > > Out of interest were there any major gameplay changes associated with lone > wolf version 4? > > while I see the point, frankly just because microsoft are too lazy to add > backward compatibility into windows doesn't mean there won't be ways around, > and in the case of vb applications it seems that there are already pretty > solid ways of running them on windows 7, which is why developers like Jim > and Aprone are writing games in vb 6 stil (and I don't mean the hole virtual > system emulation mallarchy either). > > So personally, ---- and not just because I'm stil running xp (my computer > afterall can't last forever), I am rather more interested in what possible > gameplay changes or additions version 4 might have, especially if it's being > sold as a separate game. > > Then of course what about the 92 custom missions for the game? > > personally I'd be more in favour of David writing a sequal rather than a > version upgrade to the game, with significant gameplay changes, and leaving > lone wolf version 3 as the distinct lone wolf. > > beware the grue! > > dark. --- Gamers mailing list __ [email protected] If you want to leave the list, send E-mail to [email protected]. You can make changes or update your subscription via the web, at http://mail.audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/[email protected]. If you have any questions or concerns regarding the management of the list, please send E-mail to [email protected].
