1. Re: David Cuny's editor/GUI
David Cuny writes:
> The problem is in polygon() function in the routine graphic_window(), in
> win95.e. The polygon is not being filled with the correct color. This is a
> bit strange, because the command button which uses a similar call later
> works just fine.
I tried to duplicate this on my win95 machine but was not able to.
I set up your editor for graphics using the win95 style of interface.
It seemed to run ok, but maybe I missed something.
> There is another anomoly - when I trace() the code, the problem corrects
> itself. Remember that one of the big selling points of Euphoria is that
> putting in trace code is not supposed to make problems appear or disappear.
One Euphoria problem I did see however is where you use mem_copy() to
write to the screen. In the current release, mem_copy() might
write to the trace screen, rather than the main output screen.
(Similar to the poke bug that you reported a long time ago).
I fixed this a couple of weeks ago, and the fix will be in the
next release. However, even with this fix, I found that my trace screen
got temporarily messed up when your display_clean_image() was executed.
It does mem_copy() as well as some low-level video port I/O.
I wonder if this port I/O could be causing the palette problems.
Anyway, if you can send me step-by-step instructions for observing
the polygon bug, I'd be happy to investigate it.
Regards,
Rob Craig
Rapid Deployment Software
