Search:

You're so adorable.

I'd recommend C# as well as Java. Visual Basic whether it's VB6 or VB.Net are not taken seriously by the rest of the world. Rust is one of the newest languages taking the world by storm and seems to...

I'm pretty sure that VB6 IDE can only understand 8 bit ANSI Strings. Visual Studio 6 was created when Windows itself was still largely an ANSI operating system. If you want to use Unicode Strings you...

64 bit compilation is generally overrated. Unless you're dealing with arrays over 2 GB consistently in your application or trying to use 64 bit DLLS, you really don't benefit from 64 bit compilation....

There are no sides. There is only the truth.

So what are you saying? It takes 15 minutes for the JIT to compile an application when deployed? It takes 15 minutes to install? What are you even talking about here?

My deployment process for...

Not while I am here.

Then stop spreading blatant lies like this:


15 minutes load time? Really? If you don't use it, then you don't know anything about it so stop lying like this.

It was dilettante saying nonsense...

Then stop complaining about MS abandoning VB6. Stop complaining when those of us that like .Net better say it's better. Stop complaining about VB.Net not being like VB6. Stop making "bring back VB6"...

It's funny, I was actually thinking about how Rust was created on top of LLVM. LLVM was the back end compiler. It seems to be a very big deal in the world of language development. There might be a...

32 bit isn't going anywhere, at least not until it becomes the norm for programs to use more than 2 GB of it's personal address space. The advantages of a 64 bit OS has more to do with the OS itself...

I hear you but you're ignoring the big elephant in the room. The world doesn't seem to care. If it did care about this as much as you do, .Net would have died in it's tracks with the likes of...

This is just the way it goes. Technology is always improving and old technology become obsolete. That's life. Even VB.Net's time will come to an end, it has already begun.

I didn't say it wasn't possible. I just didn't know how. My knowledge on Windows and COM in those days were still far too limited to figure out how to do it on my own. Even when I looked up online...

lmao. Ill take it ;)

It's funny, even someone simply saying that may have been enough but noooo. Everyone was talking about how slow it was and that it took years to start. No mention of it's...

If that's the case then just avoid all that entirely and use GetClientRect/GetWindowRect with SetWindowPos to position all your Controls.

A key mistake I made back then was not choosing my words carefully. I didn't realize what I think and what I was actually saying were 2 different things. I also made the mistake of not realizing my...

Whatever, I've lost interest in arguing with you.

None of us wanted it but we needed it.

You're the one that's being ignorant here. What you are completely failing to grasp is that all these common controls and the Forms themselves are built on top of operating system abstractions. Every...

You guys were focused on twips when that had nothing to do with it. All I showed was that in the case of the sample you posted, you could induce the correct behavior whether or not twips were...

I realized it was a waste of time. Because all we ended up doing was going head to head .Net vs RC5. But here's the thing, you had to spend all that time to write that library, I didn't. This is what...

The more I use WPF, the more I fall in love with it. You just feel so powerful, like there is no kind of UI you cannot create with it. It even feels better when you're creating simple UIs with plain...

Ehh....well I expect there are all kinds of gremlins waiting in the dark with this. I don't know enough to cover all the edge cases that would cause it to fail. I certainly don't know enough to have...

Nevertheless, it is very applicable to my case. It's very easy to make an argument that I'm being subjective. I'm just pointing out that I can back up what I say but only to those willing to listen...

I just tested this and it still didn't fail, even with a UserControl. If it's failing for you, I might be missing something. I've attached the project I used to test it.

I'm not getting into this with you guys again. Believe whatever you want.

I can, but I've learned that on this forum, it's a waste of time to try. Instead, I will say that VB.Net is better and leave it right there. If someone comes along who I feel would genuinely like to...

I've always been nice. But nice doesn't mean I'm not willing to speak the truth just because it offends some people. When I say that VB.Net is better than VB6, I'm not saying that to be mean...

SetWindowPos works exclusively in pixels. The only reason I'm using ScaleX/Y is because I'm reading the dimensions of the client area from ScaleWidth/ScaleHeight properties of the Form and I need...

Turns out I was correct. The problem has nothing to do with Twips. Use this:-

Option Explicit

Private Declare Function GetDpiForWindow Lib "user32.dll" (ByVal hwnd As Long) As Long
Private...

As a result of my participation in the other thread where I was researching DPI, I decided to tackle this and see what's up while all this DPI stuff is still fresh in my mind. First I want to address...

You're welcomed. :)

See I'm not such a bad guy after all. :bigyello:

Your question seems to be hinting at concerns over how the XAML is married to VB code. Underneath it all, XAML is just a way of instantiating objects. For example this:-

<Grid x:Name="grd1">
...

Yes, all of these properties are set at design time using XAML. To put it in VB6 terms, XAML is the text you find in frm files that tells you what controls a Form has, where they are etc. This is...

If you've ever worked with HTML/CSS then you've worked with relative positioning before. It's the exact same concept. Minor adjustments are all done with margins and paddings.

In WPF you live and...

That's one of the main reasons but it's goes a lot deeper than that. While a WPF application by default will look exactly like any other Windows application, underneath the hood, they are completely...

I get the problem at 175%.

Well this got out of hand fast:ehh:

Now I realize that I'm not as experience as you when it comes to DPI awareness so maybe I missed something. Maybe I did something wrong in testing. I've attached the two .Net applications I wrote to...