Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!husc6!rutgers!bellcore!texbell!tness1!sugar!peter
From: peter@sugar.uu.net (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: 1.3 includes
Message-ID: <2903@sugar.uu.net>
Date: 25 Oct 88 11:48:35 GMT
Article-I.D.: sugar.2903
References: <8377@cit-vax.Caltech.Edu> <215@antares.UUCP> <2879@sugar.uu.net> <3058@amiga.UUCP>
Organization: Sugar Land Unix - Houston, TX
Lines: 51

In article <3058@amiga.UUCP>, jimm@amiga.UUCP (Jim Mackraz) writes:
> In article <2900@sugar.uu.net> peter@sugar.uu.net (Peter da Silva) writes:
> )In article <3053@amiga.UUCP>, jimm@amiga.UUCP (Jim Mackraz) writes:
> )> The dos does some validation based on size, wrongly, which effects
> )> moving preferences file from new disks to old, and so on.

> )I hope this is fixed in a later version, rather than going to something
> )nonstandard.

> Hey, big guy, we ARE the standard.

Yeh, I know. I thought after I sent it that my phrasing was totally weird. But
I hope you understand what I'm trying to say... there are hooks in the existing
Prefs design for changing the size of the structure and file, and you have in
the past indicated that people shouldn't depend on the size of the file staying
constant.

By the way, that "we ARE the standard" line didn't work for AT&T. And they're
much bigger than Commodore-Amiga. I hope you can keep the system in line, tho',
without stifling creativity.

Speaking of which, what are you doing about multiple serial ports? Eventually
you're gonna get sick of me asking, and you'll post something about this
new grand scheme you've been hatching on Bix. Why not now?

> Sounds fine.  Note that Preferences does some measure of validity
> checking on some things (e.g., PointerTicks) which are not documented.

Shoulda put those validity checks into SetPrefs, probably (monday-morning
quarterbacking at its finest).

> Poking preferences values without the help of a Commodore program (which
> doesn't include morerows, by the way) might just lead one into
> the cracks in the Preferences scheme.  Caveat user.

I've been doing it for 6 or 8 months now without problems.

> Making frequent calls to SetPrefs at runtime to carve some desired
> behavior out of the system is another way to get stuck in a crack.
> Caveat programmer. 

Ditto. No cracks. A few warts.

> I feel like that all the time.

You sound like Steven Wright.
-- 
		Peter da Silva  `-_-'  peter@sugar.uu.net
		 Have you hugged  U  your wolf today?

	Disclaimer: I accept full responsibility for my own typos.