Is there a way to convert a .TIF file in VB6
in [Visual Basic]
|
From: Paul Clement on 1 Mar 2010 11:24 On Mon, 1 Mar 2010 08:41:35 -0000, "Mike Williams" <Mike(a)WhiskyAndCoke.com> wrote: � > � He didn't ask that, troll! He posted to the Classic VB � > � newsgroup and he specifically asked for a VB6 solution. � > � > That's up to him to decide, not you. � � He already DID decide! He SPECIFICALLY asked for a VB6 solution in the very � post to which you were responding. You really are a stupid little boy, � Clement! � � Troll. � � Mike � � Then why did you post a Windows API solution? Or, don't you live by your own rules? ;-) Paul ~~~~ Microsoft MVP (Visual Basic)
From: Mike Williams on 1 Mar 2010 12:58 "Paul Clement" <UseAdddressAtEndofMessage(a)swspectrum.com> wrote in message news:l6pno514sj7c1m47m0o1c3t2tuqnf5m0j8(a)4ax.com... > � The OP did NOT post his question on the VB.Net group. > � He posted it here. Also, he SPECIFICALLY asked for > � VB6 solution. > > Doesn't really matter. .. . . and there we have it in a nutshell. As far as you are concerned the person who posted the original question doesn't really matter. You are a troll, Clement. Mike
From: Mike Williams on 1 Mar 2010 13:07 "Paul Clement" <UseAdddressAtEndofMessage(a)swspectrum.com> wrote in message news:ueqno595slg27gla2jmr8kt0if4ipiguhu(a)4ax.com... > Then why did you post a Windows API solution? > The more stupid things you say, Clement, the clearer it becomes that you are a troll. Mike
From: mayayana on 1 Mar 2010 13:39 > Doesn't really matter. Not all functionality in an application is developed in the environment or > programming language you are using. It certainly isn't in the case of GDI (as you suggested) and in > many instances it isn't the case with ActiveX components (such as WIA). But if you can use > technologies as extensions from VB then it's certainly fair to mention them. > > Ironically, the only time you object is when it's Visual Basic .NET. Sounds like your objections are > rampant with double-standard and credibility issues. ;-) > This is what Karl was talking about in terms of intellectual dishonesty. You've recommended a non-VB solution in a VB group and somehow you manage to turn that upside down and portray it as an attack on .Net! Since you really don't understand concepts you just use them as weapons where it suits you. The objections are to .Net, and only .Net, because nobody else is so rude as to try to sell their products here. I don't remember anyone ever saying, "Well, shucks, you could do that easily if you switch to Java." According to this article: http://www.vbaccelerator.com/home/vb/code/vbmedia/using_gdi_plus/GDIPlus_Hel per/article.asp ..Net's Drawing object is just a thin wrapper around gdiplus. So you're suggesting that somebody change the language and tool they work with so that they can use a superfluous wrapper, with a 300MB dependency, around the same library that they probably would have used in the first place. Come to think of it, that's a fairly accurate description of .Net. :)
From: Paul Clement on 1 Mar 2010 15:10
On Mon, 1 Mar 2010 13:39:52 -0500, "mayayana" <mayayana(a)nospam.invalid> wrote: � � > Doesn't really matter. Not all functionality in an application is � developed in the environment or � > programming language you are using. It certainly isn't in the case of GDI � (as you suggested) and in � > many instances it isn't the case with ActiveX components (such as WIA). � But if you can use � > technologies as extensions from VB then it's certainly fair to mention � them. � > � > Ironically, the only time you object is when it's Visual Basic .NET. � Sounds like your objections are � > rampant with double-standard and credibility issues. ;-) � > � � This is what Karl was talking about in terms of � intellectual dishonesty. You've recommended a � non-VB solution in a VB group and somehow you � manage to turn that upside down and portray it � as an attack on .Net! Since you really don't � understand concepts you just use them as weapons � where it suits you. Actually I'm turning it right side up. I've seen Delphi discussions, PowerBASIC discussions, Realbasic discussions, etc. in this newsgroup with respect to alternative solutions and no one, not even you, raises any objections. Amongst development environments and languages it's only when Visual Basic .NET is mentioned that a select few start raising a stink about it. If you're looking for intellectual dishonesty, there you go. � � The objections are to .Net, and only .Net, because � nobody else is so rude as to try to sell their products � here. I don't remember anyone ever saying, "Well, � shucks, you could do that easily if you switch to Java." OK, reality check. It's a Microsoft newsgroup. It's a Microsoft product. The next version is .NET. You may not accept that, but it's the reality. That said, no one is forcing you to use .NET. I suggest it as an option because ultimately Classic VB will not be one. In the mean time I will continue to help Classic VB developers, and that may mean suggesting Visual Basic .NET interop solutions. Sorry. � According to this article: � � http://www.vbaccelerator.com/home/vb/code/vbmedia/using_gdi_plus/GDIPlus_Hel � per/article.asp � � .Net's Drawing object is just a thin wrapper around � gdiplus. So you're suggesting that somebody change � the language and tool they work with so that they � can use a superfluous wrapper, with a 300MB � dependency, around the same library that they probably � would have used in the first place. Come to think of � it, that's a fairly accurate description of .Net. :) � No, in this instance I'm suggesting they consider reducing the amount of code they have to write and also providing an option for them to move forward in the future. Unlike you (and a few others), I will not deny alternatives and insist they stick with a solution until the day arrives when it's no longer viable. Paul ~~~~ Microsoft MVP (Visual Basic) |