home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!news.umbc.edu!comb1.comb.umd.edu!stern
- From: stern@comb1.comb.umd.edu (Brian Stern; COMB)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: I hate THINK Pascal...
- Date: 25 Jan 1993 14:13 EST
- Organization: University of Maryland, Center of Marine Biotechnology
- Lines: 28
- Distribution: world
- Message-ID: <25JAN199314131127@comb1.comb.umd.edu>
- References: <1993Jan24.005729.13045@fcom.cc.utah.edu>
- NNTP-Posting-Host: comb1.comb.umd.edu
- News-Software: VAX/VMS VNEWS 1.41
-
- In article <1993Jan24.005729.13045@fcom.cc.utah.edu>, Dmitry Boldyrev <dmitry@chemistry.chem.utah.edu> writes...
- >Hello,
- >I really hate THINK Pascal now!! :( Because, whatever I do,
- >all couse problems..
- >I'm working on Molecular Designer package and would like to write Floating
- >palettes. Problem with Events, partcicularly with App4Evt, made me CRAZY!!
- >If you have enought time, please take a look on this fragment of my code:
- >
- code deleted
-
- This is a bug in Think Pascal.
- In my experience Think Pascal NEVER passes suspend/resume events to an
- application running in the Think environment :-(
- However, if you build and SaveAs a double-clickable application, your compiled
- program will receive these events as you would expect them to :-)
- Obviously you can't use source level debugging for your suspend/resume
- processing, but it shouldn't be that difficult to debug that code anyway.
- As I'm writing this it occurs to me that Pascal might not trap the supend/resume
- events if you have debug off for the unit containing your event loop. However,
- if you are switching in or out of your program Pascal has to process these
- events also. It ought to pass them to your program but it doesn't.
- Hope this helps,
-
- BrianS
-
- Stern@mbimail.umd.edu
-
-
-