Re: Trouble with XmScrolledWindow & children

2000-07-20 Thread C Hennessy
Benoît Smith wrote: > > Greetings, > > I recently tried to bring a software from Solaris (featuring Motif) to > Linux (feat. LessTif), but it looks like the ScrolledWindow, > ScrolledText & ScrolledList widgets ignore any changes I make regarding > the values of the XmNx & XmNy resources: whiche

Re: Trouble with XmScrolledWindow & children

2000-07-20 Thread Carlos A M dos Santos
Are you sure you have a recent version of LessTif? I have an application which uses ScrolledText and have compiled it unmodified with both LessTif, Motif 1.2.4 and Motif 2.1.30. Could you please send a code example? On Thu, 20 Jul 2000, Benoît Smith wrote: > I recently tried to bring a softwar

Trouble with XmScrolledWindow & children

2000-07-20 Thread Benoît Smith
Greetings, I recently tried to bring a software from Solaris (featuring Motif) to Linux (feat. LessTif), but it looks like the ScrolledWindow, ScrolledText & ScrolledList widgets ignore any changes I make regarding the values of the XmNx & XmNy resources: whichever values I give, the widgets are

RE: lesstif-CVS bug: Broken pipe with Grace

2000-07-20 Thread Mitch Miers
Huh. TopLevelShell also inherits from vendorShell. Ah, it too just XtInheritRealize, so the depth will be 1. ApplicationShell inherits from TopLevelShell, so it's depth will be 2. Shrug. I guess use wc != xmDialogShellWidgetClass or your fix. Mitch > -Original Message- > From: Marti

RE: BaseClass (was Broken pipe with Grace)

2000-07-20 Thread Mitch Miers
Or, more trivially, just call it directly (_XmVendorExtRealize()). Neither closure nor call_data is used. A workaround would be a private unsafe version of XtAdd/Remove/Call/Callback; it would be thread safe if you knew the callers were. You might want more than one function to be called at rea

RE: lesstif-CVS bug: Broken pipe with Grace

2000-07-20 Thread Mitch Miers
Martin, It has the intended effect of only calling the realize callback once, but a more proper semantic would be ... && IntentedWrapperDepth == 0) as this would mean wc == vendorShellWidgetClass given what RealizeDepth() does. So you could as well use that equality check as well. Pick a

RE: Recent BaseClass changes

2000-07-20 Thread Mitch Miers
> > While CVS is non-available I am looking for a summary of what's still > > to be done related to the "BaseClass" changes: > > > > - there was this thread "RE: lesstif-CVS bug: Broken pipe with Grace " > >w/o a final conclusion. As Martin told me his last suggestion isn't > >the way

BaseClass (was Broken pipe with Grace)

2000-07-20 Thread Mitch Miers
Alexander, Martin [Alexander wrote] > While CVS is non-available I am looking for a summary of what's still > to be done related to the "BaseClass" changes: > > - there was this thread "RE: lesstif-CVS bug: Broken pipe with Grace " >w/o a final conclusion. As Martin told me his last sugge

Warning: XtRemoveGrab asked to remove a widget not on the list

2000-07-20 Thread Mogens Kjaer
Hello Lesstif, Scenario: lesstif-0.91.4 Motif-2.0 widgets Redhat 6.2 I get the warning message: Warning: XtRemoveGrab asked to remove a widget not on the list twice every time I destroy a toplevel shell. I've included a simple example, press "Create Window 2" to make a second window, and whe

Memeory leak in Manager

2000-07-20 Thread sholson
Here is a fix for a memory leak in Manager. Its a simple failure to free when the widget is destroyed. - Steve *** lesstif-0.91.3/lib/Xm/Manager.c.origSun Mar 5 07:38:29 2000 --- lesstif-0.91.3/lib/Xm/Manager.c Sun Jul 9 00:50:08 2000 *** *** 853,858 --- 853,863 -

Uninitialized variable in XmString

2000-07-20 Thread sholson
Here is patch for a uninitialized variable problem. The problem is caused by the way _XmStringGetNextSegment treats its second argument. See the comment at the top of _XmStringGetNextSegment. - Steve *** lesstif-0.91.3/lib/Xm/XmString.c.orig Wed Jun 14 16:00:12 2000 --- lesstif-0.91.3/li

Re: Fix the Xbae Imakefiles, please!

2000-07-20 Thread Alexander Mai
On Thu, Jul 20, 2000 at 01:18:28PM +, Carlos A M dos Santos wrote: > > Hello > > Please apply the attached patch to fix the following problems in Xbae > Imake support: > * Xbae/Xbae.tmpl contains wrong revision numbers; > * Xbae/include/Xbae/Imakefile generates a Makefile that is not

Fix the Xbae Imakefiles, please!

2000-07-20 Thread Carlos A M dos Santos
Hello Please apply the attached patch to fix the following problems in Xbae Imake support: * Xbae/Xbae.tmpl contains wrong revision numbers; * Xbae/include/Xbae/Imakefile generates a Makefile that is not compatible with non-GNU make programs and that removes Matrix.h Caption.

Re: leaks

2000-07-20 Thread Alexander Mai
On Thu, Jul 20, 2000 at 02:02:33PM +0200, Alexander Mai wrote: [...] > Ok, situation has changed for me here: > as of now > command/test3 leaks by 40 bytes > selectionbox/test9, textf/test8 are down to 36! Well, on DU with Motif 1.2.4 I get this: ++ command/test3.motif leaking 950 bytes per C

Re: leaks

2000-07-20 Thread Alexander Mai
[Instead of a real reply copy fom archive] * From: Rick Scott * Subject: leaks * Date: Thu, 06 Jul 2000 16:10:15 -0700

ddd fix and question

2000-07-20 Thread Alexander Mai
OK, cvs is back again. The Text.c fix seems to work, thanks. Dumb question, I don't use ddd often: what's this between the toolbar and the source window? I get another bar with entries Run:step:next:... but it is nothing usable. I don't see this on my DU version of ddd nor on any screenshot. --