From dpkreil@gmail.com Thu Jan 14 01:15:17 2016 Received: (at submit) by bugs.x2go.org; 14 Jan 2016 00:15:18 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,HTML_MESSAGE, T_DKIM_INVALID,T_HK_NAME_DR autolearn=ham version=3.3.2 Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id D4EB05DB06 for ; Thu, 14 Jan 2016 01:15:16 +0100 (CET) Received: by mail-wm0-f43.google.com with SMTP id f206so397553769wmf.0 for ; Wed, 13 Jan 2016 16:15:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:from:date:message-id:subject:to :content-type; bh=wg137PUIpLLX7IhG0/53FF0cnFvPBG5TwELhXX8t/fk=; b=i9j+VdDZG24+E6u1R8sI902sgYTdEHaOfd78Uybmvtk5wspvlwqSLdXhUp4F02OmU2 YVE2JkB31IjSg7ISRFEPo6kEQWYvwpxDBjd84XiN2mHgbmp3LrRdCDLyyD7pyEcGKZ4X 58tvWPAHypPmhyJLvx5Rmfo0NLQ1a7Q1inSK34XBTWM2n+1IZ3LA+N1jVR4/G+CTsMue hvbY1q/CuUGlUtp1CbAl2F2qn/su26GIxvYhpKA4ANYZRHnuaSW/dY18QHzmFhjwc5yN ycpEcMyFKazu1hx/BLi3oo0NP38vJt4lSV9MOZbwMTVECu8tUXMy1ou+aRdhWy9Pp6kC THlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:sender:from:date :message-id:subject:to:content-type; bh=wg137PUIpLLX7IhG0/53FF0cnFvPBG5TwELhXX8t/fk=; b=DSS0Q1x24mBz9fQ0QPU2jyKP0rBWvfMtoH1YVSge1f9fH06PNbH7NHHL8YtquLGcF8 zELXe4mjG4iSYevBW1cT38jVyDJxo0vrR6SG28FqcIuzykpBNMSW9Ijog5JibobVWbuk lN+WfLgpIMy87ihzag6mzA9elBx4KyGG3Qu/g2RPpptaNH7YvpvZyxe3beuPy9fW1GtH 60eV1ZGW6d+G7gGbNRnIvmrfxUMAkQrlLseJbCdWlWV0mJmWXrApc2PFTPS82wlP1ckE ijw6GzqPyf6UX+chsNhGCcHrcktSKtcVur9hBUdxGL9PU6JaBXgVLZHhT+aXhiS5ZkTs ljzw== X-Gm-Message-State: ALoCoQlobo/k+YFutUoRacVEwFxdbmEBYlKLOX+uzsBhClEA0Ou6IL0qRJ/3IO8uikBNdPrdeo+oucZDhwEJXRLUX4r/MMyP/Q== X-Received: by 10.28.98.133 with SMTP id w127mr1559206wmb.4.1452730516495; Wed, 13 Jan 2016 16:15:16 -0800 (PST) MIME-Version: 1.0 Reply-To: boku@kreil.org Sender: dpkreil@gmail.com Received: by 10.27.172.83 with HTTP; Wed, 13 Jan 2016 16:14:37 -0800 (PST) From: "Dr. D. P. Kreil (Boku)" Date: Thu, 14 Jan 2016 01:14:37 +0100 X-Google-Sender-Auth: 3nYW9WJq6DDfMbEtQ93LBfPTZz8 Message-ID: Subject: PyHoca-GUI hard limit on session screen size (x max = 3000) To: submit@bugs.x2go.org Content-Type: multipart/alternative; boundary=001a1148d85263e2c70529402ef3 --001a1148d85263e2c70529402ef3 Content-Type: text/plain; charset=UTF-8 package: pyhoca-gui version: 0.5.0.4 When adding a new session in the profile manage, the dialogue apparently enforces limits. I have a three screen configuration of 3x 1200x1920, so an x-size of 3600 or even 3500 is perfectly reasonable to request, yet the GUI limis what I can enter to 3000. Notably, the standalone x2go client does not have this problem, and sessions with screen sizes > 3000 work with no problem at all. I just cannot request them through the pyhoca-gui. I'm running this on a Windows client but I would be surprised if this would not apply to all client o/s variants. --001a1148d85263e2c70529402ef3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
package: pyhoca-gui

version: 0.5.0.4

When ad= ding a new session in the profile manage, the dialogue apparently enforces = limits. I have a three screen configuration of 3x 1200x1920, so an x-size o= f 3600 or even 3500 is perfectly reasonable to request, yet the GUI limis w= hat I can enter to 3000.

Notably, the standalone x2go client does no= t have this problem, and sessions with screen sizes > 3000 work with no = problem at all. I just cannot request them through the pyhoca-gui.

=
I'm running this on a Windows client but I would be surprise= d if this would not apply to all client o/s variants.
--001a1148d85263e2c70529402ef3--