|
QUICK ACCESS BASICS! COMPILING AND BUILDING STRANGE ERROR MESSAGES PROJECT MANAGER THE .Gateway PLUGIN PG DEBUGGING MEMORIES SLUGGISH COMPILED APPLICATIONS EDITOR BEHAVIOUR [return to FAQs page] [next FAQsheet] [previous FAQsheet]
Ultimo aggiornamento:
21 Gen 2000 |
FAQsheet #2 :: MOSTLY THE ENVIRONMENT BASICS! [Q]: OK, I've received my CD but when I double-click the FB^3 Editor I get an error message! What gives? [A]: You can't start FB^3 from the CD, you must copy it to a hard drive! COMPILING AND BUILDING [Q]: I have some old notes that tell me that FINDERINFO will only work if the "High-level event aware" flag (in SIZE resource #-1) is turned _off_... [A]: FB^3 sets the bits automatically. If you have a size resource in your res file that overrides what FB^3 writes as a default, then you will need to set the bits in it. [Q]: With FB II, the Project Manager was a list of the incls, period .. This made having skads of Include Files a real headache to maintain. With FB^3 having the folder for Groups .. A long list becomes only a few folders .. And with it a simplified way to sort & store Include Files. The demise of the 32K barrier allows a "Cross Use Of Code" that is limited only to a programmers skill & imagination. In FB^3, I do intend to consolidate the Include Files of my final Build, but, until then, with it going to be a couple hundred Include Files. Will I be seeing "True Running Speed" [A]: You missed the boat on this one. You can have a thousand includes and it's not going to slow down your program. Oh, maybe the compile will take an extra half second or so, but it's not going to affect the running speed of your program. FB links all of the pieces together into a single FCOD. [Q]: I made a black and white icon for my app but when compiled it appears with a standard FB^3 Icon... How come? [A]: Let me begin by explaining how an application is built. FB^3 starts building your application by making a copy of a runtime shell. (Path: FB Extensions/Compiler/Runtimes). Then it starts to add in resources that it encounters in the headers. The "RnTm FBII.Incl" file has two resource lines:RESOURCES "Rntm FBII.Rsrc","APPLFB3!"All of the resources related to the icons are in the file named "Finder BNDL.rsrc" which is in the headers folder. (Path: FB Extensions/Compiler/Headers) If you have another resource file in your project or if you include another resource file with a RESOURCES line, FB will add it to the project. If your added file contains the necessary ICON and BNDL resources, they will replace the default set from "Finder BNDL.rsrc". |
|||||||||
|
[ritorna all'inizio] |
STRANGE ERROR MESSAGES [Q]: [The Compiler] tells you that there is an Unresolved Error, and it has the "Click Me To Go To It" like the other errors and warnings. But, all that clicking does is get you that Damnable .. BEEP I know how to find it .. Copy the Error and paste it in the "Go & Find" dialogue window, and quick like a Boy Bunny Rabbit seeking Romance, there it is .. Meanwhile, Back At The Ranch: If Clicking the Btn that supposed to take you there, ain't gonna take you there .. Why is the btn there? [A]: Here's the catch: If the error is that a function def is unresolved, how can we go to the line where it's not? Staz Tech note: you normally get this type of "unresolved" message if you are using an FBII statement but not running in FBII runtime emulation. [Q]: I'm getting a false 'missing parens' error at times. It usually follows behind another error. When I fix the first error, then the missing end ')' error goes away too. [A]: When the compiler can't recognise your use of a parameter, it often loses its place on the line. That is how you can easily end up with two errors on one line with the second message being inaccurate. [Q]: What's this Errors file in my FB^3 folder? There weren't any in my project. I opened the file and it was empty! [A]: FB3 created an "Errors" file, even though there weren't any, in the same folder. The editor knows when to open the file and when not to. It also deletes it on exit. When you quit the editor, it clears it. It has been suggested that if there are no errors and it doesn't need to be opened that we kill it as soon as the Compiled program is created but there are some underlying issues that make that less than desirable. That's why we keep a list of files and dispose of them on exit. |
|||||||||
|
[ritorna all'inizio] |
PROJECT MANAGER [Q]: When I drag an item from the Project Manager to the Finder, it disappears and makes some unknown text clipping on the desktop. If I drag it back, the Project Manager doesn't accept it. Is this a bug? [A]: It's not a bug - although it isn't a really nice feature either. The message that you get explains that the clipping has expired. The clipping is just a reference to the original project object and the text of the dragged item. It doesn't usually survive a trip to the desktop. [Q]: If there is a project window behind a non-project editor window when the user selects "Run" there is different behaviour if the frontmost document was previously saved on disk or if it's an "untitled x" not already saved: - if the non-project file is saved then "Run" compiles the project - if the non-project file is not saved then "Run" compiles the non-project "untitled" If the user does any modification in source code of a previously saved file then selects "Run" the file is saved without asking. But if the document was not previously saved on disk (it's "untitled") then the file is not saved. If the "untitled" not saved is behind a project's window when the user selects "Run" then a DLOG appears and asks to save "untitled x". [A]: This is working as planned. When you run an untitled file, it is saved in the temp folder along with a temp project and is used to create a temp application. If you run a project or any file that is in a project, all of the open files are saved. The problem is that you also have an untitled file which may need to become part of the project, so the editor asks if you want to save it. Even if you cancel (because you don't want it to be part of the project) the compilation will continue. |
|||||||||
|
[ritorna all'inizio] |
THE .Gateway PLUGIN & NORTON 'ISSUES' [Q]: Norton says that there is a problem with the ".Gateway Plugin". [A]: Norton incorrectly flags names starting with "." as an error. However it is standard practice (Apple Technotes) for items that should not appear in a menu. You can safely ignore warnings. (Another problem with Norton is that it tries to reset the bundle bits on your project resource files. This is a nightmare when you are trying to get an icon to show up because it starts treating resource files as applications.) [Q]: What exactly does the plugin ".Gateway Plugin" do? [A]: It communicates with the compiler. |
|||||||||
|
[ritorna all'inizio] |
PG [Q]: If you add additional globals files to a project (say ones associated with .INCL that you might have) then any return to PG after that point removes the new Globals files. [A]: You can put your globals file in the group called "Your filters" and they will be preserved. You can alternatively add a "GLOBALS" line to the Project Include that manually adds the file. |
|||||||||
|
[ritorna all'inizio] |
DEBUGGING [Q]: How do I find out the values of variables when debugging with FB^3? [A]: There's a "Scripts" menu action you can insert that drops you into Macsbug showing the value of any given variable... [Q]: When I build a PPC application from the project it takes a very long time to launch the resultant app and when it does finally start the same 2 debugger windows are there (yes, the debugger was turned off in the project when I built it). [A]: I had this problem when I switched from FB 3.0.8 to FB 3.0.12. I solved it by trashing the preferences file (System folder:Preferences:STAZ:FB Editor Prefs). |
|||||||||
|
[ritorna all'inizio] |
MEMORIES [Q]: Probably a simple question, but I cannot get the Butterflame example to run on my StarMax 3000. I tried: Doubling the memory allocated to the editor (will time out) Adding 3000K to the app. heap in the compiler Re-saving in PG All of this produces an out of memory for Gworld error from the GRFX.filter. Trial compile works fine. [A]: Adding memory to the compiler or editor takes memory away from your compiled application. Memory not used by the editor and compiler is what is left for the application. |
|||||||||
|
[ritorna all'inizio] |
SLUGGISH COMPILED APPLICATIONS [nothing to do with FB^3!] [Q]: If anyone has a PowerBook and knows how to programmatically resolve this problem [...] I changed all the settings so that the computer is on maximum performance. Max performance includes screen never dimming, hard drive never spinning down and a few other 'nevers'. I let a program run and I got the same results. After a minute or two the program began to slow down. Printing to screen (Lite Runtime) came to an almost screeching halt until I moved the mouse. It's not a big deal now since I know that this is a known PowerBook issue, not related to any program. I'd just like a way to circumvent it. [A]: A POSTEVENT(0,0) will bring a sleepy cpu back up to full speed (and power drain). |
|||||||||
|
[ritorna all'inizio] |
EDITOR BEHAVIOUR [Q]: Totally by accident I just saw that when you uncheck the "Toolbox Require CALL" preference, Toolbox names become boldfaced. [...] I would have thought the Toolbox names would have been bold in either case and just the "CALL" would have been required. [A]: This works exactly as it should. It's why we made it a preference. Some people use toolbox procedure names as variables. That's why we went back and made this a preference so that they could get away with it even though it isn't terribly good.
[Q]: Has anyone noticed a disappearing underscore "_" character? [A]: Sounds like your font either doesn't have an underscore character or it lies below the base line + descent. Change the font used for constants and tell me what happens. [Q]: And what does the small option window (new or open) do differently than the file menu's new or open? It is rather confusing to have two places to choose open or new, implying they are somehow different. Even if you close the editor and begin again, the match FBII option seems still to be chosen (the little window still comes up), or does it always come up? How do you get rid of it. [A]: You get rid of it by selecting the appropriate checkbox in the prefs window. (Display Tab: Open selection window when all others are closed.) The selection window is something that we have used in commercial products for years. It keeps novices from closing a window and thinking that they have quit the application. [Q]: In the Preferences window, I can name my application. Intuitively, it seems to me that if a single file (non-project) is being built, the app should either get a name based on the name of the file (i.e. what is in the Preferences window), or I should be asked for a name. [A]: Technically speaking, the dialogue should say, "Building project named..." for projects or "Building file named..." for files. The editor will not be able to scan the code for the application name since any preference put in the compiler tab will be overridden by an OUTPUT FILE statement. That's why we don't use "Building application named...". [Q]: I am having trouble with the FIND/REPLACE command; it frequently tells me it cannot open one or more of the include files. [A]: Try resetting your aliases. Choose "Reset Search Paths" from the project menu. [Q]: The Editor keeps dropping me into MacsBug... particularly a place called "BowelsOfTheMemory"?! [A]: Probably a bug of MacsBug; 6.6f2c1 is garbage. It's _almost_ usable if you remove the "MacsBug preferences" folder files; 'Leaks dcmd - optional' 'PageFaults dcmd - optional' 'Startup Actions - optional' If any of these are present, you'll almost always wind up in the BowelsOfTheMemoryMgr. Hopefully, Apple will have another version out shortly. [Q]: I have a variable named 'rect'. Each time it appears in my file it is Capitalised and Highlighted... however the app compiles OK. Am I doing something wrong?[A]: Same here: I went through _some_ of my code (where this was bothering me) and changed the variable ' rect' to 'xrect'. However, that really isn't necessary; the compiler knows the difference between a variable and a keyword based on position - the editor can only go by its _name_ and is thus highlighting anything in its "list of keywords".Everything will work fine, it's just annoying to us humans. Change it if you wish, or leave it as is... [Q]: Use cmd-G to find again. Close this file. Open it again. Cmd-G. Editor beeps at you. Cmd-G. This time it finds the item. [A]: Standard HIG - once you've closed the file, you're no longer "finding again", you're finding for the first time. I like the fact that it lets you repeat the cmd-G and continue; most programs would just beep at you until you did cmd-F. |
|
© 2000 Pix&Mix
Tutti i diritti riservati |
||
|
FutureBASIC è un marchio registrato di Staz Software, Inc ed è usato previa autorizzazione. |
||