File: TK_EvalFile.cat

package info (click to toggle)
scilab 2.4-1
  • links: PTS
  • area: non-free
  • in suites: potato, slink
  • size: 55,196 kB
  • ctags: 38,019
  • sloc: ansic: 231,970; fortran: 148,976; tcl: 7,099; makefile: 4,585; sh: 2,978; csh: 154; cpp: 101; asm: 39; sed: 5
file content (60 lines) | stat: -rw-r--r-- 2,933 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

TK_EvalFile(2)                 Scilab Function                 TK_EvalFile(2)
NAME
  TK_EvalFile - Reads and evaluate a tcl/tk file

  Author: Bertrand Guiheneuf

  With this routine, one can read and evaluate the content of a file contain-
  ing tcl/tk scripts. This allows to create powerful tk interfaces.

Usage
  TK_EvalFile(filename)

Input parameter

  o    filename : string character Contains the name of the file to read and
       evaluate.

Output parameters
  None

Description
  The filename might be relative or absolute. It is absolute if begining with
  a leading slash (/). When relative, the specified path refers to the direc-
  tory where scilab was launched.

Advantages and drawbacks of this functionality
   This routines allows to use directly tcl/tk scripts. This thus allows, for
  instance to use Interface Builders such as SpecTcl to design the interface.
  The interfaces built directly with tcl/tk scripts are much faster than th
  ones built with the Scilab Graphic Object library provided with tksci (see
  uicontrol for example). Indeed, those Objects are warpings around tk
  graphic widgets.  Nevertheless, this way of creating graphic user interface
  sould only be used when one aims at adressing directly specific tk/tcl
  features.  There are two main reasons for this.  First of all, there is no
  simple way to manipulate scilab objects from within a tcl/tk script. Thus,
  the interface designer has to write two sets of callbacks routines. One to
  describe the changes occuring in the interface when the user acts on the
  widgets.  The second set of call routines will perform the (pure) scilab
  reactions to the user actions. Here is an example: Suppose you design a
  scrollbar corresponding to a spline tension value. You want the spline to
  be displayed in a graphic windows and updated each time the user moves the
  scrollbar. At the same time, you want the value of this tension parameter
  to be displayed within the Interface. You will have to write a first tcl/tk
  (callback) function which will be automatically called by the tk scrollbar
  ('-command' option). This callback function will update the displayed value
  of the parameter in the interface and will then call the scilab routine
  ('ScilabEval' command) to update the graph.
Remarks on the tcl/tk script style
  Because Scilab manages the tcl/tk events, it creates the root window ".",
  this window should not be destroyed nor directly used by your tcl/tk
  scripts. You should thus always create your own toplevel windows.  More-
  over, since this module was written at a time when namespaces didn't exist,
  some variables defined by scilab tcl/tk scripts could bother your code. It
  is generaly a good idea to take a look to the tcl/tk scripts evaluated when
  scilab is lauched. They are located in the directory
  $(SCI)/routines/tksci/SCRIPTS.

See also
  ScilabEval, TK_EvalStr, TK_GetVar, TK_Setvar