| 1 |
GS_get_cat_at_xy |
| 2 |
|
| 3 |
diff gsdrape.c gsdrape.bak - region clipping not working |
| 4 |
(see cont. example in germany location testdata) |
| 5 |
Inconsistent error - depends on view res, maybe check I3d init. |
| 6 |
or num points returned. |
| 7 |
I think fixed now. |
| 8 |
|
| 9 |
did a bunch of DIFFUSE -> AD changes for trial |
| 10 |
|
| 11 |
shininess not working |
| 12 |
OK - working now - will be different from SG3d due to infinite light. |
| 13 |
|
| 14 |
-------------------------------- |
| 15 |
NVIZ color bug: |
| 16 |
see /BUGS |
| 17 |
-> small z-scaled elevations are displayed dark. |
| 18 |
- problem in lat/long databases, too |
| 19 |
|
| 20 |
Helena wrote: |
| 21 |
>applied with the opengl function glNormal found in gsd_prim.c. I suspect |
| 22 |
>that there is a problem with how the normal vectors are calculated and |
| 23 |
>normalized. With a large Z range the normal XY values span -1 to 1, and |
| 24 |
>the normal Z values span 0 -1. With lat / long data and data with a low |
| 25 |
>Z range, the normal Z (temp[Z]) component is not normalized to the 0-1 |
| 26 |
>range but rather a small component of it. |
| 27 |
|
| 28 |
You are right that there is a problem with normals for surfaces with values |
| 29 |
<0-1>- I have already reported it, it seems that it is also causing parts of |
| 30 |
the surface to disappear for larger values of z for higher resolution/higher |
| 31 |
zscale case. Bill fixed it for the SGI-GL version - if the GL version |
| 32 |
is available it would be good to compare them. I will check with Bill, |
| 33 |
but I would like him to finish the legends first. |
| 34 |
|
| 35 |
-------------------------------- |
| 36 |
The trans.c file should be removed and any calls to the functions in that |
| 37 |
file should be replaced with appropriate OpenGL calls. All the functionality |
| 38 |
in trans.c can be achieved with OpenGL. |
| 39 |
|
| 40 |
-------------------------------- |
| 41 |
This library needs a general overhaul. There are many places which have |
| 42 |
empty functions containing only return statements, as well as several comments |
| 43 |
that say /* You can do better than this */ which indicates areas for |
| 44 |
improvements. |
| 45 |
|
| 46 |
-------------------------------- |
| 47 |
64-bit support needs to be added and properly handled |