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 04:49:19 -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 07JBcc84004675; Wed, 19 Aug 2020 07:39:20 -0400 Received: from outgoing-exchange-3.mit.edu (OUTGOING-EXCHANGE-3.MIT.EDU [18.9.28.13]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 07JBcaVk004672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 19 Aug 2020 07:38:36 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 07JBeogJ003331 for ; Wed, 19 Aug 2020 07:40:51 -0400 Received: from oc11expo12.exchange.mit.edu (18.9.4.17) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 19 Aug 2020 07:37:36 -0400 Received: from oc11exhyb7.exchange.mit.edu (18.9.1.112) by oc11expo12.exchange.mit.edu (18.9.4.17) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 19 Aug 2020 07:38:35 -0400 Received: from NAM11-DM6-obe.outbound.protection.outlook.com (104.47.57.170) by oc11exhyb7.exchange.mit.edu (18.9.1.112) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 19 Aug 2020 07:38:35 -0400 Received: from DM5PR12CA0011.namprd12.prod.outlook.com (2603:10b6:4:1::21) by MN2PR01MB5678.prod.exchangelabs.com (2603:10b6:208:113::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3305.24; Wed, 19 Aug 2020 11:38:34 +0000 Received: from DM3NAM03FT058.eop-NAM03.prod.protection.outlook.com (2603:10b6:4:1:cafe::4b) by DM5PR12CA0011.outlook.office365.com (2603:10b6:4:1::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 11:38:33 +0000 Received: from mail-ej1-f42.google.com (209.85.218.42) by DM3NAM03FT058.mail.protection.outlook.com (10.152.82.212) 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 11:38:33 +0000 Received: by mail-ej1-f42.google.com with SMTP id c16so25864896ejx.12 for ; Wed, 19 Aug 2020 04:38:33 -0700 (PDT) From: Jason White To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Wed, 19 Aug 2020 04:37:55 -0700 Subject: Re: [EE] LCD cover materials? Thread-Topic: [EE] LCD cover materials? Thread-Index: AdZ2HsaqWv2An6hPT5aq5N6DKDPt0Q== 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.218.42 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.42; helo=mail-ej1-f42.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=YiruHReBKPSz36EHdPx1/erc3RXwolJRzP4kHiT7FY0=; b=Rn/fQb2t8nN/PXGEmq+Rpf4Qf9T9sGoNt0jIfIPo0l8WyI0aXFc9zRoXeu+RC6li2y ykkwZgK64HwyncttPpUfzhw+PZWzmMxylH4CtpUHuVRekJsDeAjNExCudW1QVxjeBnsv hZc1nZbUsLBEIax4BI4MfhqR8oH9Y3GdNQdzUvYn3R9Bh1Sl6vdPxvEdR2zNCQCNImdM j1NlvC4GhyjSYOT1LZ0opitwrAmkLFNXp7XMFv/MHpqVwDg/bG09/GV8QJESX4m0pxQL 5/Kb46jy+dmoOGH+SuzlSHKN1xPWoWpnId/BT2ZOyt1rQgMWVr1zQoDQ/B0mUV8gEXPS b/nQ== authentication-results: spf=pass (sender IP is 209.85.218.42) 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:a17:906:a413:: with SMTP id l19mr25264811ejz.15.1597837112277; Wed, 19 Aug 2020 04:38:32 -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 In the past I think I've seen thin adhesive plastic films attached to displays of that type (similar to electrostatically adhered cell phone screen protectors). Thickness and material can likely be chosen such that it lasts for a reasonable amount of time before scratching up. In the case of cell-phone screen protectors they are replaceable and often sold in packs of 2 or more with the expectation that the individual protectors will wear out and be replaced. Perhaps researching the manufacturers of transparent lens/screen protector films might yield a whitepaper. Disclaimer: I'm not affiliated with the company below. My first google PDF result for "lens screen protector film filetype:pdf" ( https://www.photodon.com/Film-Comparison-Print.pdf ) yields a PDF comparing the different grades of plastic protection film from the sellers website. The FAQ on the website ( https://www.photodon.com/FAQ-Screen-Protectors.htm= l) suggests that they sell $5 sample kits of different films, do custom screen protectors, and have an online tool for 'finding the right screen protector film for the application'. Best of luck! And, if possible, let us know how it goes. -Jason White On Tue, Aug 18, 2020 at 7:47 PM 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. > --=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 .