Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas021.isp.belgacom.be (localhost [127.0.0.1])
        by inav003.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AV-3.00) with ESMTP id j796eHbV015226
        for <joris.at.lebbeke@skynet.be>; Tue, 9 Aug 2005 08:40:17 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx004.isp.belgacom.be (inmx004.isp.belgacom.be [195.238.3.48])
        by inas021.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AS-2.03) with ESMTP id j796e6aR009674
        for <joris.at.lebbeke@skynet.be>; Tue, 9 Aug 2005 08:40:07 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx004.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id j796drR9009227
        for <joris.at.lebbeke@skynet.be>; Tue, 9 Aug 2005 08:39:57 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id j796Xilg010405;
	Tue, 9 Aug 2005 02:35:05 -0400
Received: from mail10-fra-R.bigfish.com (mail-fra.bigfish.com [62.209.45.166])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id j796XdsD010401
	for <Tiff@lists.maptools.org>; Tue, 9 Aug 2005 02:33:40 -0400
Received: from mail10-fra.bigfish.com (localhost.localdomain [127.0.0.1])
	by mail10-fra-R.bigfish.com (Postfix) with ESMTP id 6081D4281E1;
	Tue,  9 Aug 2005 06:33:35 +0000 (UTC)
X-BigFish: VPC
Received: by mail10-fra (MessageSwitch) id 1123569214915104_29946;
	Tue,  9 Aug 2005 06:33:34 +0000 (UCT)
Received: from smtp01.oce.nl (smtp01.oce.nl [134.188.1.25])
	by mail10-fra.bigfish.com (Postfix) with ESMTP id D1FE64293E8;
	Tue,  9 Aug 2005 06:33:34 +0000 (UTC)
Received: from smtp05.oce.nl (smtp05.oce.nl [134.188.1.26])
	by smtp01.oce.nl (8.12.8p1/8.12.8) with ESMTP id j796XYxC012075;
	Tue, 9 Aug 2005 08:33:34 +0200 (MEST)
Received: from smtp-venlo.oce.nl (localhost [127.0.0.1])
	by smtp05.oce.nl (8.12.8p1/8.12.8) with ESMTP id j796XXg7017400;
	Tue, 9 Aug 2005 08:33:33 +0200 (MEST)
Received: from smtp03.oce.nl (smtp03.oce.nl [134.188.150.26])
	by smtp-venlo.oce.nl (8.12.8p1/8.12.8) with ESMTP id j796XUH4023622;
	Tue, 9 Aug 2005 08:33:31 +0200 (MEST)
Received: from oce.nl (localhost [127.0.0.1])
	by smtp03.oce.nl (8.12.8p1/8.12.8) with ESMTP id j796XT0J023425;
	Tue, 9 Aug 2005 08:33:29 +0200 (MEST)
Message-ID: <42F84E37.F20B0593@oce.nl>
Date: Tue, 09 Aug 2005 08:33:27 +0200
From: Rob van den Tillaart <rvdt@oce.nl>
X-Mailer: Mozilla 4.61 [en]C-CCK-MCD   (WinNT; I)
X-Accept-Language: en,nl
MIME-Version: 1.0
To: Joris <joris.at.lebbeke@skynet.be>
Subject: Re: [Tiff] Overlay Hyperlinks On TIFF
References: <0c6201c5980d$a9fb1b50$6501a8c0@gateway><Pine.SOC.4.60.0508031024540.11359@blade.simplesystems.org><42F73BB1.1EF341BE@oce.nl>
	<002e01c59c0c$cb6d3680$0fb2f651@dfgrrxsknr4e>
	<000f01c59c2c$675cdb80$0fb2f651@dfgrrxsknr4e>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Filter-Version: 1.12a-oce (smtp-venlo)
Cc: Tiff@lists.maptools.org
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/pipermail/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-UIDL: 000000000023ceae.00000a68
X-MSP-STORE: Tue, 09 Aug 2005 08:40:23 +0200
Status:   


Joris wrote:
> 
> Earlier, I wrote:
> > uint16: number of clickable areas
> > per clickable area
> >     uint32: x
> > ...
> 
> Not that it matters much, and it's probably hypothetical and not meant to be
> useful, but there's an aligment stupidity here that I might as well correct...
> 
> How about this:
> 
> uint16: number of clickable areas
> uint16: region type
> per clickable area
>      uint32: x
>  ....etc
> 
> The region type value can be either of
> 0: the width and height values are meaningfull, the clickable area is a
> rectangle
> 1-65534: the width and height values are to be ignored. Instead, this value
> describes are radius, and x and y describe the center point of a circular
> region. This type of region should not be included if XResolution and
> YResolution tags are in the IFD and have different values, since pixels in that
> case are not rectangular and a radius in pixels does not make sense.
> 65535: the widht and height values are to be ignored. Instead, after all regular
> rectangular regions (region type = 0) and circular regions (region type 1 to
> 65534) have been checked, and no region is found to comply, the x and y of this
> type of region that is nearest is said to be clicked. Again this type of region
> should not be included if XResolution is different from YResolution.

some refactoring :)

regiontype:	name	description
--------------------------------------
0000: 	[rectangle]	the width and height values are just that
0001: 	[ellipse]	the width and heigth values are the lengths 
			of the axis of the ellipse.
			For circles they are identical
			Note that if the X-Y res differs one still can 
			define perfect 	circles 
FFFF: 	[nearest]	see above 65535

This scheme include ellipses and leaves room for 60000+ other shapes
and/or 
attributes. The [not] and [doubleclick] are region attributes: E.g. the
[not rectangle] 
is the complement area of [rectangle]. all area outside the rectangle.

> It can happend that multiple regions apply (either rectangular or circular, it
> cannot happen that more regions of type 65535 apply, except if these regions
> have identical x and y values). This case is undefined, and application code can
> de whatever it wants with this. Writers should avoid writing clickable area data
> with overlapping regions because the behavious in such case is not defined.

What to think about a 'nearest point with attracting factor' region
type? 
define a number of points with a different charge. Gravity.
Automatically 
creates area's. 
The ultimate region type is the polygon I guess.

> Just for the fun of it, though... ;-)

fun is the grandmother of creativity !

> 
> Joris Van Damme
> info@awaresystems.be
> http://www.awaresystems.be/
> Download your free TIFF tag viewer for windows here:
> http://www.awaresystems.be/imaging/tiff/astifftagviewer.html


regards,
rob

_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
