Re: No Win32Lib Drag and Drop example OR IS THERE ??
- Posted by mattlewis (admin) Nov 09, 2011
- 3173 views
So let me suggest a few things again, as Derek is doing whatever he is doing for Selgor per this thread, what might save everyone (including Derek and friends) some time in the long haul as the lib is further developed. Then Selgor (and i and anyone downloading from user contribs) can finally count on the newest version of win32lib always working with older code.
1) put the old function and procedure names back into the current win32lib, in a way they call the new code transparently to the user, but operate apparently the same olde way they did 5 years ago. This will save patching the olde bugs.
I think Derek has gone to a lot of trouble to maintain backward compatibility for some time, which probably explains his comments. If you look at the current library, you'll see compat01.ew and compat02.ew. These are full of deprecated bits of code that allow older programs to continue working.
2) if a funct or proc name is the same as 5 years ago but takes different arguements, Eu v4 now has a way of dealing with that, so if the args passed fit win32lib of 5 years ago, perform as if win32lib of yore, else perform as new.
Yes, I suspect that you might start seeing default parameters used something like this in new development.
3) And/or, set a var that tells the current win32lib which previous version to act like.
Yes, the new ifdef stuff can be used for this sort of thing. Obviously, it makes library development a lot more difficult, so I suspect that if it gets used, it may happen on a case by case basis (if at all). I've been working on Win32Lib in an attempt to port it to run on 64-bit windows, and it is a big, complicated bit of code.
This is usually where the humans jump in and say "do it yourself" or start a character-disparaging name-calling flame war. Proceed.
LOL 
Matt
