tc008@zeus.unomaha.edu (10/02/90)
A few C question that hopefully will be answered:
1. in V36/2.0, I tried using a flag that would show the sizing gadget in
the upper right hand corner and not display the one in the lower right hand
corner. I forgot what the name of this flag was... but anycase in the header
for intuition.h it said that this would automatically pop up without the sizing
gadget in the lower corner. Any ideas.
2. Knowing that we can change the fonts (3 separate categories) I found
something that must be must be dealt with which I did not see in any manuals.
When I use a string gadget. I see you can call out andpoint to the intuiText
where then you can change the font of that text for printing. My question is
how can you make the input text that you type in any font you ask for instead
of having the system default. The reason for this is that if you make borders
and have text inside of that. When some one new comes and uses your program
with a different system font. It's not good.
3. I have a question for all you database gurus. How do you keep storage
for all the variable when a user is using a database package which will allow
one to customize the records. Can you allocate variables on the fly?? I am not
really familiar with this procedure. Ex: PowerBase for IBM.peter@cbmvax.commodore.com (Peter Cherna) (10/09/90)
In article <1886.27085b45@zeus.unomaha.edu> tc008@zeus.unomaha.edu writes: >A few C question that hopefully will be answered: > > 1. in V36/2.0, I tried using a flag that would show the sizing gadget in >the upper right hand corner and not display the one in the lower right hand >corner. I forgot what the name of this flag was... but anycase in the header >for intuition.h it said that this would automatically pop up without the sizing >gadget in the lower corner. Any ideas. There is no supported way to move the size gadget, not in 1.x nor in 2.0. You're probably thinking of SIZEBRIGHT and SIZEBBOTTOM, which are flags that help you control in which border the gadget is. The gadget is always in the bottom right corner, but can be in the bottom border or the right border (or both). If you notice that Shell windows have a blank strip the width of the size gadget running down the right side, that tells you that the size gadget is in the right border. Under 2.0, it's very clear in which border the gadget is. > 2. Knowing that we can change the fonts (3 separate categories) I found >something that must be must be dealt with which I did not see in any manuals. >When I use a string gadget. I see you can call out andpoint to the intuiText >where then you can change the font of that text for printing. My question is >how can you make the input text that you type in any font you ask for instead >of having the system default. The reason for this is that if you make borders >and have text inside of that. When some one new comes and uses your program >with a different system font. It's not good. Under 2.0, you can supply a StringExtend structure, which lets you specify the font to use. Peter -- Peter Cherna, Software Engineer, Commodore-Amiga, Inc. {uunet|rutgers}!cbmvax!peter peter@cbmvax.cbm.commodore.com My opinions do not necessarily represent the opinions of my employer. "Television is a medium because it is neither rare nor well-done." - E. Kovacs
peter@sugar.hackercorp.com (Peter da Silva) (10/12/90)
In article <14989@cbmvax.commodore.com> peter@cbmvax.commodore.com (Peter Cherna) writes: > If you notice that Shell windows have a blank strip > the width of the size gadget running down the right side, that tells you > that the size gadget is in the right border. Under 2.0, it's very clear > in which border the gadget is. Speaking of the Shell windows... Given that you have to track a fair amount of information to handle redrawing of the shell window on resize anyway, how hard would it be for y'all to stick a scroll bar in that blank strip before you cast 2.0 in ROM? -- Peter da Silva. `-_-' <peter@sugar.hackercorp.com>.
jesup@cbmvax.commodore.com (Randell Jesup) (10/23/90)
In article <6781@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes: >Speaking of the Shell windows... > >Given that you have to track a fair amount of information to handle redrawing >of the shell window on resize anyway, how hard would it be for y'all to stick >a scroll bar in that blank strip before you cast 2.0 in ROM? Yeah, except that information is in the console.device, not the CON: handler. It could be done, but would probably eat several K we don't have of ROM, and take several weeks or more of someone's time (not counting QA/testing). -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com BIX: rjesup Common phrase heard at Amiga Devcon '89: "It's in there!"
joseph@valnet.UUCP (Joseph P. Hillenburg) (10/25/90)
You mean to tell me that even though the the 1.3 ROM's had space left, even though they were 256k, you've managed to fill the 512k 2.0 ROM's to the brim? -Joseph Hillenburg UUCP: ...iuvax!valnet!joseph ARPA: valnet!joseph@iuvax.cs.indiana.edu INET: joseph@valnet.UUCP
jesup@cbmvax.commodore.com (Randell Jesup) (11/08/90)
In article <5mHkR10w163w@valnet> joseph@valnet.UUCP (Joseph P. Hillenburg) writes: >You mean to tell me that even though the the 1.3 ROM's had space left, >even though they were 256k, you've managed to fill the 512k 2.0 ROM's to >the brim? Well, graphics is now ~100K, workbench is now ~70K, intuition is about ~100K, dos is ~37K, gadtools is ~25, console is ~16, fs is ~20, icon is another 10, shell (and the built-in commands) is another 18, etc, etc. (Check out the mods listing in wack1.0 - it's a pain, but you can figure out the approximate size of each module). A lot of things were added (gadtools, etc), a lot of other things grew (intuition, graphics, wb, dos/shell/fs/con-handler), etc. Remember that code expands to fill all available space. Unix is a prime example of this. :-) Even timer.device got bigger (it also got far more accurate). Some of the stuff had been intended for disk - Wb, gadtools, icon, ieeesingbas, ramdrive, etc. Other stuff was needed to support ECS chips (>1024-pixel lines, etc), Hedley screens, the "new look", public screens, all the new gadget stuff in intuition (boopsi, etc), etc, etc. There was stuff that didn't fit in rom, though - diskfont didn't (don't know why), asl didn't, etc. Other things may leave rom again in the next version. Oh well. Having all that in ROM makes it boot amazingly faster than pulling it off disk. Now, how much did those 1MB roms cost? ;-) -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com BIX: rjesup Common phrase heard at Amiga Devcon '89: "It's in there!"