On Fri, 21 Sep 2012, Marcin Cieslak wrote:
> + union {
> + XtPointer ptr;
> + Dimension dim;
> + } wide;
> + XtVaGetValues(dir_label, XmNwidth, &wide.ptr, NULL);
> + d_width = wide.dim;
> + XtVaGetValues(file_label, XmNwidth, &wide.ptr, NULL);
> + f_width = wide.dim;
Sorry, t
When asking for data using XtVaGetValue()
make sure that there is enough place for
the return value (which is sometimes XtPointer).
Providing pointer to (int) is not enough.
Cast XtPointer into requested int types
directly, which unfortunately introduces
compilation warning:
cast from pointer to
Hiya everybody,
This is a quick status update so that you all know I'm still working on this
.
The pkgsrc freeze for 2012Q3 started last Sunday and I had to get some
stuff fixed before that, so with that out of the way I'm focusing more
on porting CDE to NetBSD (and when I'm done with that Drago
On Sat, 22 Sep 2012, Jelle Hermsen wrote:
> The pkgsrc freeze for 2012Q3 started last Sunday and I had to get some
> stuff fixed before that, so with that out of the way I'm focusing more
> on porting CDE to NetBSD (and when I'm done with that Dragonfly).
CDE on FreeBSD works pretty nice now (o
On Sat, 22 Sep 2012, Marcin Cieslak wrote:
> When asking for data using XtVaGetValue()
> make sure that there is enough place for
> the return value (which is sometimes XtPointer).
> Providing pointer to (int) is not enough.
>
> Cast XtPointer into requested int types
> directly, which unfortunate
On Fri, 21 Sep 2012, Marcin Cieslak wrote:
> Casting (int) to (char **) will not
> prevent crash on a 64-bit system.
>
> A proper ANSI prototype has been added.
Applied.
--
Jon Trulson
The Higgs Field is what make atoms matter.
-- Tom L.
On Sat, 22 Sep 2012, Marcin Cieslak wrote:
> On Sat, 22 Sep 2012, Jelle Hermsen wrote:
>
>> The pkgsrc freeze for 2012Q3 started last Sunday and I had to get some
[...]
> I am not the gatekeeper but I don't mind partial patches as long
> as they don't break other builds. Feel free to experiment on
Hiya,
Thanks Marcin for the elaborate update on the FreeBSD side of things. I'm
definitely a proponent of using CSRG_BASED and have_something macros. It would
be great if you would only need to teach one configuration header about an OS,
defining a bunch of have_something macros in there. Howeve