Is there a way to convert a .TIF file in VB6
in [Visual Basic]
|
From: Paul Clement on 2 Mar 2010 00:50 On Mon, 1 Mar 2010 21:21:19 -0000, "Mike Williams" <Mike(a)WhiskyAndCoke.com> wrote: � > � > 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. � � > What is clear is that it was a simple question and the � > best reply you could muster was to call someone a name � � You really are a foolish boy, Clement. Using Windows APIs with VB6 is � perfectly natural and virtually everybody who � is using VB6, as was the OP, and who asks how to perform a specific task in � VB6, as did the OP, would be perfectly happy to accept a solution that � requires them to call some API functions from VB6. Such a solution is � perfectly sensible. Your own suggested solution however, which was to advise � the OP to use a completely different development platform simply because you � did not have sufficient knowledge to provide him with a real answer, is the � mark of an idiot. You are both an idiot and a troll, Clement. And the act of � saying that is not "calling someone names", as you so childishly put it, it � is simply a statement of fact. � � Mike � Yes, well using COM with an external library is perfectly natural and sensible as well and it can be easily done with .NET, regardless of the internal implementation of the library. Unlike you I made no assumptions concerning the OP's aptitude or knowledge or his desire to learn anything new. I certainly don't expect you to consider options outside or your knowledge or interests but you should know by now that you can't read the minds of those you don't know or impose your desires (or lack thereof) upon them. Ignorance is evil Mike. Denying others choice is the work of a selfish, angry and bitter man. Don't be one. :-) Paul ~~~~ Microsoft MVP (Visual Basic)
From: Paul Clement on 2 Mar 2010 00:54 On Mon, 1 Mar 2010 22:47:18 -0500, "Rick Rothstein" <rick.newsNO.SPAM(a)NO.SPAMverizon.net> wrote: � > 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. � � This is going to sound a lot harsher than I mean it to be (so I apologize in � advance), but that is a ridiculous statement to make (in defense of your � initial posting to this thread I presume) within this thread given the OP � **plainly** stated in the Subject and **unequivocally repeated** in the body � of his message that he was looking for a VB6 solution. Please enlighten us � as to how you could possibly construe that to mean "please tell me about � non-VB6 solutions that may exist which could answer my question"? Perhaps someone could clarify what the OP means by a VB 6.0 solution? If it means a solution that must be written in VB 6.0 then the OP is out of luck because all of the suggestions require an implementation that was not developed in Visual Basic. Now, if you chose to extend the solution to libraries created outside of VB 6.0 many options are available, including Visual Basic .NET interop (yes I and many others currently do this). So which is it? If it's the former then why just jump on me? If it's the latter then everyone should be entitled to offer viable suggestions. Or are you going to continue to create different set of standards for different people or subjects? Paul ~~~~ Microsoft MVP (Visual Basic)
From: Rick Rothstein on 2 Mar 2010 01:18 Come on Paul... seriously... do you REALLY believe that giving a VB.NET interop solution is in keeping with what the OP was looking for? Really? Since VB6 provides a Declare statement so that API functions can be incorporated into a VB6, I would say that Mike's (mscir) solution is a totally valid response to the OP's question. I would also say that Shotgun Thom's solution (adding the Microsoft provided DLL) is also a totally valid response to the OP's question as adding DLL's to VB6 is not that foreign a concept. Why them and not your VB.NET solution? Because they both allow the OP to implement a solution using his existing copy of VB6 (which is what he asked to be able to do). Your solution, on the other hand, requires him to purchase some current version of VB.NET and then follow that up by spending who knows how much time learning how to become accustomed to the differing environments before becoming comfortable enough to try and implement your approach. I honestly think you are grasping at straws here trying to defend your original entry into this thread. -- Rick (MVP - Excel) "Paul Clement" <UseAdddressAtEndofMessage(a)swspectrum.com> wrote in message news:cc5po5hcd7ajjf7cjkqqunhb6ieambicvp(a)4ax.com... > On Mon, 1 Mar 2010 22:47:18 -0500, "Rick Rothstein" > <rick.newsNO.SPAM(a)NO.SPAMverizon.net> wrote: > > � > 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. > � > � This is going to sound a lot harsher than I mean it to be (so I > apologize in > � advance), but that is a ridiculous statement to make (in defense of your > � initial posting to this thread I presume) within this thread given the > OP > � **plainly** stated in the Subject and **unequivocally repeated** in the > body > � of his message that he was looking for a VB6 solution. Please enlighten > us > � as to how you could possibly construe that to mean "please tell me about > � non-VB6 solutions that may exist which could answer my question"? > > Perhaps someone could clarify what the OP means by a VB 6.0 solution? If > it > means a solution that must be written in VB 6.0 then the OP is out of luck > because all of the suggestions require an implementation that was not > developed > in Visual Basic. > > Now, if you chose to extend the solution to libraries created outside of > VB 6.0 > many options are available, including Visual Basic .NET interop (yes I and > many > others currently do this). > > So which is it? If it's the former then why just jump on me? If it's the > latter > then everyone should be entitled to offer viable suggestions. Or are you > going > to continue to create different set of standards for different people or > subjects? > > Paul > ~~~~ > Microsoft MVP (Visual Basic)
From: Mike Williams on 2 Mar 2010 03:18 "Paul Clement" <UseAdddressAtEndofMessage(a)swspectrum.com> wrote in message news:k47po591kcri9c8fsuia6pvn6pdf45iej2(a)4ax.com... > Denying others choice is the work of a selfish, angry > and bitter man. Don't be one. :-) Now you really are proving that you are an idiot as well as a troll. The OP did NOT ask for suggestions regarding a choice of alternative development environment. He asked for a solution that he could implement in VB6. Nobody denied him anything, except of course yourself who denied him a real answer to his question and who instead suggested that he should move elsewhere. If you really do think that failing to offer a choice of development environments in answer to a question regarding a specific development environment is "denying others choice", especially when a solution using his existing development environment is available, then you are even more of an idiot that I thought, and if you do not really think that then you are a liar, And, of course, you are clearly a troll. So there you have it. Liar and troll or idiot and troll, one or the other. I have known for some time that you are a troll, but I never had you down as an idiot so I'll give you the benefit of the doubt and put you down as a liar. The sad thing is that with the breadth of knowledge that you obviously have (except regarding the OP's specific question of course, where your knowledge was clearly limited) you could have been a really useful member of this group. How sad that it has not turned out that way. Mike
From: Tony Girgenti on 2 Mar 2010 09:27
WOW!!! I wish I would have remembered to check the 'Notify me of replies' checkbox. I did not realize all of this was going on. I think the suggestion by Shotgun Thom is the best. The sample program using the Wiaaut.DLL works great and is very simple. My only problem is that many of the .TIF files i am trying to convert are multipage documents. They were originally created for faxing. When i convert a multipage .TIF file to any other format using Wiaaut.dll, it only keeps the first page in the output. So, i have decided to create multiple .JPG files from one multipage .TIF file. That will work for me presently. I want to thank everybody for all of their suggestions and micr for helping me through personal emails. micr spent a lot of time researching this issue and kept me informed as to what he found. Thanks, Tony "Shotgun Thom" wrote: > On Feb 27, 6:37 pm, Paul Clement > <UseAdddressAtEndofMess...(a)swspectrum.com> wrote: > > On Sat, 27 Feb 2010 09:02:01 -0800, Tony Girgenti <tony(nospam)@lakesideos.com> > > wrote: > > > > ¤ Hello. > > ¤ > > ¤ I want to develop a VB6 program to convert a .TIF file to a .JPG file.. > > ¤ > > ¤ Is that possible using VB6? > > ¤ > > ¤ Any help would be gratefully appreciated. > > ¤ > > ¤ Thanks, > > ¤ Tony > > > > It's pretty easy to do in Visual Basic .NET but I'm not aware of any code > > solutions in Classic VB that don't implement a third-party component (and the > > Kodak Imaging libraries are no longer included in Windows). > > > > Paul > > Frankly, nothing is easy to do in .NET. Paul obviously doesn't know, > or conveniently forgot, that Microsoft replaced Kodak with WIA > (Windows Image Acquisition Library). With WIA you can easily convert > between TIFF and JPEG (or png, bmp, etc.) and, btw, do lots of other > stuff like scan, print using photo print wizard, etc. all in VB6. > > It's free. Download at: > > http://www.microsoft.com/downloads/details.aspx?familyid=a332a77a-01b8-4de6-91c2-b7ea32537e29&displaylang=en > > . > |