Olaf Oh I did get the information but not from an official source. I got it on some blog. It's not that I don't trust unofficially sources but MS documentation is usually very thorough which is why I prefer to find certain types of information in the MSDN docs. Blogs and forums don't typically cover everything there is to know about a particular data type, class, interface etc. After using more than a dozen programming languages and writing millions of lines of code, I decided to make Basic and JavaScript language my future research direction and the focus of my work.
Originally Posted by Niya I stopped taking you seriously when you made these statements. You are a. NET evangelist, you do not waste opportunity to talk against VB6. Personal or not personal, that's the thuth. What you are after is to demoralize people here. Yes, I don't like what you do. I agree with Eduardo- here. It's been 8 days since the OP has posted They are either gone, or simply reading through the replies and watching, or somehting LEt's not turn this into another holy war.
There's plenty of other threads around here for that. Stick to the question at hand and try to be objective about it. If you can, go start your own thread and flan the flames of your evangelism somewhere else. Originally Posted by Eduardo- You are a. I have zero problems with anyone who loves VB6 but objectively speaking, VB.
Net is much better. That's the truth. I have been getting into these debates on this forum since I got here and in all those years I have not heard a single thing that would convince me that VB6 is a better choice than VB. Net for anything. The only thing I can think of that VB6 has that is better is it's native code compiler which Olaf proved to me many years ago has the ability to produce very high performance code comparable to the best C compilers. But this is just one thing and it's too small a thing to justify any argument that VB6 is better.
Most people who use VB6 are writing business applications. No one is thinking about squeezing every ounce of performance out of the CPU for a pay roll application. They just want to knock it together quickly and get paid. Net is better at this. Originally Posted by Niya I have been getting into these debates on this forum since I got here and in all those years I have not heard a single thing that would convince me that VB6 is a better choice than VB.
There are probably many things, but let's talk about one: Using scales in twips is much more convenient than pixels for making applications DPI aware. Anyway I have no idea how. Perhaps it has something totally automatic, transparent and ready to go it is what I would expect from a new language Codebank projects. Originally Posted by Eduardo- Anyway I have no idea how.
Perhaps it has something totally automatic, transparent and ready to go it is what I would expect from a new language Originally Posted by Eduardo- PS: Have you already studied the advantages of using twips? DPI and screen resolutions are very involved topics. There is no one size fits all in this arena.
Narrow it down a bit and give me an example of a problem in that space you've had to solve using Twips and I'll look into how. Net does it. Being DPI aware is actually a quite narrow topic. I realize you don't know about it, so I suggest reading this tutorial. At least read a bit, until you get the main concepts the tutorial goes into many details for VB6. And if you have specific questions, just ask. Last edited by Eduardo-; Jan 20th, at PM. That doesn't answer my question.
That day I actually did spent at least 2 hours looking into it. I even went so far as to experiment with it a bit. Because despite what you might believe, I do listen to other people's points to try and see where they are coming from.
I spent a fair amount of time that day trying to figure out how what you gained by using Twips in VB6. Ultimately, I wasn't able to find a problem. The only problem I've discovered in all this is that when you change the scale and layout settings in Windows 10, your apps can get a little blurry but nothing I or any of our clients wouldn't be able to live with.
So I am asking Give me an example of how Twips helped you solve a problem. Because as far as I can tell, Windows applications in general, regardless of what they were written in, seem to have no problem dealing with different size monitors, resolutions or DPI settings.
I have never had a reason to consider DPI when writing any program. The biggest challenge I've ever had when it comes to dealing with DPI or different resolutions and whatnot is making my Forms look reasonable on multiple resolutions and I have found ways to deal with these issues before that never involved me having to dip into DPI awareness or using Twips.
I remember even back when I was using VB6, I had to solve quite a few layout issues mostly with writing custom controls. I certainly didn't need Twips to solve them it, in fact it, I remember that got in the way quite a bit. Towards the end of my tenure with VB6, I had gotten into the habit of setting the ScaleMode on everything to vbPixels.
I just didn't want to deal with Twips anymore. They were just getting in the way when I had to do complicated layout calculations, especially when the Win32 API was involved.
The Win32 API deals only in pixels. GetWindowRect is the most prominent example I recall from my own experience. These days I'm using WPF to write Windows Desktop applications now and it has very powerful layout capabilities that lend themselves quite naturally to creating Forms that present themselves decently on any resolution so this problem is largely a thing of the past for me.
This is why I am asking you about it because I just can't see it why it's as important as you make it out to be. Help me to understand why. Also, if the blurriness itself is the problem you're talking about. You just have make a couple of very minor changes to a. Net project and that blurriness goes away. It would look crisp and properly laid out no matter what DPI setting you use.
And assuming that this is the problem you're referring to, how can Twips be used to solve this? As far as I understand and feel free to correct me if I'm wrong, the blurriness comes from the fact that an application is not DPI aware so Windows just takes a Bitmap snapshot of the Windows and scales it up so it loses quality.
All my research into this point to application manifests being a solution to this. Where does Twips come into play? Ok, you have to understand that I'm willing to spend much time explaining how to do things in VB6 to someone that does not use VB6 and "hates" it.
But if you spent two hours trying to understand this topic and you didn't do it, I think I'll spend at least ten minutes trying to explain it. The other reason I didn't explain it to you before is because I already explained it in the forum several times, but now I do not feel like it to try to find those posts that in general were answers to people and do not remember their thread titles. But it seems that you already grasped the main idea: the problem is the blurriness.
You say that you don't mind, and your user either. OK, that's one position. It is valid. I have some old programs I left like that. The other is a bit more "perfectionist" if you want. One thing is the screen resolution and another thing is the DPI setting. Some background that surely you already know : The monitors have a native, physical resolution. For example the monitor I'm using now has x physical pixels.
Apart from that, Windows let you specify the resolution, you can use the one that match the physical or another one. So, there is a physical resolution, and a logical resolution.
It is recommended, specially with LCD monitors to use the logical resolution that matches the physical one Windows says "recommended". When you are using a logical resolution that does not match the physical one, the video driver scales everything. But you already know all that. I'm just explaining it to set the ground.
There is something else in monitors and also printers and other devices that are the dots-per-inch. How many dots there are in a physical inch. The printer normally have , , dots-per-inch. Monitors also has dots-per-inch, but the dots are pixels, so they are pixels-per-inch. How many pixels there are in a inch. But Windows does not care much about the real DPI of monitors, that is the same to say that it does not take into account the monitors physical dimensions.
Instead, it works with logical DPIs. That's logical, not physical. To know the physical size you need to use a ruler. For many programs that would mean nothing, because the screen still have the same x pixels, so if you work in pixels it means that you don't care what the final user sets there the DPI setting. But the user is trying to say something, or that the monitor is physically smaller, or that he is not comfortable with the size of the elements in the screen and wants everything bigger.
If you ignore that, you are ignoring a setting by the user. That was the case of Windows XP. So, what would be expected from the apps? That if the user set a higher DPI setting, the program should make every UI element a bit bigger, because or the user has a small sized monitor but not low resolution or the user wants to see every element bigger that is the normal case. The OS itself responded well to the setting change, they prepared it for that, but not most apps.
Developers mostly developed like everybody has 96 DPI. But it seems to me that with LCD monitors, and the tech generation getting old, setting more than 96 DPI started being more common and MS acknowledged the issue. When people changed setting the OS UI elements looked bigger but not most of the programs windows.
Then, with Windows Vista this thing changed. Now the OS will help to make app bigger. Stretching the windows. Something like a StretchBLT for every window that is not prepared to scale properly itself by own code. The result: blurriness. But wait, some developers worked to add code to adapt the program to the DPI, not everyone was ignoring the issue.
OK, if you had your program ready to handle it itself, you need to say it. The default is that you don't. There is where the manifest file comes into play. You need to declare in the manifest file that your program is "DPI aware" that means that whether you are handling it yourself, or that you prefer to show everything smaller but crisp normally the first option.
Then the OS does not scale the windows of your program. But, but VB6 unlike other languages was already quite ready for DPI aware. When it loads the forms and controls in a different DPI, it automatically scales everything regarding to pixels.
And here is were twips appear. What are twips? OK, twips is an unit that measures things in that logical measurement. Not in pixels, but in "logical inches". So, with VB6, if you work in twips, you are already close to declare your program as DPI aware in the manifest file,a dn have a crisp program, enlarging all according to the DPI setting the user chooses. Well, no so fast, there are still some issues, mostly images that are in pixels by their very nature, and also the fonts are scaled automatically by VB6 but in steps, and sometimes they might be a bit bigger or smaller than exact scale so you will need to leave some little room around labels and use the proper alignment.
PS: I guess I spent more than 10 minutes. I'd say it's a waste of time and I would spend my time in, for example, VB. Unless you have a really good argument for VB6 ofcourse.
I wouldnt waste my time learning VB6. I worked with it 10 years ago and I'm still thankful everytime I look at my CV that I had the opportunity to start working in C. VB6 felt like a mickey mouse language. You might do a search on indeed. I find about jobs there as opposed to , jobs on a search for ". VB6 applications are probably still used quite a lot but I believe for new development over the years VB6 has been chosen less and less as a primary platform to develop an application with people opting for.
NET alternatives. In terms of learning it, I would only do this is you need to work with old VB6 applications that will not be upgraded to. NET, or if you are upgrading VB6 applications to. NET then by all means learn it but dont waste to much time on it. I would hazard an educated guess, based on my own experience, that there are many more programmers writing new COBOL programs than new VB6 programs.
VB6 is ten years replaced and, as far as I can tell, no longer supported in any way by Microsoft. There are still products around that are written in it I have two myself but Microsoft have meant to have said that Windows 8 will not work with VB6 programs, also Visual Studio 6 required to build VB6 projects does not easily run on Vista and Win7.
VBA is very similar in syntax and it looks like this will be supported for the next few years at least. My advice: learn VBA if you need it, but only learn VB6 if you have a maintenance project that requires it. It is difficult to suggest other alternatives there are lots!
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Is Visual Basic 6 still widely used? Asked 11 years ago. Active 7 years, 11 months ago. Viewed 7k times. Improve this question.
Nick Nick 91 1 1 silver badge 2 2 bronze badges. Depends on what you need it for? Why would you want to learn it? Learn any other language. Microsoft said in September that there were still several million people using VB6. At my company we still use VB6 every day. I'd suggest looking at it another way. There are plenty of highly experienced VB6 programmers in the market to meet the needs of existing employers. The only exception might be in specialized fields where VB6 is still popular but other less-widely held skills are also needed.
We still have a lot of VB6 code here, but when we're recruiting we don't look for VB6 skills particularly. We reckon those of us with greying hair can easily help bright new hires get to grips with VB6, provided they can program.
Please check out the book below. This book is authored by our tutor, Dr. It was used as a textbook by the University of Wesleyan. Besides that, this book has been used in high school and university computer science courses all over the world. You can certainly use it for your VB projects reference text.
Based on this book, you can also write reviews using educational service. Please check out this book. Preview the book.
0コメント