From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: Child-frame can not move to proper position when run "env GDK_SCALE=2 emacs" Date: Thu, 11 Jan 2018 11:54:34 +0100 Message-ID: <5A57426A.8040607@gmx.at> References: <87wp0sy3bq.fsf@163.com> <5A53B5C5.70105@gmx.at> <87608c54xw.fsf@163.com> <5A548EAA.3060908@gmx.at> <874lnvi9mm.fsf@gmail.com> <5A55E8C3.9090303@gmx.at> <87vag9j097.fsf@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1515668006 27366 195.159.176.226 (11 Jan 2018 10:53:26 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 11 Jan 2018 10:53:26 +0000 (UTC) Cc: Feng Shu , emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 11 11:53:22 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZaTx-0006At-Cq for ged-emacs-devel@m.gmane.org; Thu, 11 Jan 2018 11:53:13 +0100 Original-Received: from localhost ([::1]:34060 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eZaVw-0000Pp-S7 for ged-emacs-devel@m.gmane.org; Thu, 11 Jan 2018 05:55:16 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47617) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eZaVd-0000LG-Mr for emacs-devel@gnu.org; Thu, 11 Jan 2018 05:55:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eZaVY-0007ko-PS for emacs-devel@gnu.org; Thu, 11 Jan 2018 05:54:57 -0500 Original-Received: from mout.gmx.net ([212.227.17.22]:49629) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eZaVY-0007kA-El for emacs-devel@gnu.org; Thu, 11 Jan 2018 05:54:52 -0500 Original-Received: from [192.168.1.100] ([213.162.73.239]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MVNWU-1eMvpS1kBa-00YeU4; Thu, 11 Jan 2018 11:54:44 +0100 In-Reply-To: <87vag9j097.fsf@gmail.com> X-Provags-ID: V03:K0:KslZbamD1sQswdviJsxNXde6ho8XTD/VHiu9PE5G9+7HxoEpxkL 25MxnQnHpv4Q2X6QbxfYJi/Droot8rxtPLPD6WQLOja2LAL1Qzf/+OoFoWJEmfiuPcVLB2B 2FTXw6j9UqUJSVKGkVJ54eKWVA2w7FAJ6uUgPvlLHvoQH8HCMJzx7N/vfOS+bl45i3rKJgk beA4Ew9fHgX8HjETQdCXg== X-UI-Out-Filterresults: notjunk:1;V01:K0:LIKuEwVTGsc=:gtC23YrjYRb4w6wEDVuhIg lBftBOlYdLskWjByKGT+/JmAmHl1o/XyMPqLSuiwfL6RMMpc5JDja3P7iZOym0KMDiaziI7yk ky6yGTKhGwaizTD8NvJO7/ySy4aaBUl2rUC3sEQcQiVOkW/SSnXh8FbFr5dHOOScpDK/e0XkG JUpno9ToRuqRS0TN59Qvbp19vY5agTgmX4RQ1B0HQdTSux9ImBej4pNf6WkmtG/fjBRiwN52i mw/6zyAr2gullaYXCnddsF1dH3OJ+u3wPieeAZWLr+zk93P3N8Lcf0D2na9jzsOPTpqDcDHzL HVK1m93s2V3K9xOByXTLFd+0wcwR1KP9gLnkebTtKgwqHN/nIFg/QQnA0qFriCqPB1NjbftL8 mwaR8UJfdVg2wXrGZTCIZvRL1wbsNkCVdlxzmo/HWpM3EjXz5sXcoad9z0OhPHez9eT3kUFhW 3Dqzk85zx4P5qvMy8RqXF85abED8UujABK3JK0eFzRBKyWrgREdm692s98dcc+pE5Eb1Yx2/q sUf3y49/2YzlW0q5+TTSEHyMsZvyD5yKfqqnmy+XnUCFaCMwNXPeUA+Wk7uABKtUpOhAGzYW3 /V4tl9PrLMab6vAed5hVQcr5aQPQpsx4nOzWdXUZRmbs3D+6FXxc/4QnVGz1kIFvbXmxg8sEK tEXHRoetg0Nz20jEokZyTSN5LN09MIC1i8WMfWJSR4tl9XRC6g2emnAcVdhQdAv1yWF6FlIu3 JEHXHUzeBxYyfkJPZ0vlqq4qxa/AeE/te+z6UMQ+3OYrZc9fcG5Fy1L5FCKt6Jzg62s3mjYo X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 212.227.17.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:221828 Archived-At: > That depends on what you mean by 'this'. If you mean 'Emacs always > works in pixels regardless of scaling', then 'Coordinates and Windows' > in windows.texi would be a good place. I'm just not sure we can > guarantee that yet (I know that e.g. frameset-restore misbehaves in > the presence of scaling, and I haven't tracked down why yet) I meant when and where programmers have to be aware of the presence of scaling. If we can make scaling completely transparent, they probably can ignore this issue. If we can't or there are still unsolved issues (like the one with the frame size changing when enabling or disabling scroll bars) we should mention it somewhere. martin