Teleuse Support FAQ

This table shows the platform/OS and the compatible TeleUSE version.

www.motifdeveloper.com

http://www.faqs.org/faqs/x-faq/

Yes, TeleUSE provides the Ada Lightning Integration Package which provides an easy interface between the D language modules and Ada application code.  This package supports the current ObjectAda releases.

A gray setting marker indicates that the value shown is inherited. 
 

A D event field is a defined parameter for Data carried with a D event. It is accessed in D using the form:

     <d-event>.<d-event-field>

The problem isn't that the D event isn't sent, it's that your rule hasn't been registered for that D event yet. In TeleUSE, each D module is initialized separately, and it is during this "init" process that each rule is registered with its specific D event, local data is created, and the D module's INITIALLY rule is run. Thus, if the first D module initialized is the one that creates the widgets, then the other Dm odules won't have had a chance to register their rules yet, therefore the createCallbacks appear to get lost. The simple solution is to not create widgets in your INITIALLY rule (creating and initializing local variables is ok!). Instead, do the following in one of your D modules (I usually create a separate D module called "Main" for this and other generic D event handlers):

   devents:

        MainInit :local [];

   locals:
        top_w : widget;

   rules:
        INITIALLY does
          send (MainInit);  -- allow all INITIALLY's to run first !!
        end does;

        MainInit does

          top_w := create widget ("MyApplShell", nil, nil);
          top_w.show;
          --
          -- ... whatever else needs to be done ...
          --
        end does;

A local variable in a D module instance can be declared exported which makes it accessible from other D module instances. This is described in Chapter 3, "Declaration Parts" in Developing Dialog Components. The same is true for D events. By using the exported feature, there is probably no need to use .de files. The ability to export local variables was introduced with TeleUSE 3.0. Although D variables are still not directly share-able, you CAN access another D modules local variables

1) IF they are exported and   2) IF you have a handle to the D module instance.

Here is an example:

  devents:
    SomeCallback[];
    foo :local[]
  locals:
    x: string;
    d: devent;
  rules:
    SomeCallback does
      x := "foo";
      d := self.(x);
      send(d);
    end does;

    foo does

      printf("In foo\n");
    end does;

If you have a UDA of type string that represents the name of a D event field, you can use:

  x := SomeCallback.source_widget.StringUDA;
  d := self.(x);
  send(d);
  --          or simply:

  d := self.(SomeCallback.source_widget.StringUDA);
  send(d);

The list provided in the Vip "Define User Attributes" window is only a subset of the possible choices ... not exactly intuitive! Basically, you can use any valid X resource type that has been registered with the XtConvert mechanism (at the time 'vip' was built!). So you can use types like:

        Alignment (XmRAlignment)
        SiblingWidget (TuRSiblingWidget)
        WidgetChild (TuRWidgetChild)
        Cursor (XtRCursor)
        XRectangleList (TuRXRectangleList)
        IntTable (TuRIntTable)

        StringTable (XtRStringTable)
        Pointer (XtRPointer)
        ... etc ...

When you define UDAs in D code (e.g. "w.define("Name", "XType");"), you may use any valid D datatype, including any "User Datatypes" defined in your AIM files, as well as all the X resource types.

If you are using TeleUSE 3.0.2 or later, you can use the predefined operation "is_defined()" on the widget datatype. Actually, it returns the type of the attribute, but if it hasn't been defined it returns "nil". And this works for normal widget attributes as well as UDAs. So basically you can test for existence like this:

      if (my_w.is_defined("MyUDA") != nil) then

        -- the UDA exists
      end if;

In $TeleUSE/include/teleuse/tk_widops.h you will find 2 undocumented routines. These routines allow you to set/get UDAs from c code:

  extern void tk_get_widget_attr();
    /* Widget widget; */
    /* tu_string attr; */
    /* tu_string * prtype; */
    /* tu_pointer * pvalue; */
    /* tu_status_t * status; */

  extern void tk_set_widget_attr();
    /* Widget widget; */
    /* tu_string attr; */
    /* tu_string rtype; */
    /* tu_pointer value; */
    /* tu_status_t * status; */

  Example:

    tu_string uda_type;
    tu_pointer uda_value;
    tu_status_t status;

    /* My_UDA is a string UDA */

    /* To get UDA: */

    char *result_str;

    tk_get_widget_attr(wid, "My_UDA", &uda_type, &uda_value, &status);
    result_str = (char *)uda_value;

    /* To Set UDA: */

    tk_set_widget_attr (wid, "Other_UDA", XtRString, uda_value, &status);
                                          ^^^^^^^^^
                 Found in $TeleUSE/X11R5/include/StringDefs.h

It must be realized, managed, and mapped. If a widget has no parent, though, managing it is meaningless. A widget needs to be explicitly realized ONLY if none of its ancestors have been realized or it has no ancestors. Non-shell widget are managed automatically when they are created so no explicit managing is necessary. TopLevelShell and ApplicationShells should be opened/closed, after they have been realized, using:

      top_shell.do_popup();  <-- opens shell

      top_shell.do_popdown;  <-- closes shell

The problem is occurring because XmScrolledWindow parent of the file list needs to be unmapped.

To remove the problem, use:

dmodule main #include < teleuse/teleuse.h>

... 

INITIALLY does
  top := create widget ... 
  list_wid : widget := XmFileSelectionBoxGetChild(top->FSB, XmDIALOG_LIST);
  list_wid.parent.mapped := false;
           ^^^^^^

Set the XmScrolledWindow not just the XmList. Also, use the following option in your uxb.conf file:

  DINCLUDEDIR $TeleUSE/include

 to locate teleuse/teleuse.h for D.

You can set the background of the WHOLE scrolledWindow in D using:

