[squeak-dev] Something in the update process damages the
background
Chris Muller
asqueaker at gmail.com
Thu Sep 12 02:13:16 UTC 2013
On Wed, Sep 11, 2013 at 2:52 PM, karl ramberg <karlramberg at gmail.com> wrote:
> I agree with this. Look for a user set background, if nil do default fill,
I don't understand your proposal. The background just _is_ whatever
it is. We set it during the release process. When someone downloads
a release image, they either "set the background" to a color,
gradient, pattern, or bitmap of their choice or, they don't. How are
you going to "look for a user set background?" When would such a
thing be done? Upon loading Morphic? Why? Why not just leave it as
is?
>
> Karl
>
>
>
> On Wed, Sep 11, 2013 at 9:04 PM, tim Rowledge <tim at rowledge.org> wrote:
>>
>>
>> On 11-09-2013, at 11:58 AM, Bob Arning <arning315 at comcast.net> wrote:
>>
>> > Well, since the whole point of this snippet is to change your project's
>> > background, I'd say you simply want to delete it. Then you can rely on
>> > whatever you do in release building to set the background for the standard
>> > image and everybody else keeps their background as-is.
>>
>> It seems to me that the pattern ought to be along the lines of
>> if user has set a specific preference, leave things alone
>> if not, reset the default
>> if that requires a redisplay/explosion/descent-down-the-rabbit-hole, do
>> it.
>>
>> tim
>> --
>> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
>> Strange OpCodes: DNPG: Do Not Pass Go
>>
>>
>>
>
>
>
>
More information about the Squeak-dev
mailing list
|