jpd00964@uxa.cso.uiuc.edu (08/17/89)
/* Written 12:37 am Aug 16, 1989 by mark@apple3.cis.ohio-state.edu in uxa.cso.uiuc.edu:comp.sys.next */ /* ---------- "help requested with finishing touch" ---------- */ >1) I am using the bitmap method composite:toPoint: and trying to seqeuence > thru a series of bitmaps onto a window but I am getting blocking > of those composites into very fast sequences of images that then > hesitate. I would prefer, a smoother animation and am aware of the > animation timer method found in the example BreakApp. Will that > method smooth it out. Am I using the wrong flushing mechanism > to composite the bitmaps to screen? What would be the proper one? It sounds like the problem has to be with sharing processes in unix. That means that your program gets a bunch of process time, then it gets none, then it gets a bunch, etc. The proper way to do this is with the animation timer as shown in BreakApp. These are postscript calls, so they are described more in the display postscript section of the manuals. > 2) I draw to both window directly and to bitmap, yet when I composite from > bitmap to window the y axis is reversed running from the upper > left corner rather then the lower left corner, yet I draw with the > same code. Thats curious. Less curious but still to fix is that > the text letters printed using postscript are also reversed and > look correct only in the upsidedown bitmap. I assume that in some > way I should be flipping the axis but where? That's because they are supposed to be. In each view, there is a flipped variable. That is set by setFlip. You MUST set the flip for each subclass. This is all described in the dox under drawing. Basically, text is flipped because that way successive lines are incremented. Think about it. >4) My application has three windows. One of which I want to resize upon > initialization. I have an init() function I call from either a > button press or from my application method new+. Yet their behavior > is very different. When done from new, nothing seems to happen. > What am I doing wrong here? I'm not sure from your description, but a guess would be that you have not actually assigned the window yet. Do you have an outlet with the IB? If so, which I suspect, then you should call init in your setWindow:anObject message. that's what its for, after all. > 5) When I was using Interface Builder I found that I needed more or less > outlets and action/target routines after my initial creation of > the project file. I realize that the dreaded UNPARSE button can > only be pressed once but it would seem that there should be ways > to add more outlets and action/targets within IB. Is there? > If not, I assume correct programming practice would be to make a > messa outlets and target methods and save em for a rainy day. You should play around a bit more. This one was easy. The PARSE button does everything you want. You just add in the outlets and actios exactly like they appear if you had UNPARSED and hit parse. >mark@cis.ohio-state.edu /* End of text from uxa.cso.uiuc.edu:comp.sys.next */ Michael Rutman Softmed jpd00964@uxa.cso.uiuc.edu