Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!oliveb!amiga!jimm From: jimm@amiga.UUCP (Jim Mackraz) Newsgroups: comp.sys.amiga Subject: Re: 1.3 includes Message-ID: <3053@amiga.UUCP> Date: 23 Oct 88 23:32:49 GMT References: <8377@cit-vax.Caltech.Edu> <215@antares.UUCP> <2879@sugar.uu.net> <3048@amiga.UUCP> <2884@sugar.uu.net> Reply-To: jimm@cloyd.UUCP (Jim Mackraz) Organization: Commodore-Amiga Inc, Los Gatos CA Lines: 69 In article <2884@sugar.uu.net> peter@sugar.uu.net (Peter da Silva) writes: )In article <3048@amiga.UUCP>, jimm@amiga.UUCP (Jim Mackraz) writes: )> My understanding is that the official V1.3 include files will have )> struct Preferences the same size as V1.2 (else, DOS is confused). ) )Why is DOS confused? I mean, Prefs seems designed to allow extensibility. )What went wrong? The dos does some validation based on size, wrongly, which effects moving preferences file from new disks to old, and so on. )> The Row/ColumnSizeChange stuff is the somewhat unauthorized 'morerows' )> stuff. It should survive in name and function. It should NOT be used )> by any program except morerows, or the equivalent. ) )I should hope so, since it was in the 1.2 Prefs with NO indication that it )was unauthorised. I hope you didn't assume it was usable by a program other than morerows or the equivalent. )> The wb_Width/Height/Depth stuff aren't specifically Hedley, but specify )> a scrolling Workbench screen. This is not implemented (at least correctly) )> in any available software, released or in public alpha/beta. Don't )> touch or even look. )Too late... my 'prefs' program (posted to comp.sources.amiga) lets anyone look. )Not to mention touch. Hey, that's great. Your program or users' behavior might interfere with later system software. I expect the users will be able to tell. )> The ext_size was for an extension scheme which we have abandonded in )> favor of a more general, modular, extensible preferences scheme. )> Don't touch or look. )Too late. Too bad. I hope you don't count too heavily on its values, which are not documented. )I doubt if many people other than me are actually using the program, and I )certainly don't hack those fields. Well, I was kind of counting on that. )> )I discovered this when told my 'prefs' program (which assumed the Aztec 3.6 )> )files) wouldn't compile with 3.4 and the Amiga 1.2 includes. ) )> Please EMail exactly what the problem was: I don't see where incompatibility )> would arise if you were not using the new fields. Thanks. ) )I *am* using the new fields. When I wrote the program I just copied the fields )from the latest includes I had handy... the Aztec 3.6 ones. This makes it )obvious what the problem was... other people didn't have the new files. )-- ) Peter da Silva `-_-' peter@sugar.uu.net You'll like V1.4 Intuition: nothing you aren't allowed to play with in Intuition will be present in the include files. I'm assigning Reserved[4] to a function key. jimm -- Jim Mackraz, I and I Computing amiga!jimm BIX:jmackraz Opinions are my own. Comments regarding the Amiga operating system, and all others, are not to be taken as Commodore official policy.