The last time I checked, the XFree distributions weren't compiled
for thread-safety. (This is a while ago.) Things may have changed.
If your X isn't thread-safe (a compilation option), then no matter
what LessTif does, your application will not run. So check this
first.
There is a bit of thread support in a couple of the LessTif widgets, but
no more than that.
TextField is not one of the widgets I touched on when doing this.
Making TextField threadsafe should not be hard, there's documentation
in lesstif/doc/ on how to do it.
If you're working on this, could you help us out ?
Danny
[EMAIL PROTECTED] wrote :
> Hi, I am making an application using lesstif with multiple threads using
> pthread.h .
> My problem is that I have a number of textfield widgets that are managed
> by a form manager widget. As mentioned before I use multiple threads.
> One of them handles user interface events, using XtAppMainLoop () and
> the other one changes the contents of the textfield widgets from time to
> time using XtVaSetValues, where the XmNvalue resource is set. When doing
> so, the contents (text) of the widgets is not visually updated. Unless I
> move the mouse pointer over the window containing the textfield widgets.
>
> Has this problem anything to do with the use of multiple threads ? Or is
> something else the problem. I already tried to solve the problem with
> XmUpdateDisplay
