discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strange Gorm/ProjectCenter behaviour ... bug?


From: MJ Ray
Subject: Re: Strange Gorm/ProjectCenter behaviour ... bug?
Date: Sun, 08 Dec 2002 12:30:38 GMT
User-agent: slrn/0.9.7.4 (Linux)

<void_s@ihug.com.au> <void_s@ihug.com.au> wrote:
> The problem is in any editing field, when the escape key is pressed, 
> the program inputs the escape key into the field as a little 
> dotted-outline square. This takes up space in the string, is part of 
> the string, but neither backspace, nor the mouse selection, nor 
> delete will erase it.

This might be a bug with the text entry field from the way you describe it. 
I think that's a work in progress, so hopefully that will be corrected soon.

Sorry I can't give you a happier message.

Hello to the mailing list from the newsgroups once again!
>From marcel@metaobject.com Mon Dec 09 09:07:18 2002
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
        id 18LOZ3-0002H8-00
        for discuss-gnustep@gnu.org; Mon, 09 Dec 2002 09:07:17 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
        id 18LOZ0-0002Fy-00
        for discuss-gnustep@gnu.org; Mon, 09 Dec 2002 09:07:17 -0500
Received: from mailout11.sul.t-online.com ([194.25.134.85])
        by monty-python.gnu.org with esmtp (Exim 4.10.13)
        id 18LOYz-0002Fd-00
        for discuss-gnustep@gnu.org; Mon, 09 Dec 2002 09:07:13 -0500
Received: from fwd02.sul.t-online.de 
        by mailout11.sul.t-online.com with smtp 
        id 18LOYv-0006Lo-0F; Mon, 09 Dec 2002 15:07:09 +0100
Received: from metaobject.com (320089961391-0001@[217.88.120.237]) by
        fmrl02.sul.t-online.com
        with esmtp id 18LOYo-1L8ooiC; Mon, 9 Dec 2002 15:07:02 +0100
Date: Mon, 9 Dec 2002 15:07:00 +0100
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v551)
To: Andreas Hoeschler <ahoesch@smartsoft.de>
From: Marcel Weiher <marcel@metaobject.com>
In-Reply-To: <3DC04C02-0923-11D7-A5F6-003065CCA582@smartsoft.de>
Message-Id: <7C8FB402-0B7F-11D7-ABAC-00039366F3C0@metaobject.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.551)
X-Sender: 320089961391-0001@t-dialin.net
X-Mailman-Approved-At: Mon, 09 Dec 2002 10:30:50 -0500
cc: discuss-gnustep@gnu.org
Subject: Re: Converting TIFF to JPG/GIF/PNG
X-BeenThere: discuss-gnustep@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Discussion list for the GNUstep programming environment
 <discuss-gnustep.gnu.org>
List-Help: <mailto:discuss-gnustep-request@gnu.org?subject=help>
List-Post: <mailto:discuss-gnustep@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/discuss-gnustep>,
        <mailto:discuss-gnustep-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/discuss-gnustep>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/discuss-gnustep>,
        <mailto:discuss-gnustep-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 09 Dec 2002 14:07:18 -0000


On Friday, December 6, 2002, at 03:01  Uhr, Andreas Hoeschler wrote:

> Hi all,
>
> I have to convert TIFF --> JPG/GIF on the fly. The images stored in 
> the database are in TIFF. The application (GNUstep tool) is supposed 
> to return them in JPG/GIF or PNG format. On MacOSX I do
>
>       NSBitmapImageRep *imageRep = [NSBitmapImageRep 
> imageRepWithData:[_image
>       TIFFRepresentationUsingCompression:NSTIFFCompressionLZW factor:15.0]];
>       _jpgData = [[imageRep representationUsingType:NSJPEGFileType 
> properties:properties] retain];

Silly question:   why are you doing the TIFF-encoding step at all?   
After all, you're taking the image (initialized from a file?), 
converting that to TIFF, then getting an image (NSBitmapImageRep) again 
and then convering that to JPEG.

Why not get a JPEG-representation directly?  Just get the 
NSBitmapImageRep (from a file or wherever) and then get its 
JPEG-representation.

And if you determine you absolutely need to go via an intermediate 
TIFF-step (I can't see a good reason why), simply don't apply LZW 
compression to it.  BTW:  the compression factor is meaningless for LZW 
compression.

Marcel

-- 
Marcel Weiher                           Metaobject Software Technologies
marcel@metaobject.com           www.metaobject.com
Metaprogramming for the Graphic Arts.   HOM, IDEAs, MetaAd etc.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]