From user-return-23271-archive-asf-public=cust-asf.ponee.io@poi.apache.org Mon Dec 3 18:08:51 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id BAAFD180645 for ; Mon, 3 Dec 2018 18:08:50 +0100 (CET) Received: (qmail 25262 invoked by uid 500); 3 Dec 2018 17:08:49 -0000 Mailing-List: contact user-help@poi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "POI Users List" Delivered-To: mailing list user@poi.apache.org Received: (qmail 25237 invoked by uid 99); 3 Dec 2018 17:08:48 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Dec 2018 17:08:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 86CC3C0413 for ; Mon, 3 Dec 2018 17:08:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.111 X-Spam-Level: *** X-Spam-Status: No, score=3.111 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URI_HEX=1.313] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id cXEL3SXuEfFH for ; Mon, 3 Dec 2018 17:08:46 +0000 (UTC) Received: from mail-lf1-f52.google.com (mail-lf1-f52.google.com [209.85.167.52]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 0321B5F1AD for ; Mon, 3 Dec 2018 17:08:43 +0000 (UTC) Received: by mail-lf1-f52.google.com with SMTP id p6so9726303lfc.1 for ; Mon, 03 Dec 2018 09:08:42 -0800 (PST) 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=+sHuj1m/5ySBVmQFs/I0eFLQYiBSZbCXwaEQAKouVUQ=; b=i0NLocJ9Zdd3ylPpg4zhXSi3oQjOCBKosVoj3frGRSJzbIbDfVZfjyT0oXUvNpG/wh ggx29xRwmVq7yBArsrr4XysOejl3P+HfAeE9SRhcg6YroRowTxCblRbtb6zq/ZDuVJOK T0+xSuUyOedp7a9WjZOJ5uTvrHgECSfui+0+reEp5ywLEkjsMeBxb7sDxPCCD7ih25Gt FqurVyU7zRLJhR46inC0xMtPzC+7LCXAvzgvatI/8xJE8XC+RE8qaPHwRQ4c7ftXsuDB DRz3rkX2ab4kA8ssoyQa8nncG13lK80dhIJ56gcuh+UOwgnodm0G43jgWPjH5rEJqC/F TkmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=+sHuj1m/5ySBVmQFs/I0eFLQYiBSZbCXwaEQAKouVUQ=; b=EMAHovbaIKuKXiOLh1y2xEQ8t7ES6v9USguST7DETI0OZvMJIK4IeodN+6I5E/zWEf A/lmnJbqwQwyXGzJfpt1ooqZBXByLKmItuC2hEkVs3VD+v5kAc8AZ3il49oDM2XZs4AV +Lc3thBj7rHzsD8CDiv/wM6aUXhFLKnsUY/KflrDTWSjjnX9cnKu6mWB0LDZ5kNiyLW4 1L8dTbVQUQFQWOLKo6+qZBB8q2gzuo0ms2uowv1JE8mdFtIg6n0jLP8S6OkJ3a9ZmmGx INwd7fb9S2p1zBi8I5Qqdj5DF85NkP6lCdQl2LwSXejkzgYJ+lsEfv4EGLBIY4Ge6ELU hOOg== X-Gm-Message-State: AA+aEWZ8/YUm86FYjZDTnS/A9BEAy4f8qvr7hZE0ZbVBq8WhTfDm9ME9 W8rb1Vsfb6TJmqWe4prLJdEqaix3vnyj/QPQTlTXm6XL X-Google-Smtp-Source: AFSGD/XmDpMlDme/XtJMrwnWKv3+TnTp0h9G14DWlkimvOVfPkJtzxRBTNGN772q/ymO9otrP1fgzqSQ9v/ShhfSRmA= X-Received: by 2002:a19:e601:: with SMTP id d1mr10117071lfh.71.1543856915411; Mon, 03 Dec 2018 09:08:35 -0800 (PST) MIME-Version: 1.0 References: <1543566473870-0.post@n5.nabble.com> In-Reply-To: <1543566473870-0.post@n5.nabble.com> From: Greg Woolsey Date: Mon, 3 Dec 2018 09:08:23 -0800 Message-ID: Subject: Re: Hyperlink() special case To: POI Users List Content-Type: multipart/alternative; boundary="000000000000070daa057c2133e5" --000000000000070daa057c2133e5 Content-Type: text/plain; charset="UTF-8" Just saw this - Gmail puts all emails from Yahoo in spam for some reason I haven't investigated. I like this, it was one of my first thoughts, but the display value parameter is not always a String - it can be anything, including an error result, in my testing. So there would need to be HyperlinkEval instances for each type of existing Eval class. Possible, but a bit to maintain. Advantage is the ability to use type checks to see what the cell value is, rather than looking at the formula string. Probably less to maintain and less invasive than adding to the evaluation pathway. I'll add it to the issue and hopefully be able to play with it in a month or so after wrapping up my current project. On Fri, Nov 30, 2018 at 12:28 AM pj.fanning wrote: > How about `public final class HyplerlinkEval implements HyperlinkValueEval, > StringValueEval` where HyperlinkValueEval has a `Hyperlink > getHyperlinkValue()` method? This way you can treat the result as a string > and get the current behaviour (to maintain compatibility) or you can treat > the result as a Hyperlink and get access to its link and its display text. > > > > -- > Sent from: http://apache-poi.1045710.n5.nabble.com/POI-User-f2280730.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@poi.apache.org > For additional commands, e-mail: user-help@poi.apache.org > > --000000000000070daa057c2133e5--