HDTenEightyP/NetNews huggingface dataset:
From: daniel@osf.org (Daniel Dardailler)
Subject: Re: motif scale/scrollbar problem, bug?
 
Organization: Open Software Foundation
Date: Mon, 16 Nov 1992 16:49:55 GMT

|> 	I encountered the following behavior while developing a Motif
|> application.  I have an XmScale widget with the XmNvalueChangedCallback
|> attribute set to some function.  In the callback function, I simply pop up
|> a *modal* XmErrorDialog.
|> 
|> 	Now, if I drag the scale's slider and then release the mouse button,
|> the callback gets called and the errorDialog is popped up.  Everything is ok
|> right here.  However, if I click the mouse button inside the scale's trough,
|> then the following sequence of events occurs:
|> 
|> 		1. The slider moves.
|> 		2. The callback function gets called and the errorDialog
|> 		   gets popped up.
|> 		3. And the slider keeps moving (after XmNinitialDelay
|> 		   milliseconds) as if the mouse button is still pressed
|> 		   inside the trough.
|> 
|> This only happens if the errorDialog is modal.  This behavior also applies
|> to XmScrollBar.
|> 
|> 	Could anybody please shed a light on this?  Is this a Motif
|> bug/oversight?  Or did I do something wrong?  Any ideas on how to
|> circumvent this?
 
When your use the slider or an arrow, the callback is called at the very end 
of the event processing (at ButtonRelease time), no state here, no problem.

When you press in the through, the ButtonPress calls the callback,
and a timer is installed by the scrollbar, which automatically calls
the callback again and again, until a ButtonRelease occurs or
the slider hits an arrow.

By popping a modal box from the callback, you are stealing the 
ButtonRelease from the scrollbar code, which cannot remove the timer
appropriately.

We already got a report similar to yours by a person who was setting the
scrollbar insensitive in the callback, same problem.

To me, this is a bug in the application.

