On Thu, 20 Jan 2000, David Fedor wrote:

> >Could you expand on the "can not edit graphics" bug? There were a few
> >major things... [many graphics bugs described]
> 
> Briefly, don't bother editing graphics in this version of Windows
> constructor.  The editor is busted.
> 
> The appropriate engineer has been hacking and slashing the code on this for
> the past week, and as soon as we have the graphic editor fixed and reliable
> (and better than it was in r6) we'll post it.

Then may I ask (please don't take this as rudeness), why was it released
then?  Considering that one of the major features people (or at least me)
have been waiting for was the color graphics editing.

BTW, just curious, I take icon editing is in that "being fixed" block (I
hope).

> Use everything else, but don't waste time trying to use the graphic editor.
> (Remember, this is prerelease, where you're guaranteed that it isn't
> shipping quality yet!)

Ok, I know this will open a can of worms, but I don't think some of the
stuff I paid for in R6 was shipping quality.  I ended up having to use
pilrc to eventually get around the black icon problem.... <steps off of
soapbox> ;)

> >And question on the Icon/Bitmap Families, are they OS backwards
> >compatible?
> 
> Yes.  All the way back to 1.0, assuming you've got a black and white member
> in the family.

Excellant.. exactly what I was hoping for!!

Thank you.

James Lee, [EMAIL PROTECTED]
Seahorse Software, http://www.seahorsesoft.com/

Reply via email to