Matrix login procedure messing with Windows Forms scaling

Csharpie

2017-04-28, 09:38 #1

Member since Apr 2017 · 2 posts
Group memberships: Members

Show profile ·

Link to this post

Subject: Matrix login procedure messing with Windows Forms scaling

Hello,

I am currently developing a small project based on the MatriX dll, using a regular C# WinForms application in VS2015.

My sample code looks like this:

using System;
using System.Windows.Forms;
using Matrix.Xmpp.Client;
 
namespace WindowsFormsApplication1
{
    public partial class Form1 : Form
    {
        String lic = @"MyVerySecretLicenseKey";
        XmppClient xmppClient = new XmppClient();
 
        public Form1()
        {
            Matrix.License.LicenseManager.SetLicense(lic);
            InitializeComponent();
        }
 
        private void button1_Click(object sender, System.EventArgs e)
        {
            openXmppSession();
        }
 
        private void openXmppSession()
        {
            xmppClient.SetUsername("testuser");
            xmppClient.SetXmppDomain(Properties.Settings.Default.serverAddress);
            xmppClient.Password = "testPassWord";
            xmppClient.Open();
        }
 
    }
}

It works fine, but on Windows 10 HiDPI-Devices (where scaling is set to 200% by default), it breaks the rendering of the window. You can see the result in the attached screenshot, taken from a Surface Book.

I suspect this has something to do with the license window, which would normally appear at this point, but gets suppressed since a valid license is provided...

Regards!

The author has attached one file to this post:

matrix.png 16.7 kBytes
You have no permission to open this file.

This post was edited on 2017-04-28, 10:44 by Alex.

Alex

2017-04-28, 10:06 #2

Member since Feb 2003 · 4449 posts · Location: Germany
Group memberships: Administrators, Members

Show profile ·

Link to this post

Can you use the MatriX light package?
This comes without any dialogs and references to winforms.

Alex

Csharpie

2017-04-28, 11:06 #3

Member since Apr 2017 · 2 posts
Group memberships: Members

Show profile ·

Link to this post

Hi Alex,

thank you for the quick response, a first test looks positive

Are there any mentionable drawbacks on this version?

Regards!

Alex

2017-04-28, 12:28 #4

Member since Feb 2003 · 4449 posts · Location: Germany
Group memberships: Administrators, Members

Show profile ·

Link to this post

The non light version has references to WinForms and WPF. The main reason for having those references is to make it a little easier for programmers which write GUI applications with MatriX. Because then MatriX internal invokes all the threads back to your main UI thread. So you don"t have to invoke any event yourself.

And there is a property in the vcard which gives you the user avatar as a System.Drawing/Image.

So, not really any drawbacks. You can easily invoke events yourself when required, and getting an image from the Base64 vcard data is also pretty trivial. We can share the code when you need it.

My assumption is that you hit the problem described here:
http://stackoverflow.com/questions/34900791/mixed-wpf-and-…
Because MatriX references SWF and WPF in the full version. Maybe the manifest described from there solves your problem as well.

MatriX only tries to find your GUI dispatcher during the login. It does not execute and other code on your related to scaling.
It could also help when you set the dispatcher yourself, then MatriX will not try search for it during the login.

I hope this helps.

Alex