Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Although varying the camera distance and focal length will change the object's visual size, it has the drawback of also changing the perspective, thus leading to a somewhat distorted view. I suggest to use the camera's <code>SceneScale</code> property instead.</p> <p>Alas, I have no valid steps to calculate the correct value for that. In my case I have to scale to a cube with varying size, while the window size of the viewer is constant. So I placed two dummycubes at the position of the target cube, each sized to fit either the width or the height of the viewer with appropriate values for <code>SceneScale</code>, camera distance and <code>FocalLength</code>. During runtime I calculate the new <code>SceneScale</code> by the ratio of the target cube size in respect to the dummycube sizes. This works quite well in my case.</p> <p><strong>Edit</strong>: Here is some code I make for the calculations.</p> <ul> <li><code>ZoomRefX</code> and <code>ZoomRefY</code> are those DummyCubes</li> <li><code>TargetDimX</code> and <code>TargetDimY</code> give the size of the current object</li> <li><code>DesignWidth</code> and <code>DesignHeight</code> are the size of <code>MyGLView</code> at design time</li> <li><code>DesignSceneScale</code> is the camera's <code>SceneScale</code> at design time</li> </ul> <p>The calculation code:</p> <pre><code>ScaleX := (ZoomRefX.CubeSize*MyGLView.Width)/(DesignWidth*TargetDimX); ScaleY := (ZoomRefY.CubeSize*MyGLView.Height)/(DesignHeight*TargetDimY); NewSceneScale := Min(ScaleX, ScaleY)*DesignSceneScale; </code></pre> <p>The DummyCubes <code>ZoomRefX</code> and <code>ZoomRefY</code> are sized so that they have a small margin to either the left-right or top-bottom edges of the viewing window. The are both positioned so that the front faces match. Also the target object is positioned to match its front face with those of these DummyCubes.</p> <p>The formulas above allow the window size to be different from design time, but I actually didn't test this feature.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to adjust GLCamera to show entire GLScene
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USUwe Raabe
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the tip - I've been playing with SceneScale as well, using it in my OnMouseWheel event handler. Do I understand correctly that you set those dummycubes up during development, and the fit the cube accordingly at run-time? Sounds like a clever trick. Change the object, not the camera.
      singulars
      1. PO
      1. USAndreas
    2. COI set the dummycubes at during development to a size matching the window size of the viewer. Two cubes because the screen is not quadratic, but the dummycubes are. Now when my real object has say double the size of the dummycube, I know I have to halfen the SceneScale to make its visible size like the dummycube at design time. Doing these calculations separately for the widht and the height I can calculate the SceneScale that makes the target object fit into the window. This only works because the window size is fixed. And I don't change the object - I only change the camera's SceneScale.
      singulars
      1. PO
      1. USUwe Raabe
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload