-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathBUGS.txt
124 lines (82 loc) · 4.43 KB
/
BUGS.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
=====================================================================
000 ShapeScale nodekit causes continuous redraws.
When using this nodekit in the SoGuiExamples/nodekits/scalemarker
example, it sometimes doesn't stop sending notifications to the
scenegraph -- causing it to continually trigger redraws.
This is quite straightforward to reproduce, just try starting and
stopping spin animations while having set the envvar
COIN_SHOW_FPS_COUNTER=1, and you'll sooner or later see that it
won't stop redrawing even though the scene camera's position and
orientation is frozen.
20031117 mortene.
=====================================================================
001 SoText2Set miscalculates bounding boxes.
This might just be a missing feature (I didn't check), but it is
the case that SoGetBoundingBoxAction does not return the actual
bounding box for an SoText2Set node -- only the bounding box
surrounding the point positions for the text strings (i.e. and
does not take into account the string bbox themselves).
20031215 mortene.
UPDATE: Parts of this bug should have been fixed now. See bug #002
for info about the remaining issues.
20040206 handegar.
=====================================================================
002 SoText2Set creates too small bounding boxes for rotated strings
The bounding box will not come out right when a string has a
justification != RIGHT and an extreme rotation (about 90+
degrees). Some parts of the string will then be outside the
bounding box, leading to incorrect culling.
20040206 handegar
=====================================================================
003 ViewportRegion node fails with tiled SoOffscreenRendering.
See detailed description of bug as item #121 in Coin/BUGS.txt.
20040705 mortene.
=====================================================================
004 SoText2Set should be migrated to the new Coin cc_glyph2d interface.
It is now using the obsoleted SoGlyph class in Coin, which will
probably be removed before releasing Coin 3.0.
Note that the cc_glyph* and cc_fontspec* interfaces have not been
made public in Coin. They need a final audit before letting them
fly.
20040708 mortene.
=====================================================================
005 SmScenery node causes continuous redraws.
When using this node in any scene graph, it will for some reason
cause continuous notifications from the scenegraph -- causing it
to continually trigger redraws.
This is quite straightforward to reproduce, just set the envvar
COIN_SHOW_FPS_COUNTER=1 and load an SmScenery node, and you'll see
that it won't stop redrawing even though the scene's camera is
kept static.
I just added some convenient debugging stuff to Coin to aid in
these situations: by setting the envvar
COIN_DEBUG_ROOT_NOTIFICATIONS=1, the SoSceneManager will dump the
full notification chain of any changes made to the scene
graph. For some strange reason, this didn't help much with this
bug, as the notification chain seems rather non-sensical for
whatever happens with the SmScenery node. Could be a bug with the
Coin notification tracking mechanism -- should investigate.
20040708 mortene.
=====================================================================
006 Use of SmScenery node causes glGetError() to report
GL_INVALID_ENUM.
..but only for some drivers (like oso's laptop). Need to find out
why, it seems to have grave consequences on some drivers, like
completely short-cutting the visualization of Scenery data.
20040708 mortene.
=====================================================================
007 SoText2Set does not render correctly.
When using the Microsoft TrueType font for Times New Roman with
the FreeType library, SoText2Set renders only garbage, where
SoText2 from Coin renders correctly:
----8<-------------- [snip] -------8<-------------- [snip] -------------
#Inventor V2.1 ascii
Font { name "Times New Roman" }
SoText2Set { string "hepp" }
----8<-------------- [snip] -------8<-------------- [snip] -------------
This is most likely a general bug with SoText2Set, but it was only
tested with MS's Times New Roman.
Bug item #004 is probably related to, or possibly the cause of,
this bug.
20050317 mortene.
=====================================================================