From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 27B10211FF for ; Fri, 10 May 2024 16:25:34 +0200 (CEST) Received: from mimir.eigenstate.org ([206.124.132.107]) by 9front; Fri May 10 10:22:02 -0400 2024 Received: from mimir.eigenstate.org (localhost [127.0.0.1]) by mimir.eigenstate.org (OpenSMTPD) with ESMTP id e945b933 for <9front@9front.org>; Fri, 10 May 2024 07:21:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=eigenstate.org; h= message-id:to:subject:date:from:in-reply-to:mime-version :content-type:content-transfer-encoding; s=mail; bh=gBFgzanoMhvV ngkczXinsf1Ofig=; b=XyddSPFnQWfS7CqwQPrXLf8cu6An+Wo5PJ/yOkwdgBI8 Ehh1dTauRzVewS1GHB2PvdFzzD76oFmlQM2LNAWSzh/HCTUhT5SiF/RQI+2l8zX1 4I+CyqkLhnqmgeDrhqa5NzwBgwt98mmZoUvitfBk2MteFfO8t20xnAyH6Gpo8+o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=eigenstate.org; h=message-id :to:subject:date:from:in-reply-to:mime-version:content-type :content-transfer-encoding; q=dns; s=mail; b=gLnK6MG8dtTJao83HbS W6uXbtHlC16OyIjZwEDci1y48MkHzvVJjpHtpOI9gJ5NSOZJknWy/Y1wNOWakgZg pQ8PsQFRYtWbpf8KLlxlQjW1/U6BvZ63ruf0WyZUL1DLLx8ZfDNJszaNslSwn81+ uoD/tXooufRTEIvLxwomFYUE= Received: from abbatoir (pool-108-6-24-2.nycmny.fios.verizon.net [108.6.24.2]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 5ab0758f (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Fri, 10 May 2024 07:21:56 -0700 (PDT) Message-ID: <311B1A9C352DEB4C4D8AA17ED1105F07@eigenstate.org> To: 9front@9front.org Date: Fri, 10 May 2024 10:21:55 -0400 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: database just-in-time element lifecycle-based locator Subject: Re: [9front] [PATCH] rio: resize border and scrollbar based on font Reply-To: 9front@9front.org Precedence: bulk Quoth Stanley Lieber : > On May 10, 2024 10:10:29 AM EDT, Jacob Moody wrote: > >On 5/10/24 01:20, Kurt H Maier wrote: > >> On Thu, May 09, 2024 at 07:14:06PM -0500, Jacob Moody wrote: > >>> > >>> we do not currently do any sort of scaling in the UI for larger displays. > >>> I think we should be looking at a more general solution to this problem, > >> > >> scrollbars and borders should be arguments passed to rio and then > >> exposed in env or elsewhere > >> > >> every other attempt at 'general solutions' to ui scaling have been > >> miserable goddamn failures and I really really don't want to live > >> through it again > >> > >> khm > > > >Alright then where's you're code for a solution here? I don't > >want arguments to every fucking program for scaling. > > > > > > rio provides the borders, so every program in that rio that uses rio's borders would inherit the same settings. > > sl this is, unfortunately, not true, and is one of the uglier warts in rio. Both rio and the programs agree by convention that rio will paint into the outermost 4 pixels of the window. Programs will explicitly subtract 4 pixels from their drawing region, which rio will later paint over. Unless they're running outside of rio, in which case they will subtract off 0 pixels.