From: "Doug Bissett" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPS id 1326225 for lswitcher-dev@2rosenthals.com; Wed, 25 Nov 2020 15:12:11 -0500 Received: from [192.168.200.201] (port=48212 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1ki192-0000xx-0d for lswitcher-dev@2rosenthals.com; Wed, 25 Nov 2020 15:12:04 -0500 Received: from mail-pf1-f181.google.com ([209.85.210.181]:35348) by mail2.2rosenthals.com with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1ki149-0005nD-2X for lswitcher-dev@2rosenthals.com; Wed, 25 Nov 2020 15:07:01 -0500 Received: by mail-pf1-f181.google.com with SMTP id e8so3390976pfh.2 for ; Wed, 25 Nov 2020 12:07:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telus.net; s=google; h=message-id:from:to:date:reply-to:in-reply-to:references:priority :user-agent:mime-version:content-transfer-encoding:subject; bh=1zGvbHPX3GlcdjPxB7L2Qh9gpiEZUJnTDcW3pQiJquc=; b=KaDZy1Gi6eXOvN79z5nmuqElgx6rrzmtL19fcI5tG10glneTlR84ed3pHGT7LTJJ7u fDltd+sM5xUU5TCjvVSAt6MpLYO2RdZ/RWHSgyMxlfie851wVBujTBrKk0g2JIJOlCdk fWrsiNLXRvMiR7bHpN4qsJWL3cKFhK82U9NTtdW4tOyMm7i7BJFsiuObz6o1JcoL9FrL 8XeGRTq7mm+Jp445TXiXPT9yUsTSh5KZV1kE9T0cADwuTKQIdZcfBSKH3Mtr5Ihh+qYb BY+rSpvCaFYF6/daA4d+VqVlRSLH6MzmGF4YeFGGMsL6W+nE1V/JhvS/iDzEtx0UVZ/m V5PQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:from:to:date:reply-to:in-reply-to :references:priority:user-agent:mime-version :content-transfer-encoding:subject; bh=1zGvbHPX3GlcdjPxB7L2Qh9gpiEZUJnTDcW3pQiJquc=; b=KDBnZha3GWAiFmm2JBlYu1fQwp5W1up4tyqsBaOtAbAYXsqz+8WBv2z1LVkmGQkeT5 bZdWD+TrQRwe4cJpENFPEJfneUYewG31q2pRKUwyniwrO9/ckcQS9SkE3Shq6Dd5kf9v UegYlf6HAmXkapwuP/8MVbaGkbgNkDBVU2g1GSkCeQvqWT81vXmwGLe8nmnua6Zv7lSU 6NFlj9NvWxJFHdClTe4zRVGDtxurG9aMqqNojnXp5y77gVFAwSAFPq9b259y+l9Tzf51 llsIvIn7Ht2azuXn+JaKyqVHgmpV6IFLlxu+d9IcYYLbN+RUUkozmpaniJ/ozHJvstYU z4Ow== X-Gm-Message-State: AOAM5333EJdPC0HTNVco/4XufGVftF5Q/Nh0yHs+H+czXY3nrUz1dgcv Kxskqhqr+58enpnsrkoVIfJiKu3mn4muDhR/ X-Google-Smtp-Source: ABdhPJwp26hlWAjUbKgvDAFwxERcmhALtkaAFuJ8hnEJGnbRndOdMmsJJp02WJUSaEh+LnzzTWsbwg== X-Received: by 2002:a17:90a:a506:: with SMTP id a6mr6222753pjq.82.1606334820262; Wed, 25 Nov 2020 12:07:00 -0800 (PST) Return-Path: Received: from IREBBS7 (d75-158-37-13.abhsia.telus.net. [75.158.37.13]) by smtp.gmail.com with ESMTPSA id f134sm2727535pfa.208.2020.11.25.12.06.59 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Nov 2020 12:06:59 -0800 (PST) Message-ID: <002.803e0000f4b8be5f.038@telus.net> To: "lSwitcher Developers Mailing List" Date: Wed, 25 Nov 2020 13:05:08 -0700 (MST) Reply-To: "Doug Bissett" In-Reply-To: References: <5FBE9F80.1040406.ref@yahoo.es> Priority: Normal User-Agent: PMMail/3.25 (os/2; U; Warp 4.5; en-CA; i386; ver 3.25.00.1990) X-Mailer: (Demonstration) PMMail (Beta 2) 3.25.00.1990 for OS/2 Warp 4.5 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Subject: Re: [lswitcher-dev] XCenter widget On 2020-11-25, at 19:16:32, Alfredo Fernández Díaz wrote: > > Hi, > > I am a keyboard person, so to me lSwitcher's "main" act is the PM popup, which lets me handle a lot of things without ever > reaching for the mouse. Although I use the taskbar, I mostly ignore it, and so I am rather unacquainted with the widget. Now > that we have been discussing adequate labeling, something I am always up for, I decided I'd give the widget another go, and I > have some suggestions. I am a mouse person (I hate typing). Mind control would be even better, but the driver has not, yet, been developed. > -First, I don't think the widget should list the XCenter(s), just as the window list widget does: basically, an XCenter entry takes > up room in the lSwitcher XCenter widget, and clicking on it accomplishes nothing (please correct me where I go wrong!), so I > think this should go. An obvious, quick and dirty solution is to add "*XCenter*" (to account for most variations) to the filter list, > but I don't really see the point of it being there in the first place. A click, or two, and they are filtered. The point would be, that somebody might want them there. There are other default options that I would like to see changed, but there is nothing wrong with the way it is. Others (perhaps the majority) might want it the way that it is. User choice. Programming by survey, is rarely an ideal thing to do. because everybody wants something different, and nobody will be happy anyway. > I guess you could list and offer to close *other* XCenters from the lSwitcher widget, but "close" is not an option currently > available for XCenters from the widget popup menu. Never even thought about doing that. XCenter close is on the XCenter popup, and that has been added to the widget popup. What more do you want/need? In fact, it doesn't make any sense to offer to close the host of something that you are using. Leave it alone. > -Other tasks popup menu: they all have an "lSwitcher widget" submenu, but out of the six entries in it, only "Properties" > corresponds to the widget itself; another three correspond exclusively to the XCenter (add widget / XCenter properties / > close), and the last two could be attributed to either (help splits, and "delete widget" works for both). I propose "lSwitcher > widget" be renamed to "lSwitcher / XCenter", or whatever you suggest. You know what? Rich spent time making those extra menu items happen, because it is a PITA when they don't. Leave it the way that it is, it is working properly (if not ideally). Remember that a lot of the lSwitcher widget support is done by XCenter, not lSwitcher. That has the added advantage that the widget works like other widgets, with a lot less program overhead (and fewer problems, simply because lSwitcher doesn't need to manage windows, and so on). Sometimes I wonder why the widget is not the only option for lSwitcher. Supporting it would be a LOT easier. > -Finally, with two XCenters an lSwitcher can be added to each, but only the first one will unfold (and an error message pops up > next time you try to open both XCenters). Adding a second lSwitcher to an XCenter is not allowed, OK, but then so it should > be the case on a second XCenter if it won't work. ONE XCenter can have ONE lSwitcher widget. That is by design, and should NOT be changed. There can be more things on the XCenter, that should be opened, not just lSwitcher. Adding it to a second XCenter is really an USER problem, not a lSwitcher problem (it could probably be handled more gracefully, but that is an XCenter thing). On the other hand, other widgets, that are not allowed to have multiple copies running, manage to grey out the option in the XCenter (poorly named, but I can't think of anything better) Create New Widget popup, so a user cannot add it a second time (whether it is the current XCenter, or the "other" one, but that seems to be selectable, under some conditions). lSwitcher should do that, when it is already assigned to an XCenter, whether the assigned XCenter is open, or not. Rich probably knows how that is done. > Best regards, -- **************************** From Doug Bissett's ArcaOS system dougb007 at telus.net **************************** ... I miss the days when everything worked with just an "ON" and "OFF" switch.