1 |
User-visible bugs in FenPDF 1.0 |
User-visible bugs in FenPDF 1.0 |
2 |
=============================== |
=============================== |
3 |
|
|
4 |
FATAL: |
FATAL |
5 |
|
----- |
6 |
|
|
7 |
- import assumes application/pdf! |
- "PLANE IS NOT A CONTAINER"! |
8 |
|
- gets blue screen, nothing happens |
9 |
|
|
10 |
- Textures getting clobbered! |
- Menu seems to clobber fonts? |
11 |
|
|
12 |
- a paper turned solid green |
- Instability. Have seen it crash in renderImpl. |
|
|
|
|
- letters vanish |
|
|
|
|
|
- make sure text and paper always unbind the texture finally. |
|
|
- text done |
|
13 |
|
|
14 |
IMPORTANT: |
IMPORTANT: |
15 |
|
|
|
- transclusions / texts move by dragging WITHOUT ctrl!!! |
|
|
|
|
16 |
- startup takes far too long. [slightly mitigated already |
- startup takes far too long. [slightly mitigated already |
17 |
by tjl, fixing irregu generation.] |
by tjl, fixing irregu generation.] |
18 |
|
|
|
- start with blurring / bleaching. SOO much better viewing |
|
|
|
|
19 |
- sometimes "not a canvas view" |
- sometimes "not a canvas view" |
20 |
[ architecture-wise: what the hell is AbstractMainNode2D |
[ architecture-wise: what the hell is AbstractMainNode2D |
21 |
doing, checking members' derived types? |
doing, checking members' derived types? |
23 |
getChildView2D is **NOT** a good solution. |
getChildView2D is **NOT** a good solution. |
24 |
] |
] |
25 |
|
|
26 |
ANNOYANCE: |
- menu needs sometimes to be clicked several times |
27 |
|
|
28 |
|
- need proper grab framework |
29 |
|
|
30 |
|
ANNOYANCE |
31 |
|
--------- |
32 |
|
|
33 |
|
- timings need adjustment |
34 |
|
|
35 |
- Structlink connecting not done in the right way by spec |
- Structlink connecting not done in the right way by spec |
36 |
|
|
37 |
- selection not removed at first other click |
- selection not removed at first other click |
38 |
|
- need to think more about this |
39 |
|
|
40 |
- no click&drag of selected area to transclude |
- no click&drag of selected area to transclude |
41 |
|
|
42 |
- expose events not propagated |
- in pdf nodes, transclusions connected to center always, |
43 |
|
not real transclusion center |
44 |
|
|
45 |
|
- in transclusion nodes, text fairly unreadable |
46 |
|
|
47 |
|
- do we need xu links!? |
48 |
|
- might be appropriate, or structlink with |
49 |
|
enfilade on other end? |
50 |
|
|
51 |
|
- pdf fisheye dragging not right by coordinate system |
52 |
|
|
53 |
|
- need way to move to same node on other focus |
54 |
|
|
55 |
|
- multiple transclusions from a doc as a way of shortening |
56 |
|
doesn't work nicely with current interface - buoys need |
57 |
|
to be combined and buoys used several times magnified a little more |
58 |
|
|
59 |
|
- "crosshair" cursor too large and in wrong place! |
60 |
|
|
61 |
|
|
62 |
ALREADY FIXED, BUT SYMPTOM OF DEEPER ARCHITECTURAL PROBLEM: |
ALREADY FIXED, BUT SYMPTOM OF DEEPER ARCHITECTURAL PROBLEM |
63 |
|
---------------------------------------------------------- |
64 |
|
|
65 |
- unlink buoy doesn't work for transclusions! |
- unlink buoy doesn't work for transclusions! |
66 |
[ architecture-wise we should separate the bindings |
[ architecture-wise we should separate the bindings |