File: PROBLEMS

package info (click to toggle)
blt 2.4m-2
  • links: PTS
  • area: main
  • in suites: potato
  • size: 7,316 kB
  • ctags: 7,778
  • sloc: ansic: 68,187; tcl: 12,491; sh: 1,918; makefile: 709; csh: 25
file content (106 lines) | stat: -rw-r--r-- 4,019 bytes parent folder | download
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
Specific problems:

1. I've built BLT, but when I run it, I can't see any of the BLT commands?

   % graph .g
     invalid command name "graph"

  Starting with Tcl 8.x, the BLT commands are stored in their own
  namespace called "blt".  The idea is to prevent name clashes with Tcl
  commands and variables from other packages, such as a "table" command
  in two different packages.

  You can access the BLT commands in a couple of ways.  

  Prefix the BLT commands with the namespace qualifier "blt::"

   % blt::graph .g
   % blt::table . .g -resize both

  or import the BLT commands into the global namespace.

   % namespace import blt::*
   % graph .g
   % table . .g -resize both

2. I'm on a DEC Alpha running the graph widget. I don't see any ticks 
   or lines.

   There's a problem with code generated by the GNU C compiler 
   2.8.[0-1] for bltGrAxis.c and bltGrLine.c (I think it's just 
   these two files).

   Try compiling with either the native "cc" compiler or compile
   the two modules with -O0.

3. Under Windows the "drag&drop" command doesn't work for me.  

   The "drag&drop" command uses the "send" command to communicate
   between Tk applications.  For Tk 8.0, there's a patch available
   to add the "send" command.  And once upon a time in Tk 8.1, there 
   was a "send" command (see the alpha and beta releases), but now
   it's been removed in favor or the lower-level "dde" command.  
   You can use the dde-based "send" look-a-like in ./demos/send.tcl.
   Make sure you invoke the procedures "SendInit" and "SendVerify" 
   *before* you create and drag-and-drop targets.

4. I'm using Windows 95 and the -stipple option doesn't seem to work.

   Under Windows 95, your bitmap must be exactly 8x8.  If you use 
   a bigger or smaller bitmap, Win32 won't stipple the pattern correctly.
   For bitmaps larger than 8x8, only the upper-left 8x8 corner of the 
   bitmap is used.  For smaller bitmaps, the bitmap is extended to 8x8 
   with the new bits 0 (blank).  This is a deficiency in Windows 95, not
   Tk.
5. When I compile BLT on Solaris (maybe others?), I get lots of error 
   messages in the form:

    <unknown>	0xf44       /usr/local/lib/libtcl7.6.a(tclCmdIL.o)
    <unknown>	0xf3c       /usr/local/lib/libtcl7.6.a(tclCmdIL.o)
    <unknown>	0x628       /usr/local/lib/libtcl7.6.a(tclCmdIL.o)

   This is because Tcl and Tk have been installed only as static libraries, 
   not shared libraries.  The ./src/shared/Makefile creates the shared BLT 
   library with a back-link to these libraries.  The advantage of this link
   is that when you dynamically load BLT, the correct Tcl/Tk libraries are 
   automatically searched for any unresolved references.

   You can fix this in one of two ways. 

   o Remove the back-link.  Edit ./src/shared/Makefile and cut the 
     "-ltcl* -ltk*" references from the SHLIB_LD_LIBS macro.  

   o Create shared libraries for Tcl and Tk.  Re-configure, compile, 
     and install Tcl/Tk from their sources.  Make sure you add the 
     "--enable-shared" switch to "configure".

	./configure --enable-shared

General Problems:

1. I can't compile BLT.

   Send the output of both "./configure" and "make" to me at

	ghowlett@fast.net 
	gah@cadence.com

   This will make it easier to track down the exact problem.  

2. I get a segfault when running BLT in my application.

   The best and easiest method is to send me a *run-able* script
   that demonstrates the problem.  The hard work you do pruning 
   down the problem into a small script will greatly help solve
   it.  Usually the problem can been found and fixed right away.
   Make sure you include all the necessary pieces to make it 
   run (e.g. data file). If it's needed, also include directions 
   how to make the problem occur (e.g. double click on the left 
   mouse button).   

3. The manual page lies. 

   I appreciate any help in pointing out errors, omissions, or lies
   in the manuals.  If you have ideas how they might be improved, 
   I'd love to hear them.