Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Wed, 19 Aug 2020 05:54:14 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 07JCiWXI023251; Wed, 19 Aug 2020 08:44:59 -0400 Received: from outgoing-exchange-7.mit.edu (OUTGOING-EXCHANGE-7.MIT.EDU [18.9.28.58]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 07JCiWtw023248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 19 Aug 2020 08:44:32 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 07JCgM4X022781 for ; Wed, 19 Aug 2020 08:42:23 -0400 Received: from w92expo18.exchange.mit.edu (18.7.74.72) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 19 Aug 2020 08:43:23 -0400 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by w92expo18.exchange.mit.edu (18.7.74.72) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 19 Aug 2020 08:44:23 -0400 Received: from NAM04-SN1-obe.outbound.protection.outlook.com (104.47.44.56) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 19 Aug 2020 08:44:22 -0400 Received: from MW2PR16CA0008.namprd16.prod.outlook.com (2603:10b6:907::21) by CY4PR01MB2710.prod.exchangelabs.com (2603:10b6:903:df::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3283.15; Wed, 19 Aug 2020 12:44:21 +0000 Received: from CO1NAM03FT052.eop-NAM03.prod.protection.outlook.com (2603:10b6:907:0:cafe::cc) by MW2PR16CA0008.outlook.office365.com (2603:10b6:907::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3305.24 via Frontend Transport; Wed, 19 Aug 2020 12:44:21 +0000 Received: from mail-oi1-f181.google.com (209.85.167.181) by CO1NAM03FT052.mail.protection.outlook.com (10.152.81.213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3305.24 via Frontend Transport; Wed, 19 Aug 2020 12:44:21 +0000 Received: by mail-oi1-f181.google.com with SMTP id l204so20856237oib.3 for ; Wed, 19 Aug 2020 05:44:21 -0700 (PDT) From: Clint Jay To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 19 Aug 2020 05:44:08 -0700 Subject: Re: [EE] LCD cover materials? Thread-Topic: [EE] LCD cover materials? Thread-Index: AdZ2J9e/25isa9ZWTHKSzJLq/t5cXg== Message-ID: References: <5F3C6823.1000906@narwani.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <5F3C6823.1000906@narwani.org> Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of gmail.com designates 209.85.167.181 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.167.181; helo=mail-oi1-f181.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=sU4QfFS0hqUgwaMIs1Hpb1i0pGso38RbAjmXvofRc58=; b=D3ljw3hFvDCrd20ngT891jum/VgJd2QDBe70d+IAibaMo5N4jw983QxUV3eJv5hEwy mnXnrgx+GbvfPzcET7JtlwBLIEinzIWxQbfYIIeVnEDWfIPtj4rMeoCt6sKjC2h8P+pP wlPScguyXWw3YOjmxYsv1w97n3hx5Uj5Uw1U+WBTMWPXzEyPuxEGebaXBIOrF1gOfTB4 6+aPY2HhikJ8oZ7Uj/GvK1nWKleNoFkkvShysrHkjwUOvj3Xr9QeuA3pJGg5J6mGdmHI 6UpF5iQ/FoEbn8lQZIMyXVadEoCkQ3W+TrjW4S4JqtLSDP7xSTDiSmlf3Ecrk3nrZdCj ei3g== authentication-results: spf=pass (sender IP is 209.85.167.181) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com; mit.edu; dmarc=pass action=none header.from=gmail.com; errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-received: by 2002:a54:4019:: with SMTP id x25mr2964663oie.124.1597841060036; Wed, 19 Aug 2020 05:44:20 -0700 (PDT) x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Anything that stops the touch sensor deforming will prevent a resistive touch screen working so you're limited to thin, flexible sheets, good news though, cheap iPad screen protectors work nicely On Wed, 19 Aug 2020 at 00:47, Neil wrote: > For a device that has a TFT with a resistive touch screen, what does one > put over the display, so that the touch-screen is still usable? > I expect even thin polycarbonate will render the touch screen inoperable. > > Cheers, > -Neil. > > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 Clint. M0UAW IO83 *No trees were harmed in the sending of this mail. However, a large number of electrons were greatly inconvenienced.* --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .