mike@ames.arc.nasa.gov (Mike Smithwick) (08/20/89)
["I was born an orphan. . ."]
Ok, so I'm running dpaint, see, and I have this morerows thing runnin'
as well. So I want to create a picture thingy, and discover that Dee-Paint
automagically takes into account the extra rows, so my picture will be
320x230, instead of 320x200 as I would like. "So" sez me, "lets just change
the page size". I open up the Set Page Size requester, and type in the
smaller height of 200 in place of 230. I then close that suckah' but
nothing happens. I open it up again, and the Height is back to 230
again. This seems to affect all of my pictures. I bring in the startup
screen for Galileo done under DPaint II, touch it up "shrink" the height,
and save it out. But it is still saved as a 230 pixel high picture really
screwing up my program. Is this a bug in the Set Page Size stuff??
Signed,
confused in California
*** mike (still looking for a publisher) smithwick ***
"Los Angeles : Where neon goes to die"
[disclaimer : nope, I don't work for NASA, I take full blame for my ideas]amichel@neabbs.UUCP (MICHEL LANGEREIS) (08/22/89)
mike@ames.arc.nasa.gov (Mike Smithwick) writes : >["I was born an orphan. . ."] .... >Ok, so I'm running dpaint, see, and I have this morerows thing runnin' >as well. So I want to create a picture thingy, and discover that Dee-Paint >automagically takes into account the extra rows, so my picture will be >320x230, instead of 320x200 as I would like. "So" sez me, "lets just change >the page size". I open up the Set Page Size requester, and type in the >smaller height of 200 in place of 230. I then close that suckah' but > [ ... ] There aint no bug buddy, morerows and many others change the x-y offsets in the devs:system-configuration file and guess where DP3 (or PixMate for that matter) is looking for the screen sizes ? Right, in system-config. I had this a while ago, DP3 wouldn't play anims created on my machine at a friends place, I also had trouble playing a MovieSetter anim on the other Amiga's besides my own. Now what was the trouble, in DP3 I created a demo animation with a picture size of 672*274 (my 'normal' screen), the other machines around where 640*256 (PAL ?) so that wouldn't fit. With PixMate I changed a HAM picture to lo-res so MovieSetter would accept it as backgound for my wizz-bang animation, PixMate thought, he lets take current screen size (672*274) and MovieSetter said, fine go ahead. Playback both the anims on other Amiga's was out of the question, no way unless we put the system-configuration in devs: No bugs, just a little tradeoff for 'auto PAL/NTSC' detection I guess. Michel (RoachaToyllah) Langereis. hp4nl!neabbs!amichel@uunet.uu.net | Just speaking for myself. send a salami to your boy in the army
lphillips@lpami.wimsey.bc.ca (Larry Phillips) (08/23/89)
In <197178@neabbs.UUCP>, amichel@neabbs.UUCP (MICHEL LANGEREIS) writes: >mike@ames.arc.nasa.gov (Mike Smithwick) writes : >> [ comments about DPaint bugginess ] >There aint no bug buddy, morerows and many others change the x-y offsets >in the devs:system-configuration file and guess where DP3 (or PixMate >for that matter) is looking for the screen sizes ? Right, in system-config. If it allows you to put in a size specification in the 'Page Size' requester without complaint, and then proceeds to arbitrarily change it back to whatever it feels like, I call that a bug. If I want to make a picture that will show as 320*200, the bloody program should do it, or they should rip the 'Page Size' menu out of there and stop pretending to support different sizes. EA really ticks me off with this turkey. It allows you to use overscan, but that way invites trashed menus and screens and visits from the GURU. The so-called file requester is a hideous joke. The anim brushes do not work as the manual says they should. The 'Project' menu will not even show up (except for subitems) if I select 320*200, 32 colour. Using the font requester pukes debug information all over my CLI. This is the third version of DPaint. I could forgive the first one its foibles when the Amiga was young. I could forgive the second one because they really did make a lot of improvements; real improvements, not just a few flashy feature additions. I cannot forgive the third one. Maybe in DPaint 4? Naw.... "Throw another coat of paint on it and get it out the door." -larry -- begin 777 .signature M268@>6]U(&1O;B=T('-E92!T:&ES('-E;G1E;F-E+"!Y;W4@<VAO=6QD('-EB 2;&P@>6]U<B!C;VUP=71E<BX*. `` end +-----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 -or- 76703.4322@compuserve.com | +-----------------------------------------------------------------------+
lphillips@lpami.wimsey.bc.ca (Larry Phillips) (08/25/89)
In <539@tardis.Tymnet.COM>, jms@tardis.Tymnet.COM (Joe Smith) writes: >In article <710@lpami.wimsey.bc.ca> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: >>The anim brushes do not work as the manual says they should. > >Maybe I haven't used anim brushes enough to find the problem. What problems >are you having? Following the tutorial in tha manual doesn't work. As it turns out, you have to use the keyboard equivalent or somesuch rather than the mouse buttons. I didn't pay much attention. I can't be bothered learning the quirks of a buggy third generation product. >>The 'Project' menu >>will not even show up (except for subitems) if I select 320*200, 32 colour. > >I don't understand what you're talking about here. Unless you're referring >to fact that Dpaint handles out-of-memory gracefully (it simply does not >show some menus or brushes as opposed to crashing.) What does it say when >you select "About.." from the "Picture" menu? I am referring to when the 'Project' menu does not show up at all when selected. It is there, since I can move the mouse down and various subitems pop up where they would be when it's working right. It does not always do this, but when it does, it's irritating (to put it kindly). >>Using the font requester pukes debug information all over my CLI. >>begin 777 .signature >>M268@>6]U(&1O;B=T('-E92!T:&ES('-E;G1E;F-E+"!Y;W4@<VAO=6QD('-EB >>2;&P@>6]U<B!C;VUP=71E<BX*. > >But I don't want to sell my computer. :-) -larry -- The Mac? Oh, that's just like a computer, only slower. +-----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 -or- 76703.4322@compuserve.com | +-----------------------------------------------------------------------+
jms@tardis.Tymnet.COM (Joe Smith) (08/25/89)
In article <710@lpami.wimsey.bc.ca> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: >The anim brushes do not work as the manual says they should. Maybe I haven't used anim brushes enough to find the problem. What problems are you having? >The 'Project' menu >will not even show up (except for subitems) if I select 320*200, 32 colour. I don't understand what you're talking about here. Unless you're referring to fact that Dpaint handles out-of-memory gracefully (it simply does not show some menus or brushes as opposed to crashing.) What does it say when you select "About.." from the "Picture" menu? >Using the font requester pukes debug information all over my CLI. >begin 777 .signature >M268@>6]U(&1O;B=T('-E92!T:&ES('-E;G1E;F-E+"!Y;W4@<VAO=6QD('-EB >2;&P@>6]U<B!C;VUP=71E<BX*. But I don't want to sell my computer. -- Joe Smith (408)922-6220 | SMTP: JMS@F74.TYMNET.COM or jms@tymix.tymnet.com McDonnell Douglas FSCO | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms PO Box 49019, MS-D21 | PDP-10 support: My car's license plate is "POPJ P," San Jose, CA 95161-9019 | narrator.device: "I didn't say that, my Amiga did!"
lphillips@lpami.wimsey.bc.ca (Larry Phillips) (08/27/89)
In <542@tardis.Tymnet.COM>, jms@tardis.Tymnet.COM (Joe Smith) writes: >In article <714@lpami.wimsey.bc.ca< lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: ><I am referring to when the 'Project' menu does not show up at all when ><selected. It is there, since I can move the mouse down and various subitems pop ><up where they would be when it's working right. It does not always do this, ><but when it does, it's irritating (to put it kindly). > >What is this 'Project' menu you are referring to? My copy of Dpaint has >only 'Picture', 'Brush', 'Mode', 'Anim', 'Effects', and 'Prefs'. >Is there a pattern to its failure? Such as spare page in use, giant brush >selected, etc? Sorry, I didn't go back and look at the menu itself while posting. It is the 'Picture' menu, in the position that CBM recommends be called 'Project'. There is no apparent pattern to the failure. I can boot it up, selecting 320*200, 32 colour, and have the menu not show when selected. As I say, it is there, since I can see the subitems when the mouse is pulled down in the area where the menu should be. -larry -- The Mac? Oh, that's just like a computer, only slower. +-----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 -or- 76703.4322@compuserve.com | +-----------------------------------------------------------------------+
jms@tardis.Tymnet.COM (Joe Smith) (08/27/89)
In article <714@lpami.wimsey.bc.ca< lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes:
<I am referring to when the 'Project' menu does not show up at all when
<selected. It is there, since I can move the mouse down and various subitems pop
<up where they would be when it's working right. It does not always do this,
<but when it does, it's irritating (to put it kindly).
What is this 'Project' menu you are referring to? My copy of Dpaint has
only 'Picture', 'Brush', 'Mode', 'Anim', 'Effects', and 'Prefs'.
Is there a pattern to its failure? Such as spare page in use, giant brush
selected, etc?
--
Joe Smith (408)922-6220 | SMTP: JMS@F74.TYMNET.COM or jms@tymix.tymnet.com
McDonnell Douglas FSCO | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms
PO Box 49019, MS-D21 | PDP-10 support: My car's license plate is "POPJ P,"
San Jose, CA 95161-9019 | narrator.device: "I didn't say that, my Amiga did!"lphillips@lpami.wimsey.bc.ca (Larry Phillips) (08/30/89)
In <19351@unix.cis.pittsburgh.edu>, ejkst@unix.cis.pittsburgh.edu (Eric J. Kennedy) writes: >In article <714@lpami.wimsey.bc.ca> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: >>>>The 'Project' menu >>>>will not even show up (except for subitems) if I select 320*200, 32 colour. > >>I am referring to when the 'Project' menu does not show up at all when >>selected. It is there, since I can move the mouse down and various subitems pop >>up where they would be when it's working right. It does not always do this, >>but when it does, it's irritating (to put it kindly). > >Wait a minute, that has nothing to do with Dpaint. I've seen this >behavior in lots of programs, always when there's insufficient chip ram >to render the menu. It's probably just Intuition's way of handling low >memory situations. (If there's not enough chip ram to render the menu, >there sure isn't enough to put up a warning requester!) Closing or >shrinking some windows usually cures this problem for me. But I don't >have Dpaint III. Maybe the problem is that it's too much of a chip ram >hog... Could be. In all my years on the AMiga, this is the first time I've seen anything at all like it. -larry -- The Mac? Oh, that's just like a computer, only slower. +-----------------------------------------------------------------------+ | // Larry Phillips | | \X/ lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips | | COMPUSERVE: 76703,4322 -or- 76703.4322@compuserve.com | +-----------------------------------------------------------------------+
ejkst@unix.cis.pittsburgh.edu (Eric J. Kennedy) (08/30/89)
In article <714@lpami.wimsey.bc.ca> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: >>>The 'Project' menu >>>will not even show up (except for subitems) if I select 320*200, 32 colour. >I am referring to when the 'Project' menu does not show up at all when >selected. It is there, since I can move the mouse down and various subitems pop >up where they would be when it's working right. It does not always do this, >but when it does, it's irritating (to put it kindly). Wait a minute, that has nothing to do with Dpaint. I've seen this behavior in lots of programs, always when there's insufficient chip ram to render the menu. It's probably just Intuition's way of handling low memory situations. (If there's not enough chip ram to render the menu, there sure isn't enough to put up a warning requester!) Closing or shrinking some windows usually cures this problem for me. But I don't have Dpaint III. Maybe the problem is that it's too much of a chip ram hog... -- Eric Kennedy ejkst@cisunx.UUCP
shf@well.UUCP (Stuart H. Ferguson) (08/31/89)
+-- lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: | Sorry, I didn't go back and look at the menu itself while posting. It is the | 'Picture' menu, in the position that CBM recommends be called 'Project'. Tsk, tsk. | There is no apparent pattern to the failure. I can boot it up, selecting | 320*200, 32 colour, and have the menu not show when selected. As I say, it is | there, since I can see the subitems when the mouse is pulled down in the area | where the menu should be. Ha! I've seen this! It happened to me a few times when I was developing Intuition applications. There was no apparent pattern, no way to repeat it and no way to be really sure it was gone. It just sort of went away "by itself" and didn't seem to come back. I would bet there is an Intuition scenario that can reproduce this. It may not be a bug since the application may need to be doing something funny as well. Anyone have *any* idea what this is? -- Stuart Ferguson (shf@well.UUCP) Action by HAVOC (ferguson@metaphor.com)
andy@cbmvax.UUCP (Andy Finkel) (08/31/89)
In article <13418@well.UUCP> shf@well.UUCP (Stuart H. Ferguson) writes: >+-- lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: >| There is no apparent pattern to the failure. I can boot it up, selecting >| 320*200, 32 colour, and have the menu not show when selected. As I say, it is >| there, since I can see the subitems when the mouse is pulled down in the area >| where the menu should be. > >I would bet there is an Intuition scenario that can reproduce this. It may >not be a bug since the application may need to be doing something funny as >well. Anyone have *any* idea what this is? The last time I saw this was under very low chip memory conditions. Intuition was not able to get the memory it needed to display the entire menu; but did have enough chip memory available to display the (smaller) sub-menu. andy -- andy finkel {uunet|rutgers|amiga}!cbmvax!andy Commodore-Amiga, Inc. Life gets pretty complex the minute you stop mooing. Any expressed opinions are mine; but feel free to share. I disclaim all responsibilities, all shapes, all sizes, all colors.
kevin@uts.amdahl.com (Kevin Clague) (09/02/89)
In article <13418@well.UUCP> shf@well.UUCP (Stuart H. Ferguson) writes: >+-- lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: >| Sorry, I didn't go back and look at the menu itself while posting. It is the >| 'Picture' menu, in the position that CBM recommends be called 'Project'. > >Tsk, tsk. > >| There is no apparent pattern to the failure. I can boot it up, selecting >| 320*200, 32 colour, and have the menu not show when selected. As I say, it is >| there, since I can see the subitems when the mouse is pulled down in the area >| where the menu should be. > >Ha! I've seen this! It happened to me a few times when I was developing >Intuition applications. There was no apparent pattern, no way to repeat >it and no way to be really sure it was gone. It just sort of went away >"by itself" and didn't seem to come back. > >I would bet there is an Intuition scenario that can reproduce this. It may >not be a bug since the application may need to be doing something funny as >well. Anyone have *any* idea what this is? >-- > Stuart Ferguson (shf@well.UUCP) > Action by HAVOC (ferguson@metaphor.com) It's always dangerous following up when your 188 articles behind but... I've had this happen when I'm low on chip RAM. Kevin -- UUCP: kevin@uts.amdahl.com or: {sun,decwrl,hplabs,pyramid,seismo,oliveb}!amdahl!kevin DDD: 408-737-5481 USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086 [ Any thoughts or opinions which may or may not have been expressed ] [ herein are my own. They are not necessarily those of my employer. ]
rtczegledi@crocus.waterloo.edu (Richard Czegledi) (09/03/89)
I think I found a real bug with dpaint III. It lies in the palette requester. To demonstrate it, set your palette colour to white, and then take the 'v' slider down two knotchs. Position your cursor above one of the knobs in the RGB gadget thing. Move your cursor so that if you click, the knob will move just one step. Click. Notice it moved two steps? When it gets near the top, it doesn't move just one step. --- Also, digipaint III seems to crash about once every two days for me. So far, it has always happened either when I start the program up, or when I exit. Typicaly, it's a guru 4.008042A8. Booting right to the disk. Once it crashed, it killed my clock (spirit board), and when I booted, somehow the machine decided to spit a whole bunch-o letter 'P's in the first console window before any of the normal text came up. Pretty crash. Even the modem lights went christmas. While I'm here, I'm going to tell everybody what digipaint III lacks and needs: (attn. newtek): When you open the workbench again, it pops to the front for a billisecond, and then leaves. If I open the workbench, don't you think it means I WANT to use the workbench? Keep it to the front. The 'clear' option and the keyboard equivilent don't do the same thing. shift K usualy clears either to black, or to white (can't seem to figure out when), and clear usualy clears to some other colour completely. I can shift K, and then clear (from the menu), and the screen will go through 2 diferent colour schemes. I think it was stupid to get rid of the add and subtract modes. They were very handy, and it royaly pee'd me off. Where's the fill? No colorfonts? Oh come on! Also, it needs a HSV palette, a sprite to give co-ordinates on screen, and about 64 to 128 'cans' where you can keep good paint colours. Like what photon paint does. Very handy. A grid would be nice. Very nice and special. Modes like 'OR' should work with texture mapping. I can think of no reason why they shouldn't be allowed to work together. Why can't I rotate my brush? Huh? It's stupid that I have to texturemap, and then rotate in 90 degree increments. Also, texture mapping is sort of dumb, (the way you implement it). it bothers me that you have to put the brush in that swap thing. Sometimes the 'no-background' option doesn't seem to work. The smoothening options suck. They really suck. They are slow, and hardly ever give decent results. Take some time and do it sort of the way delxe photolab does. It pains my brain that I can't use so many options with the actual brush (the data in the brush, not the colour). A low/high option (sort of like in photolab) for the hotspot on the transparency thing. I read the bit about twisting the colour range by the hot-spot vertical bar thing. But it doesn't sort of work with the point source. It would be useful to be able to set the 'twang' factor, so you could instantly switch the range for colour ranges. Support real anti-aliasing. It looks terrible when I expand a brush, and it does it's 'pretend' smoothening nonesense. I have blurred chunks. Is that useful? Is that professional? Please come out with an update with these features/fixes/updates and you'll have a serious winner. OH! Also, please keep separate pathnames for separate file requesters. I hate it when I save a file, and I get my fonts directory. A free memory requester would be handy too. Also, it's not too hard to keep track of how long a text line is going to be. How about having it not accept input after the line would get too long? I'm a pretty pleased customer of yours. I have your digitizer, digipaint 1 , and will probably pick up your toaster when you get it out. Just my opinions. Hope something gets done.
ejkst@unix.cis.pitt.edu (Eric J. Kennedy) (09/06/89)
In article <16235@watdragon.waterloo.edu> rtczegledi@crocus.waterloo.edu (Richard Czegledi) writes:
<I think I found a real bug with dpaint III. It lies in the palette
<requester. To demonstrate it, set your palette colour to white, and
<then take the 'v' slider down two knotchs. Position your cursor above one
<of the knobs in the RGB gadget thing. Move your cursor so that if you click,
<the knob will move just one step. Click. Notice it moved two steps?
Wow, dpaint II does that, too.
--
Eric Kennedy
ejkst@cis.unix.pitt.eduswan@jolnet.ORPK.IL.US (Joel Swan) (09/06/89)
Here's another "gotcha" with DPaintIII. Turn off the tool box and title bar with F10. Draw something on the screen. Bring back the tool box with F10. Now, have fun trying to make undo work. It doesn't undo anything you draw while the tool box is hidden. A real pain. I hope someone at EA realizes that DPAINT deserves better file requesters than it has. I've even tried assigning their "default" drawer names to directories. No go. Their defaults are not devices, but just drawer names. I finally NewZapped DPAINT and changed all the defaults to device names (ie. "lo-res" to "lo-rs:", "brush" to "brsh:") but still no go. You have to click in the drawer gadget and hit return. What a brain dead user interface to the file system. I think Dan ought to get some help in this area to help polish up Dpaint. I know it would cut down on a lot of aggrivation. -- - Joel E. Swan [ swan@jolnet.UUCP <> PLINK ID: Amiga*joel ] [ "Amigas.... for the rest of us." <> CI$ : 74746,3240 ] [ "...peace with God through our Lord Jesus Christ." Romans 5:8 ]
lindam@sactoh0.UUCP (Linda C. Marquess) (09/09/89)
In article <1500@jolnet.ORPK.IL.US>, swan@jolnet.ORPK.IL.US (Joel Swan) writes: > Here's another "gotcha" with DPaintIII. [ stuff deleted] > > Bring back the tool box with F10. The keyboard equivilent (CTRL-U) still works fine with the menu bar off. It only seems natural to use the keyboard when you have the menu turned off, so I don't see it as a problem. I find DPaint III file requesters greatly improved. There are no more "default" directories. I suppose there is always room for improvements, but I am very happy with the new additions.