-disablecallback"
option do?
setslient" method?
tclIndex file for Tix?
-command and -broeswcmd options?
tixWidgetDoWhenIdle do?
-browsecmd gets called
twice. However, I just want it to be called once.
tixInit command?
We will continue to provide free technical support and maintainence for Tix. However, to recover the development costs, we would appreciate financial supports for the Tix user community. If you like Tix and would like to make a donation to the Tix Project, please send mail to xpi@xpi.com.
-disablecallback"
option do?
-value option and a
-command option. Any modification of the
-value will cause the -command callback
to be executed. Sometimes this is undesirable. For example,
calling "config -value" inside the callback procedure
will cause the callback to be re-entered and thus an infinite
recursion.
The -disablecallback can be used to advoid this
problem. When this option is set, the -command
callback will not be executed even if the -value of a widget is
changed. Therefore, if you need to modify the -value of a widget
inside its callback, do this:
proc my_callback {w} {
$w config -disablecallback true
$w config value blah
$w config -disablecallback false
}
proc my_callback {w} {
tixSetSilent $w blah
}
option add *TixControl*entry.width 10OR
tixControl .c -options {
entry.width 10
}
setslient" method?
-disablecallback option.
selsilent used to be a widget command for the
ComboBox, Control, etc. It has been removed since Tix 4.0a4 and
replaced by the tixSetSilent command. Please note
that tixSetSilent is not a widget command but an
external procedure.
(TixForm) Error:Trying to use more than one geometry
manager for the same master window.
Giving up after 50 iterations.
Most likely, the problem is when using tixLabelFrame widgets, you
packed to the wrong frame: This is WRONG:
tixLabelFrame .d
button .d.b
pack .d.b
This is the correct way:
tixLabelFrame .d
set f [.d subwidget frame]
button $f.b
pack $f.b
pack .d
Remember you don't pack directly into a TixLabelFrame
widget. Instead, you should pack into its frame
subwidget.
tclIndex file for Tix?
tclIndex files cannot be generated using the
standard auto_mkindex procedure. You must use the tixindex program
in the tools/ subdirectory in the Tix
distribution. The syntax is
tixindex *.tcl
-command and -broeswcmd options?
tixBreak command. For example:
tixFileSelectDialog .c -command "puts foo; tixBreak"
tixWidgetDoWhenIdle do?
tixWidgetDoWhenIdle tixComboBox::Update $w blah blah ..will execute tixComboBox::Update only if $w exists. $w may be destroyed after tixWidgetDoWhenIdle is called but before an idle event happens.
We can't guarantee to implement the requested features immediately. Usually it depends on how important the features. If the feature is requested by more people, it will usually get done faster. However, some frequently requested features probably won't be imlemented. Usually these features are cosmetic changes and:
Some examples are:
-browsecmd gets called
twice. However, I just want it to be called once.
-browsecmd procedure is triggered by three types
of events: <1>,
<ButtonRelease-1>, and
<B1-Motion>. When the user clicks on an entry,
a <1> and a
<ButtonRelease-1> event will happen in rapid
session, which causes your -browsecmd procedure to be
called twice.
A crude fix for this problem is to ignore all the
<ButtonRelease-1> events. You can find out the
event that triggers the -browsecmd procedure by the
tixEvent command. Here is an example:
tixDirList .c -browsecmd Browse
proc Browse {args} {
if {[tixEvent type] == "<ButtonRelease-1>"} {
return
}
# ....
}
<1> on entry one.
<B1-Motion> on entry two.
<ButtonRelease-1> on entry three.
Therefore, if you use the above method, the browse event on entry three will be lost!
To devise a better solution, it's better to understand the basic design conventions of a Tix-based GUI. Suppose we have a list of entries displayed in a listbox (or DirList, or HList). When the user clicks on an entry, the GUI usually responds by displaying a "detailed view" of the entry. For example, if we put a list of file names in a listbox, when the user clicks on a file name, we display the contents of the file in a text window. If the user then clicks on another file name, the text window will load in the contents of the new file.
Now what happens if the user clicks on the same entry twice? Do we reload the contents of the file into the text window? This is usually unnecessary, inefficient and probably not what the user wants to do. The Tix convention is, when the user clicks on the same entry again, the detail view is not updated. If the user wants to force an update (e.g, the user knows the file's contents has been changed and wants to see the new version), he or she can double-click on the entry and the application will respond by redisplaying the detail view (reloading the file).
To implement this policy, the Browse procedure should be modified as the following:
proc Browse {args} {
global currentView
set ent [tixEvent value]
if {$ent == $currentView} {
# We have already displayed the detailed view of $ent.
#
return
} else {
set currentView $ent
DisplayDetail $ent
}
}
# ./configure --prefix=/usr/vendor/tcl
loading cache ./config.cache
checking for a BSD compatible install... /usr/bin/installbsd -c
checking for ranlib... ranlib
checking how to run the C preprocessor... cc -E
checking for unistd.h... ./configure[603]: "${ac_cv_header_$ac_safe+set}": bad
substitution
make distclean ./configure make all
I have integrated Tcl7.4, Tk4.0, Expect-5.19 and Tix4.0 on Linux 1.2.13 (ELF) and Solaris 2.4. It isn't too hard. For an expectk+Tix binary you need to add a call to Tix_Init in exp_main_tk.c. If you can find the call to Tk_Init then just cut&paste and replace it with Tix_Init. Do the same if you want a Tk+Tix window shell in TkAppInit.c. Worked like a charm. If you have any problems just holler.
With Tix4.0a7 (and also with Tix4.0a6) on Solaris 2.4, when running the widget demo, in tixFileSelectBox, in the two scolling lists (for Files an Directories), some of the file and directory names have their first 2 letters chopped off. And some files are repeated.Solution: tixwish has some conflicts with /usr/ucblib/libucb.so.1 and you should not linke it tixwish (you don't need it). Here is a solution provided by Charles L Ditzel (charles@hanami.cyberspace.com):
To fix the problem I was having, all I did was:unsetenv LD_LIBRARY_PATH set my PATH to something basic like: /usr/bin:/usr/ccs/bin:/bin:/usr/openwin/bin:/opt/SUNWspro/bin removed config.cache ./configure make clean makeand now it works!! Must have been something in my oldPATHorLD_LIBRARY_PATHthat was causing it to pick up/usr/ucblib/libucb.so.
Tk_ConfigureWidget() inside the
file tixInit.c, then the problem is because you
compiled libtk.a and libtix.a with
different versions of the Th header file
tk.h. Delete all the .o files from the
src directory of Tix, fix the Makefile so that now you can
compile libtix.a with the same tk.h that you used to
compile libtk.a.
tixInit command?
*TixScheme: Gray *TixFontSet: 14PointIf you want to switch color schemes and fontsets during run time, you can issue the following commands:
tix config -scheme Gray -fontset 14Point
Please read the tix manual page for
more details
*TixScheme: TK *TixFontSet: TK
*TixScheme: Bisque