realbasic-nug
[Top] [All Lists]

Re: RB3D Camera.position based on Object3d.postion

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: RB3D Camera.position based on Object3d.postion
From: David Grogono <dave at grogware dot com>
Date: Thu, 31 Jan 2008 09:21:59 -0600
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <47A005E9 dot 1040701 at radicalbreeze dot com> <1D6A4AF1-AD19-475B-8078-EDE99C414F36 at inspiringapps dot com> <47A166F0 dot 5050707 at radicalbreeze dot com> <F14EB11A-1352-4C70-9AAF-DB522140B16D at inspiringapps dot com>
On Jan 31, 2008, at 9:09 AM, Joe Strout wrote:

> Aha, this is a good point.  You do need to take into account the
> aspect ratio of the view, since the FieldOfView can't refer to both
> at the same time if your view isn't square.  I don't remember off the
> top of my head which it is, though (I think it may be the greater of
> the two dimensions, but I'm not sure).

For a non-square RB3Dspace, the field of view is for the smaller of  
the two dimensions.  That is, if an object exactly fills the view and  
you resize the space to make it wider, the object will still exactly  
fill the view top to bottom.

A couple of other things Bryan may want to keep in mind:  FieldOfView  
is an integer, not a double and the minimum field of view is '5'.   
This are both limitations that I'd like to see changed, but for now  
it's something to keep in mind if you're doing calculations with  
FieldOfView.

Best regards, David


--
David Grogono
www.grogware.com



_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>