I've found this bug kicks in when you modify a bitmap that is currently in
use by a form. If you delete the bitmap from the form before you modify it
and then replace it back into the form, constructor doesn't slow down. Of
course, who wants to remove a bitmap before you need to edit it? But, if
Constructor acts really slow, I haven't found a way to get it back to normal
speed (even if you remove all bitmaps it doesn't fix the problem)
-----Original Message-----
From: Elia Freedman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, July 30, 1999 11:02 AM
Subject: RE: Bitmaps in Constructor
>Nope... just a bug. I have the same problem but it is indiscriminant.
>Sometimes one bitmap, sometimes two, sometimes it slows down, sometimes it
>doesn't. Rev 6 is due later this year, I guess. Hopefully they will fix
>this and other bugs.
>
>Elia
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>Sent: Friday, July 30, 1999 7:51 AM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Bitmaps in Constructor
>
>
>
>I am using Metrowerks Constructor 1.0.3 (is this the latest
>version?). When I create a form with more than 2 bitmaps on it,
>the constructor gets REALLY slow, and often crashes. The generated
>code seems to work fine on the Palm though.
>
>Is there a patch or workaround to make the constructor work better
>for making forms with bitmap in them?
>
>Thanks,
>Brad Myers
>
>
>
