pgn@osupyr.mast.ohio-state.edu (Paul G. Nevai) (02/24/89)
I had an FKey made in LSP 1.11a and worked perfectly. It contains a shoutdown manager call. When I ported it to LSP 2.0 it still works in the project but when I compile it in the reduced library setting the shutdown call doesn't work anymore. WHY? Any help will be appreciated. ., Paul Nevai pgn@osupyr.mast.ohio-state.edu Department of Mathematics TS1171@ohstvma.BITNET The Ohio State University 73057,172.Compu$erve 231 West Eighteenth Avenue 1-(614)-292-5310.office Columbus, OH 43210, U.S.A. 1-(614)-292-4975.department
ra_robert@gsbacd.uchicago.edu (02/25/89)
In article <1232@osupyr.mast.ohio-state.edu>, pgn@osupyr.mast.ohio-state.edu (Paul G. Nevai) writes... >I had an FKey made in LSP 1.11a and worked perfectly. It contains >a shoutdown manager call. When I ported it to LSP 2.0 it still works >in the project but when I compile it in the reduced library setting >the shutdown call doesn't work anymore. WHY? I have a question along similar lines: what is going on differently when you run within the project and when you compile and run outside? Specifically, I've got a situation where I create a simple modeless dialog and then invalidate its portRect. This works fine in the project, but bombs on invalRect when I've compiled it and run it as an app. I compiled it in the project without the Debug option, and the assembly language right around the invalRect call seems the same both in the project and out. I checked what was going on both with Lightsbug in the Proj and with TMON outside and what's being passed to the call seems fine. I am at a bit of a loss. It must be an error somewhere else in my program, but I have no idea why it would cause an error (out of memory) on an InvalRect call. The dialog ptr seems valid, and if I take out the InvalRect call the program compiles and runs fine. What's getting me is: why does it run fine with this call _in_ the project, and crash outside? Robert ------ ra_robert@gsbacd.uchicago.edu ------ generic disclaimer: all my opinions are mine
siegel@endor.harvard.edu (Rich Siegel) (02/25/89)
In article <2001@tank.uchicago.edu> ra_robert@gsbacd.uchicago.edu writes: >In article <1232@osupyr.mast.ohio-state.edu>, pgn@osupyr.mast.ohio-state.edu (Paul G. Nevai) writes... > >I have a question along similar lines: what is going on differently when >you run within the project and when you compile and run outside? Specifically When you run inside the environment, Lightspeed Pascal initializes thePort to point at the Drawing window IF YOU DO NOT CALL InitGraf. If you don't do proper SetPort calls to set up your windows' grafPorts (a good time to do this is on an activate event), things can and wil go wrong. --Rich Rich Siegel Staff Software Developer THINK Technologies Division, Symantec Corp. Internet: siegel@endor.harvard.edu UUCP: ..harvard!endor!siegel Phone: (617) 275-4800 x305
ra_robert@gsbacd.uchicago.edu (02/25/89)
In article <2001@tank.uchicago.edu>, ra_robert@gsbacd.uchicago.edu writes... >I have a question along similar lines: what is going on differently when >you run within the project and when you compile and run outside? [description of problem] Well, one thing running in the environment does is not let you bomb when you try to inval the WMgrPort^.portRect. Yup, that was the prob: a simple missing SetPort. Oops: sorry for any wasted bandwidth. Still, it's interesting to note that difference between running in and out of the environment. Robert ------ ra_robert@gsbacd.uchicago.edu ------ generic disclaimer: all my opinions are mine
alexis@ccnysci.UUCP (Alexis Rosen) (02/26/89)
Paul Nevai asks about the Shutdown manager in LSP. 2.0. I have used it and discovered that something truly strange goes on. I don't know if his problem is the same as mine was, but if so there are two possible solutions: 1) Run on the Mac II 2) or, just explicitly initialize all of the managers (up to the dialog mgr, at least). It seems, for some obscure reason, that the Shutdown mgr wants them all in place... Alexis Rosen alexis@ccnysci.uucp