It is not completely clear to me either what the problem is.

I've checked out emacs from CVS but it won't start building.
I've configured with 'configure --with-x-toolkit=motif' but
make says :
> dell: {54} make
> Essential Lisp files seem to be missing.  You should either
> do `make bootstrap' or create `lisp/abbrev.elc' somehow.
> gmake: *** [maybe_bootstrap] Error 1

This is on SuSE 8.0, with LessTif from CVS and emacs from CVS.

Anyway you mention that popup_deactivate_callback() gets called
more than expected. Why do you think that ? I would add a line
saying
  fprintf(stderr, "Deact(%s)\n", XtName(widget));
to the function to get a grip on what's happening.

        Danny


Pavel Jan�k wrote:
> The problem still remains. I still think it is not problem in lesstif or
> openmotif. I'll try to describe the problem again with more details:
> 
> I use popup_activated_flag to dispatch KeyPress events. Its value is
> changed with these two functions from xmenu.c:
> 
> static void
> popup_activate_callback (widget, id, client_data)
>      Widget widget;
>      LWLIB_ID id;
>      XtPointer client_data;
> {
>   popup_activated_flag = 1;
> }
> 
> static void
> popup_deactivate_callback (widget, id, client_data)
>      Widget widget;
>      LWLIB_ID id;
>      XtPointer client_data;
> {
>   popup_activated_flag = 0;
> }
> 
> The problem is, that the current code (in lwlib-Xm.c) doesn't work as
> expected. When you activate menu File, you can control the menu via
> keyboard (Up, Down). This works, but just after highlighting the next
> top-level item in the menu-bar (ie. Edit), our variable
> popup_activated_flag got zeroed.
> 
> What is the reason? It is simple. First, popup_activate_callback of the new
> menu is called and thus popup_activated_flag is set to 1, but after
> a moment, popup_deactivate_callback is called many times because it is
> called for all menu-items in the previous (File) menu.
> 
> I do not personally use Motif code, but I think that the false value of
> popup_activated_flag (it can very easy be 1 even when the popup is not
> activated) is dangerous and could be the source of potential problems (I
> saw that it is used to temporary disable redisplay etc).

-- 
Danny Backx ([EMAIL PROTECTED] [EMAIL PROTECTED])
Home page :     http://users.skynet.be/danny.backx
Projects:       LessTif (http://www.lesstif.org)
                Oleo    (http://www.gnu.org/software/oleo/oleo.html)
_______________________________________________
Lesstif mailing list
[EMAIL PROTECTED]
https://terror.hungry.com/mailman/listinfo/lesstif

Reply via email to