Re: [Plplot-devel] plimage

[Joao C. <jc...@fe...>]

On Tuesday 08 January 2002 9:22 am, Olof Svensson wrote:
> Hi Jo=E3o,
>
> thanks for you answer! Now I understand better why you you need the
> pixel co-ordinates and I think your planned improvements of plimage
> sound great. I had a discussion with Alessandro this morning and we
> agreed on the following points:
>
> The best solution is probably to create a second entry point for passin=
g
> an image as a PLFLT * pointer. There are two possibilities, either by
> using a flag telling plimage which type of pointer is passed (to avoid
> creation of unused arrays in the case of rectangular images) or by
> creating a new plplot image command.

Perhaps the latter will be more user understandable. It could just set a=20
variable in plstrm.h (that could be used  also by drivers), and call the=20
standard plimage().

> Concerning plxormod, I made some tests with the xwin and win3 devices
> and found that everything works fine unless you resize the window
> between two selections. What happens is that since plxormod is turning
> the plbuf_write off the selection rectangle is not redisplayed when
> resizing the window, and when you make a new selection the program
> (x20c) retraces the old rectangle and it becomes visible. (In fact, wit=
h
> the xwin device the resizing of the window makes the image disappear
> completely, however the old selection reappears as on the win3 device).

There are other resize/redraw issues in the new xwin plimage implementati=
on.=20
The worse being that, as I now use XGetImage(), it fails if the plot wind=
ow=20
is not completely visible!

> Maybe it is not a very important problem, but for some applications tha=
t
> we plan to do in the future we would like to keep the possibility to
> keep the PLESC commands.

OK, but probably I will changes their names, as I found the current ones =
too=20
cryptic.

Jo=E3o

>
> Regards,
>
> Olof