Much of the functionality of the 16-bit version is retained, but due to an entirely new concept of creating and handling of windows and dialog boxes, GFA-BASIC 32 is also quite different and much more compatible to VB in that area. The command library of GFA-BASIC 32 is partly compatible to Visual Basic and 16-bit GFA-BASIC. The compiler is optimized for producing fast machine code, so that GFA-BASIC 32 programs execute at high speed. When run from the IDE the code is first compiled to machine code and then executed. GFA-BASIC 32 is no longer divided in an interpreter and a stand-alone compiler. Then GFA-BASIC was developed for for the Intel processors: GFA-BASIC for MSDOS, GFA-BASIC for Windows 3.1, and the most recent GFA-BASIC 32 for Windows 95 and later. The first version was released in 1985 for the Atari ST, followed by a version for the Amiga. There are some other keys that may be of intrest to you, like the CFBundleGetInfoString one, which allows to set a string that can be seen when the user selects "Get Info" for your. Values can be "Editor", "Viewer", "Shell" or "None".Īll available keys for the ist are explained in detail here: Specify what your application does with the type. Set a name to describe your file type here. The icon must be copied to the Contents/Resources folder of the. Here you can set an icon file for these file extensions. To make this setting apply for all types (for example if you want any file to be droppable to your app icon), use a "*". The is needed, even if there is only on extension. Here is a short description of the fields: You need to specify atleast the CFBundleTypeExtensions and CFBundleTypeRole parts, the rest is optional You can also have multiple versions of the entre part, to associate different extensions with different icons for example As you can see you can have multiple extensions in the CFBundleTypeExtensions array This is what we add to the ist for the IDE (it goes into the main tag) (happened to me with setting an icon for the files) In some cases only a restart will make the changes take effect. app to a different folder for finder to notice the changes. Especially if you previously executed the program with different settings. Note2: The changes you make to the file may not immediately be seen by the finder. (mainly the CFBundleExecutable and CFBundleIconFile keys) Keep in mind that if you make some changes in the compiler options, you have to apply the resulting changes in the generated file also to your saved copy. (You can also automate this by creating a small tool that is run after the executable is created) Note: The compiler overwrites this file on every compilation, so better save your modifications elsewhere and copy the file back after every new compilation. Open the ist file in the Contents folder as described below. Open the context-menu and select "Show package contents" (this will display the contents of the. To tell finder about your file types, edit the "ist" in your bundle directory. That is because you need to tell finder what types of files you accept. If you run this, you will notice that you cannot drag any files to the application. Until WaitWindowEvent() = #PB_Event_CloseWindow If AEInstallEventHandler_(#CoreEventClass, #AEOpenDocuments, 0, 0) #NoErrĪddGadgetItem(0, -1, "cannot install event handler!") Call this before processing the first window events, else you may miss the open event! Next OpenWindow(0, 0, 0, 600, 300, "Open Document test", #PB_Window_ScreenCentered|#PB_Window_SystemMenu) If you want to accepte directories too, then change this If i, #typeFSRef, SizeOf(FSRef), = #noErr If AEGetParamDesc_(*appleEvt, #keyDirectObject, #typeAEList, = #noErr If AECreateDesc_(#typeNull, 0, 0, = #noErr ProcedureCDLL OpenDocument(*appleEvt, *reply, refcon) the correct callback behavior (therefore the DLL part) ProcedureCDLL is important, for the right calling convention (on x86) and
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |