[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

When should a CIImage be considered infinite?

Subject: When should a CIImage be considered infinite?
From: Gabriele de Simone <email@hidden>
Date: Fri, 3 Jun 2005 16:20:22 -0400
Delivered-to: email@hidden
Delivered-to: email@hidden

Quartz Composer is able to determine when a CIImage that results from a patch has infinite dimensions. I assumed that it was doing so by calling -[CIImage extent] and comparing the width and height to INFINITY, or use the isnan() macro... but as it turns out, the actual "infinite" coordinates for my CIImages are:

x -170141173319264429905852091742258462720.000000 (0xFEFFFFFF) y -170141173319264429905852091742258462720.000000 (0xFEFFFFFF) width 340282346638528859811704183484516925440.000000 (0x7F7FFFFF) == MAXFLOAT height 340282346638528859811704183484516925440.000000 (0x7F7FFFFF) == MAXFLOAT

Is it safe to always compare against MAXFLOAT then?

Thx
Gabe
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden

This email sent to email@hidden

Follow-Ups:
- Debugging Core Image Kernel
  - From: Paul Ossenbruggen <email@hidden>
- Re: When should a CIImage be considered infinite?
  - From: John Harper <email@hidden>

Prev by Date: Re: Accessing OTHER system parameters?
Next by Date: Re: When should a CIImage be considered infinite?
Previous by thread: Re: passing variables
Next by thread: Re: When should a CIImage be considered infinite?
Index(es):
- Date
- Thread

Home