File: readme.txt

package info (click to toggle)
paraview 5.13.2%2Bdfsg-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 544,220 kB
  • sloc: cpp: 3,374,605; ansic: 1,332,409; python: 150,381; xml: 122,166; sql: 65,887; sh: 7,317; javascript: 5,262; yacc: 4,417; java: 3,977; perl: 2,363; lex: 1,929; f90: 1,397; makefile: 170; objc: 153; tcl: 59; pascal: 50; fortran: 29
file content (23 lines) | stat: -rw-r--r-- 1,127 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
This example contains:

1.  A server manager xml file (helix.xml) which defines a programmable source
    that creates a helix.  It also contains extra properties for variables in
    the python script.

2.  A custom gui created in the Qt designer.  When opening the designer, a
    blank widget may be used.  Place all labels and widgets in their places,
    add a spacer at the bottom then lay them out in a grid.  The widgets are
    named after their associated server manager property.  For example,
    NumberOfRounds is a string property with 2 values.  The first value is the
    name of the python variable, and the second is the value of the python
    variable.  The widget is named NumberOfRounds_1, where _1 tells the GUI to
    tie the value of the widget with the second value of the server manager
    property.

3.  A helix.qrc file specifying the .ui file to include in the resource.
4.  A binary resource helix.bqrc, created from helix.qrc by the Qt's rcc command:
    rcc -binary -o helix.bqrc helix.qrc

  Although the Qt files aren't required, it does give a better user interface
  to the helix source.