top->ScrolledWindowClipWindow.background := top->scrolledWindow.background;
top->VertScrollBar.background := top->scrolledWindow.background;
top->HorScrollBar.background := top->scrolledWindow.background;

The internal widget names for a scrolledWindow are:

     ScrolledWindowClipWindow
     VertScrollBar
     HorScrollBar

Is the following code valid ?

        top->nameScrolledList.selectedItems.rewind;
        if (top->nameScrolledList.selectedItems.more) then
            sv := top->nameScrolledList.selectedItems.next;
        end if;

Syntatically it is correct but you should not do such operations (like rewind) directly on the scrolled list. Load top->nameScrolledList.selectedItems to a local variable before operating on it. This is because this expression invokes a function call and stores the result in a temporary variable. Operating on the temporary variable is useless. 

You can put the following in uxb.conf to undefine the word 'sun' in case user need that word in the config file. Example: if a directory has xxx/xxx/sun/xxx/xxx

#ifdef sun
#undef sun
#define sun sun
#endif

No. Globals can only be modified by direct assignment. Dot operators will not work on globals directly. If you want to use the string_list operations, you must use a temporary local variable and then assign it to the global.

Example:

If 'global_String_list' is declared in an aim file as:

       TYPE

          "char **" <--> string_list;
       ENTRY
          global_string_list  :  "char **";

In D use:

       -- build the string_list:
       local_string_list := create string_list();

       local_string_list.insert("item1",0);
       local_string_list.insert("item2",0);
       local_string_list.insert("item3",0);
       local_string_list.insert("item4",0);
       -- assign to the global:

       global_string_list := local_string_list;

In order to allow for the ehdb file to be in another directory you can use the DESTDIR option in the configuration file. Then run:

    >  uxb  -- to build

    >  uxb install -- to move the file to the DESTDIR

The DESTDIR configuration option changes the automatically generated uxb_mainc.c so that the ehdb file is referenced in the destination directory. The user can rely on an environment variable to find the file in the directory, or the path can be fixed.

You can set resources for the Help Windows in a resource file. The name of the eht help window TopLevelShell widget is 'eht'.

To set the iconPixmap of the help windows in a resource file use:

 *eht*iconPixmap: 

To set the fontList for the buttons in the help window use:

*eht*fontlist: < font specification> 

To set the fontlist for a help window frame use:

*eht*help_text.fontlist: < font specification> 

The "-geometry" command-line option is defined by Xt as ".geometry", not "*geometry". When TeleUSE builds an application, it places an "invisible" shell above all your shells to provide a consistent way of naming resources; therefore, your "-geometry" specification is being applied to this invisible shell instead of to the one you had intended.

 Instead, use the -xrm option (e.g., < app> -xrm "*geometry: 600x800+50+50"). The downside of this approach is that it will affect ALL TopLevelShells that are in your application for which the size/position is not hard-coded! You can limit this problem if you know the name of the shell at the top of the widget tree (assuming you know its name). In that case, replace the "*" with "*widget_name." (e.g., < app> -xrm "*AppShell.geometry: 600x800+50+50").

Name        : XRT widgets
  Vendor      : Quest Software
 Description : Integrations are maintained by Aonix for:


                XRT/3d
                  The easiest way to build informative and dynamic
                  3-D charts and graphs into Motif applications.
                XRT/field
                  The easiest way to build professional data-entry
                  fields into Motif applications.
                XRT/gear
                  The essential collection of add-on widgets and
                  utilities for Motif.
                XRT/graph
                  The easiest way to build powerful 2-D charts and
                  graphs into Motif applications.
                XRT/table
                  The essential multi-purpose widget for displaying
                  and editing lists, tables and forms.
  Email       :                                                                 Home Page   : http://www.quest.com
                                                                                                                                Download Integration: 
ftp://ftp.aonix.com/pub/tuts/outgoing/3rd_party_int/tu_xrt_rev11/TUXRTKIT.TAR.Z


                                                                                                                                
Name           : Xbae
                                                                                                                                Vendor       : Public Domain
  Description    : XbaeMatrix is a Motif widget which presents an editable
               array of string data to the user in a
               scrollable table similar to a spreadsheet.
               XbaeCaption is a simple Motif manager widget used to
               associate an XmLabel (caption) with it's single child.
Source     : ftp://ftp.x.org/contrib/widgets/motif/Xbae-4.6.2.tar.gz

Download Integration: ftp://ftp.aonix.com/pub/web/teleuse/tu_xbae_4_2.tar.Z


                                                                                                                                
Name        : Tuw Widgets
  Description : TuwItemBox
                Container that manages special kinds of objects called
                Tuw items. A Tuw item can consist of an icon and an
                optional name.
            TuwItemMenu
                Designed to handle the common situation requiring a
                dynamic menu, one in which the number of items varies
                as the application executes.
              TuwSource
                Displays a text file with line numbers in front of
                each line. TuwSource widget was
                developed to support source display in a debugger.
              TuwTree
                Displays a tree structure of nodes.
              TuwTable
                Allows you to build tables with different kinds of
                objects.
  Source      : Included with TeleUSE in $TeleUSE/conf/examples/tuw



  
Name        : DT Widgets
  Description : SpinButton
               A widget that allows you to cycle through a list
               of values in the forward or reverse direction.
                ComboBox
               A widget that contains a text and an arrow which
             posts a list of options for selection upon button press.
  Source      : Included with TeleUSE $TeleUSE/conf/examples/cde


  
Name        : EnhancementPak Widgets
  Vendor      : ICS
  Description : A collection of general purpose widgets, consisting
                of controls, geometry managers, and resource editors.
  Email       :                                                                 Home Page   : http://www.ics.com/Products/Epak/epak.html