As for any modal input juggling around, you'll probably have to
look into your own event dispatch control to workaround this one.
(sorry I can't help you more here).

Daniel
From: nr3m+@pitt.edu (Matthew A Henry)
Newsgroups: comp.windows.x.motif
Subject: OptionMenu Problem
Date: 18 Nov 92 16:38:08 GMT
Organization: University of Pittsburgh


System: HP705, HP-UX 8.07, Motif 1.1

I have a window that contains groups of labels, text field widgets,
toggle buttons, and one option menu.  After using the option menu, the
text field widgets will no longer become focused or accept any input.
The toggle buttons continue to work correctly.  If the window is closed
and opened again, the text field widgets are fine.  Any thoughts on why
the option menu might be effecting the text field widgets this way would
be greatly appreciated.

Thanks,

Matt Henry
nr3m@unix.cis.pitt.edu

Newsgroups: comp.windows.x.motif
From: dao@rchland.vnet.ibm.com (Dan Dao)
Subject: Re: Problem with WM_DELETE_WINDOW callback
Date: Fri, 20 Nov 1992 13:14:05 GMT
Distribution: comp
Reply-To: dao@rchland.vnet.ibm.com
Disclaimer: This posting represents the poster's views, not necessarily those of IBM
Organization: IBM Rochester

--
 
The code should read as follow:

  Atom         wmDeleteWindow ;
  Widget       shell, new_window ;
  [...]
  shell      = XtCreatePopupShell("mywindow", 
                                  topLevelShellWidgetClass, AppShell, 
                                  args, argcnt) ;
  new_window = CreatemyWindow(shell) ;    /* create and manage widgets */
               XtManageChild(new_window) ;
               XtPopup(shell, XtGrabNone) ;

                 /* I want to handle the wm Close item. */
               XtVaSetValues(shell, XmNdeleteResponse, XmDO_NOTHING, NULL);

                 /* Set up my callback for this protocol. */
               wmDeleteWindow = XmInternAtom(XtDisplay(shell),
                                            "WM_DELETE_WINDOW",
                                            False) ;
               XmRemoveWMProtocols( shell, &wmDeleteWindow, 1 );
               XmAddWMProtocolCallback(shell,
                                       wmDeleteWindow,
                                       (XtCallbackProc)myCloseCB,  
                                       (caddr_t)new_window) ;
 

Hope that help.

---
Dan Dao dao@rchland.vnet.ibm.com (507)253-8023
Newsgroups: comp.windows.x.motif
From: chuck@ccs.northeastern.edu (Chuck Wells)
Subject: Re: strange behaviour of pop up menus
Summary: I have the same problem too
Organization: College of CS, Northeastern U
Distribution: inet
Date: Fri, 20 Nov 1992 02:46:32 GMT

In article <9211121455.AA11645@lilbit.tdtech.com> prakash@lilbit.UUCP (Prakash Baskaran) writes:
>Last night I came across a strange problem.  I am using Motif 1.1.1 on a sun sparc.
>Part of my widget tree looks like this..
>
>         |
>       Form ....
>        / \
>       /   \
>    List   List
>

 [ describes problem of wierd popup behavior ]

>Has anyone had a problem like this before?   Did I miss something?  Any ideas?


This is funny, I was logging in to post the exact same question.  I'm using an
IBM RS/6000.  The problem is as follows:

I have a draw widget, and on that draw widget I have attached label widgets
containing pixmaps (so they look like icons).  I attached event handlers
to each label to check for mouse-down events (I am interested in all three
mouse buttons).  Without the presence of popups, all works fine; mouse button
#3 calls the correct event handler when pressed over a label.  However, when
I *create* a popup (I don't even try to manage it yet) and make this popup
a child of either the draw widget or any label widget (or even a parent of
the draw widget), something very strange happens: mouse button #3 no longer
causes my event handler to be called.  BUT, mouse button #1 and #2 still both
work fine, even though all three buttons use the same event handler.  
Something about the creation of a popup menu changes the behavior of button
#3 on my mouse.  Does anyone have any idea what is going on?  Is it a Motif
bug?

If you email a reply directly to me, please cc: to this address:
	ua_chw@nuhub.acs.northeastern.edu
since the sender address above usually doesn't work.  Thanks.




Newsgroups: comp.windows.x.motif
From: feit@ERA.COM (Mark Feit)
Subject: Lost Accelerators & Traversal
Organization: Engineering Research Associates, Vienna, VA
Date: Thu, 19 Nov 1992 19:57:15 GMT


I'm having a problem with accelerators and keyboard traversal not
working a little MacDraw type of thing running under Motif 1.1.4.  The
program doesn't do anything with TabGroups (i.e., no calls to
XmAddTabGroup), has only one translation which is used for a
DrawingArea and does no grabs.  The problem manifests itself as a
complete lack of keyboard traversal and the inability to use F10 to
hop into the menu bar.

Any ideas what would cause this or how to fix it?  I've tried about
two dozen things, and nothing works.

Thanks in advance.

						- Mark

 ................................. .................................
: Mark A. Feit             KD4TAJ : Internet: feit@era.com          :
: Engineering Research Associates : USENET: ...!uunet!era!feit      :
 ................................. .................................
From: smd@sl0091.srl.ford.com (Steve Dahmen)
Newsgroups: comp.windows.x.motif
Subject: Can Somebody Send some Wcl example(s)??
Date: 16 Nov 1992 21:21:41 GMT
Organization: Scientific Research Lab, Ford Motor Company
Distribution: world
NNTP-Posting-Host: sl0091.srl.ford.com
Originator: smd@sl0091.srl.ford.com


Would some kind soul send me some fairly straightfoward and simple
programs using Wcl??  Or tell me where I can ftp them from?

Ready to Prototype but Confused,


-- 
Steve Dahmen ** Graphics Application Programmer
Ford Motor Company
smd@sl0091.srl.ford.com
313-594-3229 (work)
Newsgroups: comp.windows.x.motif
From: daniel@moonshine.osf.org (Daniel Dardailler)
Subject: Re: Disabeling resizing of a shell widget
Keywords: resize no
Organization: Open Software Foundation, Motif Team
Date: Thu, 19 Nov 1992 18:01:05 GMT

 
|> How do I prevent a user from resizing a shell window?
|> I don't want to rely on MWM.
|> I tried giving the shellwidget a XmNresize false, and XmNnoResize 
|> true, but it didn't help.
 

Try setting max and min sizes (wmShell resources) to the same values.
Organization: Middle East Technical University - Computer Center
Date: Wednesday, 11 Nov 1992 14:51:18 TUR
From: <C51881@TRMETU.BITNET>
Newsgroups: comp.windows.x.motif
Subject:    Motif example source code is wanted!

Hi,
We need a little bit complex Motif demos. If someone knows
about this can he imform me about FTP adress or send the source code?
Thanks ...
                              Budak Arpinar
                        <C51881@TRMETU.BITNET>
From: deveau@oceanroutes.ns.ca ("Terry J. Deveau")
Newsgroups: comp.windows.x.motif
Subject: Re: Application without XtAppMainLoop
Date: 16 Nov 92 19:31:35 GMT
Distribution: inet
Organization: Oceanroutes Canada Inc.

Tero Takki <Tero.Takki@hut.fi> writes:
> 
> I am trying to make an application without XtAppMainLoop.
> If I use XtAppMainLoop-function, window appears with all
> widgets on it as I supposed. If I put my own never ending
> loop instead, I get one window without any widgets on it.
> 
> I suppose XtAppMainLoop does something that I would also
> have to do in my own loop. What is it?
> 
The one I've been using recently looks basically like this:

  Widget app_shell;
  XtAppContext STDBedAppContext;
  XEvent event;

  app_shell = XtInitialize ("main","STDB", NULL, 0, &argc, argv);
  STDBedAppContext = XtWidgetToApplicationContext(app_shell);
  while (True) {
     XtAppNextEvent (STDBedAppContext,&event);
     XtDispatchEvent (&event);
  }

... Terry
Newsgroups: comp.windows.x.motif
From: d91-jda@jaws.nada.kth.se (Johan Danielsson)
Subject: Re: Application without XtAppMainLoop
Organization: Royal Institute of Technology, Stockholm, Sweden
Distribution: comp
Date: Mon, 16 Nov 1992 08:26:04 GMT

In article <TERO.92Nov15182135@vipunen.hut.fi> tero@vipunen.hut.fi (Tero Takki) writes:

>I am trying to make an application without XtAppMainLoop.
>If I use XtAppMainLoop-function, window appears with all
>widgets on it as I supposed. If I put my own never ending
>loop instead, I get one window without any widgets on it.
>
>I suppose XtAppMainLoop does something that I would also
> have to do in my own loop. What is it?

From the man page XtAppMainLoop(3Xt):

     The XtAppMainLoop function first reads the next incoming X
     event by calling XtAppNextEvent and then it dispatches the
     event to the appropriate registered procedure by calling
     XtDispatchEvent.  This constitutes the main loop of X
     Toolkit applications, and, as such, it does not return.

     Applications are expected to exit in response to some user
     action.  There is nothing special about XtAppMainLoop; it is
     simply an infinite loop that calls XtAppNextEvent and then
     XtDispatchEvent.

     Applications can provide their own version of this loop,
     which tests some global termination flag or tests that the
     number of top-level widgets is larger than zero before cir-
     cling back to the call to XtAppNextEvent.



>Tero Takki
>Bredantie 26 B                   phone:  +358-0-505 1452
>SF-02700 Kauniainen              e-mail: Tero.Takki@hut.fi
>FINLAND


--

| d91-jda@nada.kth.se   | Everything's cool and froody.
| Johan Danielsson      |
Newsgroups: comp.windows.x.motif
From: daniel@juliet.osf.org (Daniel Dardailler)
Subject: Re: * Label Pixmap Problems *
Organization: Open Software Foundation, Motif Team
Date: Fri, 20 Nov 1992 18:54:21 GMT

 
|> As the title suggests, I'm having some problems getting a pixmap
|> image to appear on a label widget.  What I'm trying to do is
|> copy an area from a window in another program, and have that
|> area appear on the label widget as reference...  What I've tried
|> is setting up a shared header file between the two programs, which
|> simply contains the declaration for the pixmap.  Then, in the 
|> first program, when the user clicks on an area, I use XCreatePixmap
|> and XCopyArea to copy the region to the pixmap.  In the other
|> program with the label, I try to set it up with the LABEL_PIXMAP
|> type, and initialize it with the same pixmap.  The program always
|> bombs with an X error.  Any ideas on what's going wrong here?

Unfortunately, your description is not specific enough to let us
find the reason of your problem.

But let me guess.

You said you share a header file between your two programs where
you declare the pixmap variable and then, when the user click in one
area, you create the pixmap ??

Unless you're using some kind of shared memory mechanism, 
simply using the same header file in 2 different 
programs doesn't give you any sharing at all.

You have to come up with some inter-client communication solution
to have program2 aware of the pixmap id created by program1.

I'd suggest you take a look at ClientMessage in X.


Daniel - daniel@osf.org
Principal Software Engineer
Motif staff.

Newsgroups: comp.windows.x.motif
From: hammer@promis.com (Carl Hammerstedt)
Subject: regression testing GUI's and related tools
Summary: Looking for people who have experience with regression testing of GUI's
Keywords: GUI regression testing
Organization: PROMIS Systems Corp.
Date: Fri, 20 Nov 1992 21:50:29 GMT

Hi
	I'm looking for information and people with experience in regreesion testing
	graphical user interfaces. I am also interested in any methodologies
	relating to componet (widget) testing and application testing and how
	they inter-relate.

	Please post any E-Mail to scanlan@gpu.utcs.utoronto.ca

									Thanks...  ...Carl Hammerstedt,

									PROMIS Systems Corp.
From: snail@lsl.co.uk
Newsgroups: comp.windows.x.motif
Subject: Re: Problems with Form widget
Date: 20 Nov 92 15:39:10 GMT
Organization: Laser-Scan Ltd., Cambridge

In article <1992Nov19.042937.27756@umbc3.umbc.edu>, cs435141@umbc8.umbc.edu (cs435141) writes:
> I have been programming Motif for several weeks now (I consider myself a
> novice) and I have come up against a problem no one arround here can
> solve.  I am trying to arrange four pushButtons inside a Form widget
> in the following organization.  (Actually, this is a much simplified
> case of what I really want, but I still can't get it to work.)
[deleted...]
> But this is what I get when I run the program below:
> 
> +-------+
> |+-+ +-+|
> ||A| |B||
> |+-+ +-+|
> +-------+
[deleted program...]

You forgot to attach the bottom of buttons C and D to the form with 
XmNbottomAttachment = XmATTACH_FORM;

Use UIL instead, much easier and the end user can customize it. People will
tell you UIL is a pig etc. They are wrong, and probably lazy, or they use
Wcl (which is good). We've been using UIL here for over 3 years, no problem,
even the customer support guys picked it up easily. And for a C programmer
the layout is similar to C (what with the braces and semicolons everywhere).
-- 
snail@lsl.co.uk      

"para-phrasing an American's .sig"....
For the record, I did not vote for Bill Clinton
:-)
Newsgroups: comp.windows.x.motif
From: hassanm@a.cs.okstate.edu (HASSAN MUHAMMAD TA)
Subject: arrow-headed line in X/MOTIF
Organization: Oklahoma State University, Computer Science, Stillwater
Distribution: na
Date: Sun, 22 Nov 92 04:48:44 GMT

I am looking for a way to draw arrow-headed line using MOTIF or 
other X toolkit or Xlib.

Any help will be appreciated.
Please e-mail your help as I am not a frequent reader of this group.

Thanks in advance.


T. Hassan

e-mail address: hassanm@a.cs.okstate.edu
Newsgroups: comp.windows.x.motif
From: kshomper@turtle.cis.ohio-state.edu (keith shomper)
Subject: Label not Getting Keypress Events in translations or by Handler
Organization: The Ohio State University Dept. of Computer and Info. Science
Date: Mon, 16 Nov 1992 22:27:24 GMT

     I'm trying to get KeyPress events on a Label widget.  I can get them with
an Event Handler (sometimes), but not with translations ..... if you think you
know what's going on here, read on .....

     Here's my widget heirarchy:  Form
                                    |
                            -----------------
                            |               |
                          Label         ScrolledList

     I Need a clue to what's happening inside the List widget which is keeping
my Label widget from getting events.  Here's what's happening:  If I install
an Event Handler for KeyPresses on Label, I get these events delivered, UNTIL
I select something off of the List, then I never get another event via the
Label's handler.  Does anyone know why?  Is the List setting the Keyboard focus
after a selection and stealing the KeyPress events?

     I tried using translations on <Key> C and <Key> U (the two key presses I'm
really interested in), on the Label, but that never worked--even when I didn't
fool around with selections on the List.  Any pointers are appreciated, I've
read Chapter 7, part I in Asente and Swick, but that didn't help thid problem.
Heller's description on List in Appendix B makes a (very) short allusion to
List's behavior on FocusIn, and I perused the List code, but this also didn't
help.
Newsgroups: comp.windows.x.motif,comp.windows.x,comp.windows.x.intrinsics
From: patrick@8461.span@fedex.msfc.nasa.gov (Patrick Meyer)
Subject: Dual Screens
Reply-To: patrick@8461.span@fedex.msfc.nasa.gov (Patrick Meyer)
Organization: NASA (MSFC EO44)
Date: Mon, 23 Nov 1992 23:44:47 GMT


Has anyone written an application that runs on a device with more than one
screen? If you have, I need help.

Preferrably I would like to know how to move a window from one screen to the
other during execution.  If this is not possible, is it possible to have one
application on both screens.  Do you need to event loops?  I can't
find any documentation that shows how... help please.  

Any help appreciated.

Thanks in advance....
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
EMAIL: PATRICK%8461.Span@Fedex.Msfc.Nasa.Gov
       PMEYER%Mips9.Span@Fedex.Msfc.Nasa.Gov
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Newsgroups: comp.windows.x.motif
From: mark@IMD.Sterling.COM (Mark Buglewicz)
Subject: Re: Icon Box
Organization: Sterling Software
Date: Tue, 17 Nov 1992 05:34:21 GMT
X-Md4-Signature: adb933b61e957f3499b9fb3555a2157e

In article <GROSSJOH.92Nov16170556@lucy.ls6.informatik.uni-dortmund.de> Kai Grossjohann <grossjoh@ls6.informatik.uni-dortmund.de> writes:
>Hi netters!
>
>Afraid this is much of a beginner's question... Hope it's not a FAQ!
>
>I use the mwm and I like it quite a bit. There's one thing I don't like about
>it: When using the IconBox, you can not click on an icon in the icon box to
>minimize the associated window. The TWM Icon Manager can do that, though.
>However, I wouldn't want to change back to twm just for this one feature.
>Surely there must be a way?
>
>        Thanx, 
>                Kai
>--
>--
>  Kai Grossjohann            Phone (voice): 49 231 75 30 15
>  Baroper Str. 331 App. 510  E-Mail: 
>  W-4600 Dortmund 50         grossjoh@ls6.informatik.uni-dortmund.de
>  Germany                    
>--
>By the year 2000 we're going to have the best educated Americans
>in the world.
>                        -- Dan Quayle

Until version 1.1.5, there was no way to minimize a window from its icon.
Motif 1.1.5 now has the icon's Minimize option sensitized (available)
whenever the associated window is not already minimized.

Mark
From: jerry@shimmi.UUCP (Jerry Weingarten)
Newsgroups: comp.windows.x.motif
Subject: Motif Drag and Drop
Date: 15 Nov 92 22:48:56 GMT
Distribution: inet
Organization: The Internet
X-Unparsable-Date: Sun, 15 Nov 92 08:49:29 IST

I am trying to implement some drag and drop effects in the application that I am developing using
the facilities provided by Motif 1.2.  The only documentation that I could find was in the 
Programmer's Guide (Chapt 15) that came with the sources.  However, I find the explanation lacking 
(at best).  Some questions that come up while doing this - 

	1. What widget do I get in my XmNdropProc as the first parameter (is it the XmDropSite or my
		registered drop-site)??

	2.  How do I transfer client-data to the XmNdropProc or XmNdragProc routines?

	3. What is the meaning of the client-data in the XmDropTransferEntryRec? (I hopefully
		deduced this to be the client-data for the XmNtransferProc routine?!?!)

	4. Are there any restrictions on the data types that can be transferred between the initiator
		and receiver? For example I wish to transfer a structure that contains some strings -
	   however, these strings will be defined in the initiators adr space will the receiver get
	   meaningful pointers or should these strings be transferred as separate transfer types?

Thanx,
---------------------------------------------------------------------
Jerry Weingarten,                                  MENNEN MEDICAL LTD.

USENET: jerry@mennen.com
Phone:  972-8406751,  Air Mail: P.O.Box 102, Rehovot 76100, Israel 
FAX:    972-8406519   US Mail:  10123 Main Street, Clarence, NY, 14031
From: ruppal@BBN.COM (Rajiv Uppal)
Newsgroups: comp.windows.x.motif
Subject: Problem running under OpenWindows 2
Date: 20 Nov 92 18:47:20 GMT
Reply-To: ruppal@BBN.COM (Rajiv Uppal)
Organization: Bolt Beranek and Newman Inc., Cambridge MA
NNTP-Posting-Host: bbn.com

Hi folks, 

I am having a problem with my X application.  I thought maybe some
of you might have run accross something similar and maybe able to
give me some helpful pointers.  
 
I have a Motif 1.1.1 and X11R4 application which runs fine when it
is running under the Motif window manager.  But when I run it with
OpenWindows version 2, the application exits and gives the following 
error message:

Unexpected X error: BadAtom (request = 17); forced to exit.

This problem happens  under the following condition:
If I go into my "cmdtool (CONSOLE)" window and select a piece of text
with the mouse.  Then using the third mouse button I bring up the
"Term Pane" menu and then select "copy" from the sub-menu that hangs
off the "Edit" menu item in the "Term Pane" menu (I guess, by doing
this I am putting text into the clipboard).  After having done
this if I run my application from an xterm window, it comes up fine 
and behaves properly except when I select the "EDIT" menu within our
application.  This causes the application to exit.

If I do not have anything on the clipboard, my application runs fine
and does not exit unexpectedly. While going thru the code with the debugger 
it turns out that the application is making calls to the Clipboard in 
the following order,

XmClipboardLock(..)            < This returns ClipboardSuccess >
XmClipboardInquireCount(....)  < This also returns ClipboardSuccess >
XmClipboardInquireFormat(......)

It is in the XmClipboardInquireFormat call when it exits with the
Unexpected X error. 
  
Any help will be appreciated.

Thanks

Rajiv Uppal
Newsgroups: comp.windows.x.motif
From: dean@ecrc.de (Dean Adler)
Subject: Re: XKeysymDB
Reply-To: dean@ecrc.de
Organization: European Computer industry Research Centre GmbH.
Date: Wed, 18 Nov 1992 11:18:41 GMT

Does anyone know how the file /usr/lib/X11/XKeysymDB to supposed to be used?  My translation manager seems to require certain keysym strings which appear here.


Newsgroups: comp.windows.x.motif
From: pizzi@nervous.com (Riccardo Pizzi)
Subject: Shared MOTIF libraries: anyone?
Followup-To: poster
Reply-To: pizzi@nervous.com (Riccardo Pizzi)
Organization: The Nervous XTC Public Access Unix System, Rimini, ITALY
Date: Sun, 15 Nov 92 20:03:56 GMT

I was looking at my Motif application. It appears to be very large in size
(> 1 Mb, stripped), this is on an ISC SVR3 (2.2.1) using XFree86,
aka X11R5 on a 386.
I have sources for the Motif 1.1.3 library (I compiled it myself) and I am
wondering if there is a way to reduce the size of executables linked with it.
Are shared libraries planned by OSF? Any comments?

Please use email; I will summarize.

Thanks

Rick
-- 
Riccardo Pizzi @ the Nervous XTC Public Access Unix System, Rimini, ITALY
E-Mail -> pizzi@nervous.com        <*>      Bang-path -> uunet!nervous!pizzi
Nervous XTC, the home of the UniBoard package * Data: +39-541-27135 HST/PEP/V32
Newsgroups: comp.windows.x.motif