>widget,
> "VendorShell Destroy: destroy child\n"));
>
> + _XmVendorExtDestroy(data->widget);
> +
> /* mitch
> XtDestroyWidget(data->widget);
> */
This is a dangerous area ...
Perhaps we should wait for an expert to commit this ;-)
--
Alexander Mai
[EMAIL PROTECTED]
k like it.
[...]
Well, I copied probably too many lines from Vendor and indeed the app
starts up again ...
What about the XtRemoveCallback() below?
--
Alexander Mai
[EMAIL PROTECTED]
On Fri, 4 Aug 2000 17:50:43 +0200, Alexander Mai wrote:
>This is a dangerous area ...
>Perhaps we should wait for an expert to commit this ;-)
>
Got an expert's "Ok" and committed then ...
---
Alexander Mai
[EMAIL PROTECTED]
for your Help
>
> Bob Parry
e.g. reading the docs?
Installation docs mention a version of lex, e.g. GNU flex which
may be used.
--
Alexander Mai
[EMAIL PROTECTED]
ans having a bug within
LessTif which causes both is not very unlikely, but I'm just
not sure they are where you "fixed" them ...
Bye,
--
Alexander Mai
[EMAIL PROTECTED]
ge I would trust gcc here and
assume the code is not ANSI C++ compliant.
I got it built using an old gcc 2.7.x on a linux box.
Would be a good idea if someone would pick up the
project and polish the source probably ...
--
Alexander Mai
[EMAIL PROTECTED]
00;
Looks like this stuff is still likely to contain some misfeatures (also remembering
your last report).
I'll commit your change.
(did you actually hit the limit? At first glance you always get a minimum
increase of 1000 bytes!?)
--
Alexander Mai
[EMAIL PROTECTED]
have more important problems than fixing
test/* ...)
--
Alexander Mai
[EMAIL PROTECTED]
We're going to have another release ("real") soon.
Are there any outstanding, already submitted fixes which have not yet been
implemented or discussed?
--
Alexander Mai
[EMAIL PROTECTED]
I just found the probably earliest comment in the sources:
rws 24 Feb 1197
What's a Win* 2000 vs. a LessTif 1200 ... ;-)
--
Alexander Mai
[EMAIL PROTECTED]
On Thu, Aug 24, 2000 at 06:10:08PM +0900, R. Lahaye wrote:
> Alexander Mai wrote:
> >
> > We're going to have another release ("real") soon.
> > Are there any outstanding, already submitted fixes which have not yet been
> > implemented or discussed?
>
erwards.
Do we have an expert here who can explain what's wrong here?
---
Alexander Mai
[EMAIL PROTECTED]
dent.
So far there's no unwanted effect cause of this (func doesn't appear out of Draw.c).
--
Alexander Mai
[EMAIL PROTECTED]
27;perfect' piece of code, it
also gets substantially less attention than the libs.
After reading your mail I also started playing with it
and ran into a crash, which I couldn't resolved so far :-\
If there are really people interested in this WM they should tell
now and/or also help to debug it ...
--
Alexander Mai
[EMAIL PROTECTED]
On Fri, 25 Aug 2000 06:04:11 +0900, Mirror Man wrote:
>I make lesstif ftp mirror site of korea.
>Please added lesstif mirror list and reply this mail to me.
Thanks. We added your site to our mirrors list.
Bye,
---
Alexander Mai
[EMAIL PROTECTED]
n alternative one might also attempt a check for general problems,
e.g. memory handling. I tried running mwm inside Xvfb when I got
my crash yesterday (and an "unaligned access" on an alpha/DU system.
Usually I only see those from my Fortran code ;-)
---
Alexander Mai
[EMAIL PROTECTED]
Hope I don't blow my
>charater limit
>sending this.
Well, actually LessTif libs incorporate new patches every day ... hmm let's say week,
so a static LessTif lib isn't a good idea.
Unlike official Motif releases, which were much more "static".
---
Alexander Mai
[EMAIL PROTECTED]
;links, instead of the files.
>consider this a bug in rpm, or we don't have the spec file options correct.
Yup.
Actually the error will be seen in only very rare occasions.
But for a minimum of consistency checks we will keep the same CVSMake for the
few developers and that being used for buildi
The LessTif Core Team is pleased to announce Release 0.91.8 of the
LessTif library.
Since the last official release (note that there was
a '0.91.6' release which was not packaged properly and
never announced) we
- fixed several bugs in the libraries, including critical ones
(i.e. those whic
erly ...) or get a "final" build of Xm.dll from
my homepage (link is in INSTALL.html)
---
Alexander Mai
[EMAIL PROTECTED]
plain the whole difference
- the source archives have sizes
0.91.4 < 0.91.0 < 0.91.8
No idea here - except our distributions vary in their level
of completeness?!
--
Alexander Mai
[EMAIL PROTECTED]
On Fri, Sep 01, 2000 at 07:02:00AM -0400, Rick Scott wrote:
> On 01-Sep-00 at 04:17, Alexander Mai ([EMAIL PROTECTED]) wrote:
> > Now that 0.91.8 is out, I had a look at the archive sizes and found
> > some surprising facts:
> >
> > - lesstif-current is bigger than
had to apply the patch.
Now looking at the diff again (for unknown reasons I kept it ;-)
it "might" be that I missed something, e.g. some lines
which feature a
need_refresh = True;
...
So before bashing Peter for a broken patch someone should investigate
what exactly happened here ...
--
Alexander Mai
[EMAIL PROTECTED]
ad_string,
char *retbuf, short bufsize)
However it seems like short is too short here - and in fact it
is called with a last argument of type >= size_t (being sizeof(Atom) * nents).
What have been the constraints WRT to the signature of this function?
--
Alexander Mai
[EMAIL PROTECTED]
to ask them again. As I recall there were three basic critics
>of the license :
> you, RMS, and I :-)
>
> Danny
Did I miss something special?
What exactly are the issues you're talking about?
I'm only on the OM announce mailinglist IIRC and there's not much
traffic indeed ...
--
Alexander Mai
[EMAIL PROTECTED]
ue to a bug in the code. Probably not the only buggy test
example. Note that running the tests on different platforms is really
helpful here since some environments are less forgiving and therefore
more helpful than others.
--
Alexander Mai
[EMAIL PROTECTED]
ng with companies like IBM ...
(being an OS/2 user and having experience with trying to get them
done something without paying for)
--
Alexander Mai
[EMAIL PROTECTED]
at details is a bit time-consuming since it's
written in C++. Somehow it's really a drawback that from
inside a debugger (at least one like gdb) one can't always
see which code gets executed, but has to figure out by
carefully reading the source code)
--
Alexander Mai
[EMAIL PROTECTED]
Forgot to mention some things
On Tue, Sep 12, 2000 at 05:55:13AM -0400, Rick Scott wrote:
> On 12-Sep-00 at 05:19, Alexander Mai ([EMAIL PROTECTED]) wrote:
> > On Mon, Sep 11, 2000 at 09:46:54PM -0400, Rick Scott wrote:
> > > I finally got around to getting openMotif to compi
On Tue, Sep 12, 2000 at 11:35:42AM -0400, cat2 wrote:
> I think the textf and fsb problems are related to the textf destroy problem.
> So if you got one you probably got them both.
Fine.
More recently introduced crashes to investigate in?
--
Alexander Mai
[EMAIL PROTECTED]
page. Things are still changing - I hope
we get things done some time soon ...
There's also a new commits mailinglist - perhaps we should forward it to
the old one?!)
--
Alexander Mai
[EMAIL PROTECTED]
d the first choice
Another one is just fixed in CVS.
--
Alexander Mai
[EMAIL PROTECTED]
st cases).
Actually my wishlist based from daily usage of 2-3 M*tif apps has only 2 things
remaining which actually make me distinguish between the Motif and LT version
- and for one a patch is reported to come. So if TOG takes sufficiently long and
- as one may now estimate - no major new stuff will come in addition we may even
have the _better_ product.
--
Alexander Mai
[EMAIL PROTECTED]
ve been a good
idea (for Motif) to further go in the C++ direction. I rarely mess around with
C++ but even with small C++ apps it's sometimes a pain to get the
C bindings done properly.
And obviously C++ is still increasing it's market share - at least compared
to C (in my opinion - I have no data about this)
---
Alexander Mai
[EMAIL PROTECTED]
ays find a way to crash which
we can't predict ;-)
---
Alexander Mai
[EMAIL PROTECTED]
ed even gdb 5.0 is there
something better than 's' to really go step by step (following all
constructors's calls, etc.)?
--
Alexander Mai
[EMAIL PROTECTED]
Hmm, I seem to remember a report about problems with
NEdit Cut&Paste (as unresolved) and today I also got a
missing item when marking for delete
from NEdit/LT. Couldn't reproduce, but I can't remember
having seen this earlier. But AFAIK nothing has been changed
in this area?!?
SelectionClear event, losing _MOTIF_ATOM_0 selection
DropSMgr.c:externalSourceHandler(712)
upon each drop action. Do we have 'known' deficiencies in this
drag&drop field?
--
Alexander Mai
[EMAIL PROTECTED]
Attempt to copy to unlocked clipboard!
is showing up now quite often when trying to use cut&paste from NEdit.
It sounds familiar to me - didn't we have something like this earlier??
--
Alexander Mai
[EMAIL PROTECTED]
On Tue, Sep 19, 2000 at 10:49:32AM +0200, Alexander Mai wrote:
> Attempt to copy to unlocked clipboard!
>
> is showing up now quite often when trying to use cut&paste from NEdit.
> It sounds familiar to me - didn't we have something like this earlier??
Hmm, seems lik
in
(especially if someone would also want to move this to SF)
If anyone can offer real good reasons to keep the lesstif-current distributions
(s)he should tell us now!
--
Alexander Mai
[EMAIL PROTECTED]
is this related with LessTif, this is no test/sample of our
distribution?!
--
Alexander Mai
[EMAIL PROTECTED]
indeed makes the new (for now just a dummy) function called.
Any help is appreciated (as usual :-)
--
Alexander Mai
[EMAIL PROTECTED]
27;m not sure about the state of our converters anyway: e.g. string to pixmap
is marked as NONSTANDARD in LessTif, a simple nm call brings up a
CvtStringToPixmap or similar in a Motif 2.0 lib. Do we have to move
some things to the "standard" part?
---
Alexander Mai
[EMAIL PROTECTED]
ght be less pain than some trouble with any binary package)
---
Alexander Mai
[EMAIL PROTECTED]
to move
>> some things to the "standard" part?
>
>xpm is not supported in 1.2.4, but is a part of 2.x. An "lsf Xpm*.c | wc -l" on
>the openMotif tree shows 28 files related to xpm support.
So we should move some stuff from
#ifdef NONSTANDARD_CONVERTERS
to
#if XmVERSION >= 2
?
---
Alexander Mai
[EMAIL PROTECTED]
id=115319&group_id=8596
We hopefully get this done for the next release.
Ted also shows some other problems with LessTif, in behaviour and
appearance. Should be on the list of apps which need some work.
--
Alexander Mai
[EMAIL PROTECTED]
e else would
take at this quite simple thing - but obviously I somehow
don't understand it fully ...
--
Alexander Mai
[EMAIL PROTECTED]
ings
again tomorrow.
For now I'll plug in a late evening fix and then quit to watch some football ... :-P
---
Alexander Mai
[EMAIL PROTECTED]
While debugging where my CFLAGS from the environment got
lost (does anybody noticed this recently?) I got the idea
that we could drop the -DFOO flags from the build process.
Is there any reason not to have these settings within LTconfig.h?
--
Alexander Mai
[EMAIL PROTECTED]
ml
>
[...]
Entries have been added.
BTW, usually this happens faster but we're just moving servers, etc.
and so this got a bit delayed ...
---
Alexander Mai
[EMAIL PROTECTED]
ead
#if defined(NONSTANDARD_CONVERTERS) || XmVERSION > 1
XmRString->XmRPixmap?
and
b) lack some at all, e.g. XmRString->XmRBitmap
This is/was the explanation for the warnings issued by ishmail which
I earlier reported here.
This seems to miss even for the 1.2 version.
--
A
at
http://devrsrc.external.hp.com/STK/man/11.00/XmScrolledWindow_3.html
Here we miss it completly unlike the FileFilter stuff in FileSB.
--
Alexander Mai
[EMAIL PROTECTED]
ngly promote a 2.x version it would be 'nice'
if any binary compatibility related issues would have been solved
as much as possible?
Or would we accept if some version would again (as in the very old past)
break BC?
--
Alexander Mai
[EMAIL PROTECTED]
On Fri, Sep 29, 2000 at 07:46:27AM -0400, Rick Scott wrote:
>
> test16 seems to be getting ~50 class pointers into the class_list, but not all
> of them are getting used!!! It's as if something is getting optimized out :(
You might try the CVS version now ...
--
Alexander Mai
[EMAIL PROTECTED]
wonder why it came up with form w/o dumping core
(this must be by chance?!)
While thinking about it I should better have done it using a
WidgetClass **tmp;
(which in turn might help to explain what was wrong previously)
--
Alexander Mai
[EMAIL PROTECTED]
a working implementation.
XmStringComponentCreate() is probably now on the todo list.
(obviously even OpenMotif = Motif 2.1 won't help you with this library ...)
---
Alexander Mai
[EMAIL PROTECTED]
On Sun, 01 Oct 2000 15:31:10 +0200 (CED), Alexander Mai wrote:
>On Sat, 30 Sep 2000 22:00:39 +0200, [EMAIL PROTECTED] wrote:
>
>>I tried to compile the Xmt library, because I need it for an other program.
>>The linker detects some missing functions:
[...]
A quick search on th
On Mon, Oct 02, 2000 at 02:08:39AM -0700, Alexander Mai wrote:
> Update of /cvsroot/lesstif/lesstif
> In directory slayer.i.sourceforge.net:/tmp/cvs-serv10652
>
> Modified Files:
> CVSMake
> Log Message:
> */CVSMake: add new flag "nodist" (it will
On Mon, Oct 02, 2000 at 12:48:49PM +0200, Alexander Mai wrote:
[...]
> now a problem appears which I can remember from some earlier attempts:
> the 'make' process enters an endless loop after running with CVSMake
> with the 'nodist' flag:
>
> [...]
> make
will back it, but in general LessTif's 2.x
library will improve now since it will become the default LessTif version
soon. This is similar to the old days when just the 1.2 version was
incomplete and default ...
---
Alexander Mai
[EMAIL PROTECTED]
ample,
[...]
I have to confess that this also hurts on OS/2.
Shall we drop the #include - since it's only 3-4 lines of code anyway?
---
Alexander Mai
[EMAIL PROTECTED]
/usr/X11R6/include/X11/bitmaps/Stipple in my case---
> #define stipple_width 2
> #define stipple_height 2
> static char stipple_bits[] = {
>0x01, 0x00};
No, not really correct, but won't induce a crash probably either.
As I outlined we might get rid of this #include to
Motif is
accepting input from the community - we can do not very much.
Adding a few gimmicks to LessTif/OM is certainly not sufficient to
compete with the "newer" toolkits. And for anything else beyond this
you first need to get the manpower ...
Hmm, some news on the choice of the toolkit for the new StarOffice
versions?
--
Alexander Mai
[EMAIL PROTECTED]
ng: Attempt to EndCopy an unlocked clipboard!
copied: 'text-1' to clipboard
Status was XmClipboardNoData
Someone with an idea what to look for?
--
Alexander Mai
[EMAIL PROTECTED]
On Thu, Oct 05, 2000 at 12:11:54PM +0200, Alexander Mai wrote:
> And the actual result of trying to Copy&Retrieve is a failure:
>
> Warning: Attempt to copy to unlocked clipboard!
> Warning: Attempt to EndCopy an unlocked clipboard!
> copied: 'text-1' to clipboard
&
hecked and for whatever reasons many/all 1.2 Xm
headers are missing. Hmm, we're just about to change from 1.2 to 2.0
as the default version, this might be the reason for that omission.
For now if you need/want recent code you could the CVS version -
but that's sometimes painful, too (i.e. this
file like
#ifdef XmVERSION >=2
#define XPMPref Xpm
#else
#define XPMPref _LtXpm
#endif
void XPMPrefFoo(void) {
... }
?
--
Alexander Mai
[EMAIL PROTECTED]
[EMAIL PROTECTED]
On Tue, Oct 10, 2000 at 01:42:01PM +, Carlos A M dos Santos wrote:
> On Tue, 10 Oct 2000, Alexander Mai wrote:
>
> > Meanwhile we have two versions of incorporated Xpm stuff, being
> > lib/Xm/LTXpm.c and lib/Xm-2.0/Xpm.c. This is more or less the same
> > stuff, e
r of exuberant ctags
the existing ones are way too complicated a simple
tags:
ctags -R *
or similar would be sufficient. Adding my own target is possible, but will
result in a new, nonstandard target name ('alex-tags' ;-)?!
--
Alexander Mai
[EMAIL PROTECTED]
deeper with -sync or did you already run the example with
that flag?
(if all fails I can try to dig out some AIX boxes here and look on my own ...)
---
Alexander Mai
[EMAIL PROTECTED]
==BEGIN FORWARDED MESSAGE==
>Date: Thu, 12 Oct 2000 15:36:32 -0400
>From: "Van Brunt, Eric J" <[EMAIL PROTECTED]>
>Subject: RE: XbaeMatrix Widget Problems
>To: "'Alexander Mai'" <[EMAIL PROTECTED]>
I build the
appy, I think.
I think this check is for AIX 3.x only, but I'll anyway add something like this
to the configure script.
--
Alexander Mai
[EMAIL PROTECTED]
Hmm,
what's StarOffice now. Source is available, but on
http://www.OpenOffice.org/dev_docs/source/build.html
they don't list any GUI toolkit as mandatory, but JAVA is required.
Did they switch the GUI to Java and use strongly JNI?
---
Alexander Mai
[EMAIL PROTECTED]
On Sat, 14 Oct 2000 11:08:04 -0400 (EDT), Rick Scott wrote:
>We're committing the changes to the docs with an odd PICO now. Is this what we
>want???
>
Not really.
Mea culpa.
Shall I bring back the old docs/HTML files?
---
Alexander Mai
[EMAIL PROTECTED]
r () from /usr/X11R6/lib/libXt.so.6
#16 0x40203985 in XtDispatchEvent () from /usr/X11R6/lib/libXt.so.6
#17 0x40203d6d in XtAppMainLoop () from /usr/X11R6/lib/libXt.so.6
#18 0x804de71 in main (argc=2, argv=0xb468) at nedit.c:494
Hmm, len looks a bit too large perhaps?!
--
Alexander Mai
[EMAIL PROTECTED]
On Mon, Oct 16, 2000 at 12:13:21PM +0200, Alexander Mai wrote:
> Finally I see problems with clipboar/cutpasted&NEdit on i86 linux, so it's
> really time to work on this.
> Take recent NEdit from CVS, LessTif as of CVS, start, select some arbitrary amount of
> text, cut it
to copy to unlocked clipboard!
Warning: Attempt to EndCopy an unlocked clipboard!
copied: 'text-1' to clipboard
Status was XmClipboardNoData
So what? I'm more or less sure that the libXm is a fresh rebuild,
to ensure I might have a 'make clean && make install' again
On Mon, Oct 16, 2000 at 12:34:34PM +0200, Alexander Mai wrote:
> On Mon, Oct 16, 2000 at 06:29:15AM -0400, Rick Scott wrote:
> > So, how do you make that happen?? I'm up to
> >
> > copied: 'text-54' to clipboard
> >
> > with no problems so f
Need something to fill your lunch/coffee break today?
The attached code crashes (SIGSEGV) with LT and works with Motif 2.0 ...
In XmString line 943 fontstruct seems to be 0x0 ...
--
Alexander Mai
[EMAIL PROTECTED]
/*
* Include File Declarations
*/
#include
#include
#include
#include
n across
those samples from:
February 14, 1992
This directory contains the source files for the example programs that
are presented in "Mastering Motif Widgets." The programs have been
improved and several added since the original book was printed in February.
---
Alexander Mai
[EMAIL PROTECTED]
for nothing.
And being here I can mention that the CVSweb interface that used to be broken
(for an unknown period of time) is fixed since a couple of hours.
Staff at SF reacted in a very short time upon my report.
--
Alexander Mai
[EMAIL PROTECTED]
Recently I posted this scaledemo.c (or whatever it was called).
It works on linux with Motif 2.0 and DU with 1.2 but crashes
with LessTif (2.x). I just got the executable from the linux box
with Motif and tried here on that w/o - it works.
--
Alexander Mai
[EMAIL PROTECTED]
ing a BulletinBoard it got hit by some nonsense in
the label_fonst_list resource which in turn finally triggers a SIGSEGV,
picture is the very same on DU and linux on alpha.
--
Alexander Mai
[EMAIL PROTECTED]
y list of things to
do for LessTif I18N (and related) would be close to the lower end ...
But it's certainly not helpful to see people advice to use gtk and
even don't add a link to LT though they mention it.
--
Alexander Mai
[EMAIL PROTECTED]
memory leaks. However
looking at the mailinglist archive I see nothing which relates to Fontlist.c?!
Finally: the CVS log doesn't mention the author of test8 ...
Note that I haven't yet checked in a version which is less broken. I fixed
at least the function arguments lists, etc.
---
Alexander Mai
[EMAIL PROTECTED]
en it somehow managed to pass the SEGFAULT ...
Our spinbox samples seem to work (at least not crash immediately) so
one might have to dig out what's wrong ...
---
Alexander Mai
[EMAIL PROTECTED]
looks for some libs to be found.
Perhaps we should enhance our generic Motif-search macro?
--
Alexander Mai
[EMAIL PROTECTED]
f.org/FAQ.html) states
Is UIL (User Interface Language) supported?
Not really. Though there is some old code in place already it's unlikely you
succeed
with a project using it.
---
Alexander Mai
[EMAIL PROTECTED]
h more
> functionality in Xt than in FLTK. And FLTK is C++, leading to larger
> executable code. Look at this:
[...]
Well, true but not whole truth. The power of a library is not
proportional to the executable size ... If things ("features") would be
somehow independent you would have a chanc
get feedback about
remaining portability issues ...
---
Alexander Mai
[EMAIL PROTECTED]
r's side, not on the authors of the toolkit ...
--
Alexander Mai
[EMAIL PROTECTED]
ear n=130 I got another maximum
even harder to explain than the previous result ...
Optimization level for libXm and test9 was supposed to be -O1,
perhaps I should try again with -O0.
--
Alexander Mai
[EMAIL PROTECTED]
tif.cpp:106: since the following virtual functions are abstract:
> nsGfxFactoryMotif.cpp:106: nsresult nsIFontMetrics::GetNormalLineHeight(nscoord
>&)
[...]
This is (most probably) not a lesstif-related problem.
Does this mozilla release officially support Motif ??
I thought support
and guess I better don't search for
a few bytes memory per widget but for something more important ...
--
Alexander Mai
[EMAIL PROTECTED]
or "similar".
My explanation is that this interface might be older than "size_t" ?!
---
Alexander Mai
[EMAIL PROTECTED]
The mentioned test crashes here on at least two machines.
Did this example work previously or does it still work for anyone else?
--
Alexander Mai
[EMAIL PROTECTED]
r a proper bug report you should give more information, e.g.
the platforms and the versions of LessTif you are using.
The basic requirements are, of course, to have the most recent version
of LessTif installed (being 0.91.8) and have built the widget set
against the recent headers and libs.
--
Alexander Mai
[EMAIL PROTECTED]
On Wed, Nov 08, 2000 at 05:56:40AM -0500, Rick Scott wrote:
> Shows all good for me, both LessTif and OM.
>
>
> On 08-Nov-00 at 04:05, Alexander Mai ([EMAIL PROTECTED]) wrote:
> > The mentioned test crashes here on at least two machines.
> > Did this example work pre
Though there's the supplied patch in CVS meanwhile this might be of interest ...
--
Alexander Mai
[EMAIL PROTECTED]
Alexander,
You wrote:
> just trying to build an example showing the crash you mentioned yesterday.
> I took some example as of test/Xm/tex with a text widget, writ
101 - 200 of 576 matches
Mail list logo
