Menu
▾
▴
gnuplot-beta
|
From: Ethan A M. <merritt@u.washington.edu> - 2006-06-21 15:37:10
|
"Mojca Miklavec" <moj...@gm...>
has reported that the "with image" demo produces very strange
output on his Windows system.
On Wednesday 21 June 2006 08:29 am, Daniel J Sebald wrote:
> I'm fairly certain that this bug has to do with the fact that in Windows,
> with the CR/LF, the following may be dogdy in some way:
>
> if (!i_line) {i_line = ASCII_PER_LINE; *encoded_image_ptr++ = '\n';}
Except that we haven't heard of this problem from anyone else.
It's part of the standard "all.dem" check in the build process.
Surely *someone* would have noticed if the demos fail under Windows.
Petr? Bastian? Anyone running Windows?
--
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle 98195-7742
|
|
From: <br...@ph...> - 2006-06-22 02:17:44
|
Ethan Merritt wrote: > Binary files in cvs are supposed to be tagged with a special > marker so the download to Windows is performed correctly. > Was this done for bluetux.rgb? As a matter of fact, it wasn't. > (And how does one check this?) Sticky option '-kb' must be set. The state of sticky options is displayed by 'cvs status' (or whatever your CVS client's equivalent of that happens to be). |
|
From: Ethan M. <merritt@u.washington.edu> - 2006-06-22 00:03:07
|
On Wednesday 21 June 2006 03:15 pm, Hans-Bernhard Br=F6ker wrote: > Ethan Merritt wrote: > > Binary files in cvs are supposed to be tagged with a special > > marker so the download to Windows is performed correctly. > > Was this done for bluetux.rgb? > > As a matter of fact, it wasn't. > > > (And how does one check this?) > > Sticky option '-kb' must be set. The state of sticky options is > displayed by 'cvs status' (or whatever your CVS client's equivalent > of that happens to be). OK. So none of the binary files in .../demo were marked as such. I've now marked added the flags, and hopefully this will fix the problem. Could you Windows guys please give it time to propagate to the anonymous server, and then update the contents of .../demo and try again? =2D-=20 Ethan A Merritt Biomolecular Structure Center University of Washington, Seattle WA |
|
From: Daniel J S. <dan...@ie...> - 2007-05-05 04:08:51
|
Mojca, Just wondering if you have a real word example of an alpha image and its application for a plot. Can you think of any data or combination of data where you'd like to do alpha compositing? Dan |
|
From: <tim...@en...> - 2006-06-21 16:51:29
|
Ethan A Merritt wrote:
> "Mojca Miklavec" <moj...@gm...>
> has reported that the "with image" demo produces very strange
> output on his Windows system.
>
> On Wednesday 21 June 2006 08:29 am, Daniel J Sebald wrote:
> =20
>> I'm fairly certain that this bug has to do with the fact that in Windo=
ws,=20
>> with the CR/LF, the following may be dogdy in some way:=20
>>
>> if (!i_line) {i_line =3D ASCII_PER_LINE; *encoded_image_ptr++ =3D =
'\n';}
>> =20
>
> Except that we haven't heard of this problem from anyone else.
> It's part of the standard "all.dem" check in the build process.
> Surely *someone* would have noticed if the demos fail under Windows.
>
> Petr? Bastian? Anyone running Windows?
> =20
I don't remember if I tried for the 'win' terminal, but I am sure the=20
wxWidgets one works with image.dem under Windows.
By the way, the quoted line above belongs to post.trm, so in case it is=20
relevant, it would appear for the postscript terminal, which doesn't=20
work for other reasons ;-)
Timoth=E9e
|
|
From: <br...@ph...> - 2006-06-21 20:45:24
|
Ethan A Merritt wrote:
> "Mojca Miklavec" <moj...@gm...>
> has reported that the "with image" demo produces very strange
> output on his Windows system.
>
> On Wednesday 21 June 2006 08:29 am, Daniel J Sebald wrote:
>> I'm fairly certain that this bug has to do with the fact that in Windows,
>> with the CR/LF, the following may be dogdy in some way:
>>
>> if (!i_line) {i_line = ASCII_PER_LINE; *encoded_image_ptr++ = '\n';}
Only if the file was opened in the wrong mode. I'm reasonably sure
gnuplot doesn't get this so spectactularly wrong.
The most likely explanation is that the binary data files got mangled on
the way from CVS to Mojca's Windows box, because some tool though it had
to convert Unix to Microsoft style linebreaks (cygwin CVS to a text-mode
mounted file system, or similar).
|
|
From: Daniel J S. <dan...@ie...> - 2006-06-21 20:50:22
|
Hans-Bernhard Br=F6ker wrote:
> Ethan A Merritt wrote:
>=20
>>"Mojca Miklavec" <moj...@gm...>
>>has reported that the "with image" demo produces very strange
>>output on his Windows system.
>>
>>On Wednesday 21 June 2006 08:29 am, Daniel J Sebald wrote:
>>
>>>I'm fairly certain that this bug has to do with the fact that in Windo=
ws,=20
>>>with the CR/LF, the following may be dogdy in some way:=20
>>>
>>> if (!i_line) {i_line =3D ASCII_PER_LINE; *encoded_image_ptr++ =3D =
'\n';}
>=20
>=20
> Only if the file was opened in the wrong mode. I'm reasonably sure=20
> gnuplot doesn't get this so spectactularly wrong.
>=20
> The most likely explanation is that the binary data files got mangled o=
n=20
> the way from CVS to Mojca's Windows box, because some tool though it ha=
d=20
> to convert Unix to Microsoft style linebreaks (cygwin CVS to a text-mod=
e=20
> mounted file system, or similar).
Ahead of you, but good assessment! (I won't say "guess".) About 10 minu=
tes ago I emailed:
> Does the attached PNG look familiar?
>=20
> The size of the file is incorrect:
>=20
> -rw-r--r-- 1 sebald users 49225 Sep 1 2004 blutux.rgb
>=20
> The image is supposed to be 128 x 128 x 3 =3D 49152.=20
|
|
From: Ethan M. <merritt@u.washington.edu> - 2006-06-21 21:58:46
|
On Wednesday 21 June 2006 01:45 pm, Hans-Bernhard Br=F6ker wrote:
> Ethan A Merritt wrote:
> > On Wednesday 21 June 2006 08:29 am, Daniel J Sebald wrote:
> >> I'm fairly certain that this bug has to do with the fact that in
> >> Windows, with the CR/LF, the following may be dogdy in some way:
> >>
> >> if (!i_line) {i_line =3D ASCII_PER_LINE; *encoded_image_ptr++ =3D
> >> '\n';}
>
> Only if the file was opened in the wrong mode. I'm reasonably sure
> gnuplot doesn't get this so spectactularly wrong.
>
> The most likely explanation is that the binary data files got mangled
> on the way from CVS to Mojca's Windows box, because some tool though
> it had to convert Unix to Microsoft style linebreaks (cygwin CVS to a
> text-mode mounted file system, or similar).
Binary files in cvs are supposed to be tagged with a special=20
marker so the download to Windows is performed correctly.
Was this done for bluetux.rgb? (And how does one check this?)
=2D-=20
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle WA
|
|
From: Daniel J S. <dan...@ie...> - 2006-06-21 22:22:29
|
Ethan Merritt wrote: > Binary files in cvs are supposed to be tagged with a special > marker so the download to Windows is performed correctly. > Was this done for bluetux.rgb? (And how does one check this?) Good question. I've been searching the CVS documentation for just that. I recall reading something about this long ago. I thought maybe it put a little "b" next to the file when it transfers. But since I don't know that is supposed to happen, I'm not sure. Could have something to do with that SF server shut down and the transfer of files. Maybe they lost the binary flag or something? Dan |
