ヘルプ日本語訳/The application properties
Last-modified: 2010-09-28 (火) 20:25:40
ヘルプ日本語訳 > The propaties > The application properties
The application properties
(原文)The application properties
The properties of the application are as follow :
This folder contains all the properties to build the application.
- Choose the graphic mode used by your application. 256 colors save a lot of memory, but restrain the number of colors displayed by the application.
- Build type
Indicates the type of application to build when you select Build application from the file menu. Can be a "Stand alone application" (a simple EXE file), a screen saver (a SCR file), or an internet application (to use either with the Vitalize! plugin or as a sub-application object in another application).
- Build filename
Enter the name of the file to build. If you do not enter anything, the name of the application is used and the required extension is added (SCR, EXE).
- Image filters
Indicates the image filters to include in the executable file of your application. If the Automatic option is selected in the Image Filters dialog box, then all the filters will be included if your application contains objects that display graphic files. In order to reduce the size of your stand-alone applications or screen savers, we recommend you to unselect the Automatic option and select only the filters you use.
- Sound filters
Indicates the sound filters to include in the executable file of your application. If the Automatic option is selected in the Sound Filters dialog box, then all the filters will be included if your application contains samples. No filter will be automatically included if your application plays only external sample files. In any case, we recommend you to unselect the Automatic option and select the filters you need, in order to optimize the size of your application and/or to include the needed filters.
- Install Settings
Opens the Install Settings dialog box and allows you to build an install program for your application and the external files it uses.
- Build Options
- Compression level
Choose between Normal and Maximum. Maximum might be a little slower to build.
- Compress sounds
Use this option to gain space in your built application. If this option is selected, the uncompressed WAV samples of your application will be compressed to ADPCM format, reducing their size by 2 or 4.
- Include external files
Includes in the built file all the external files referred to by the events or by any object. This option is very handy if you want to create one EXE file that contains everything. Upon runtime, the files are extracted to a temporary folder, and all the pathnames that refer to the files are relocated to the temporary folder. Note: this option doesn't include the files whose filename is calculated with an expression in the events.
- Compress the runtime
By default, the runtime is compressed and extracted to a temporary folder when the stand-alone application starts. This can cause problems with applications that access the Internet, especially if a firewall is installed on the machine. For such an application, unselect this option so that the runtime is not compressed and always keeps the same pathname when you run it. Note: uncompressing the runtime will add about 300 Kb to the size of the stand-alone application.
- Windows Vista Options
- Execution Level
This option allows you to select the privilege level of your application when it's executed on Windows Vista :
- None : in this mode, the application is executed by Vista in "compatibility" mode, i.e. when you create a file in system directories like the Program Files directory, Vista creates it in a directory in the current user's Application Data directory and displays it as if it was in the system directory.
This mode is used to keep compatibility with old applications that write to their install folder or to the HKEY_LOCAL_MACHINE\Software registry key. You should not use it in new applications designed for Windows Vista.
- As invoker (default) : in this mode, the application is executed with the privileges of the current user (or the calling application if the application is launched by another one). On Vista usually with normal privileges you are not allowed to write to system folders (Program Files, Windows, etc.) or to registry keys not located in the HKEY_CURRENT_USER folder. This mode is the prefered mode for Vista applications.
- As administrator : in this mode, Windows Vista will ask the user to confirm s/he wants to run your application, and if so will run it with elevated privileges, i.e. your application will be able to write to system folders and anywhere in the registry. This mode should be reserved to installers or applications that really need to access system folders. Note: you should sign your application with a certificat so that the confirmation screen displays this application was made by you and can be trusted.
Note: when you run your application from MMF2, it's always executed with the "As invoker" option. If you need to run your application in administrator mode from MMF2, then exit MMF2 and run it as administrator. The MMF2 runtime will be executed in administrator mode too.
- Run options
- Command line
Enter here the options you wish to pass to the application when you run it from the editor. You can use the standard Multimedia Fusion 2 Developer options like /NOF to prevent the application to switch to full screen, /DIB to force the application to use the standard graphic mode, etc. Of course these options won't be saved in the stand-alone applications, they are only used when you run your application from the editor.
- Enable Debugger Shortcuts
Allows you to enable the keyboard shortcuts of the debugger. Unselect this option if the debugger shortcuts conflict with yours.
- Show Debugger
Allows you to show or hide the debugger.
This folder contains the properties of the window in which the application is displayed.
Enter the size of the application window. You can choose between preset sizes or enter your own. Warning, do not confuse the size of the window with the size of the frame!
- Border color
Enter the color of the border drawn around the frame if the frame does not fill the window entirely.
Check this option and a title bar will be displayed on the top of the window.
- Heading when maximized
Check this option to maintain a title bar when the application window is maximized
- Disable close button
Check this option and the close button of the window will not work. Warning, your application must contain a way out!
- No minimize box
Check this option to disable the minimize box.
- No maximize box
Check this option to disable the maximize box.
- No thick frame
Check this option and the application window will be drawn with a thin line instead of a thick line. If this option is selected, the window won't be resizable.
- Maximized on boot-up
Check this option and the application will be maximized on boot-up.
- Hidden at start
Check this option and the application will be hidden on boot-up.
- Menu bar
Check this option to include a menu in the application. A click on the edit button opens the Menu editor.
- Menu displayed on boot-up
If this option is checked, the menu bar is displayed in the window when the application starts.
- Window menu index
Used when creating a MDI application. Indicates the index of the menu where the list of MDI child windows is inserted.
- Full screen
- Change resolution mode
When running the application, the resolution mode of the computer will change to match as best as possible the size of the window. For example, if your window is 640x480, the resolution mode will change to 640x480. Use this option to create full screen applications.
- Allow user to switch to/from full screen
If this option is selected, the menu of the application will contain an entry to allow the user to switch between full screen mode and windowed mode.
- Keep screen ratio
In full screen mode, the resolution mode of the computer will change to match as best as possible both the size of the window and the width/height ratio of the current screen. This option avoids your application window to get distorted on wide screens.
- Screen ratio tolerance
This option allows you to define a tolerance for the "Keep screen ratio" option. This tolerance is a percentage of the current screen ratio. It allows you to switch to a screen resolution close to the window size of the application even if its width/height ratio is not strictly identical to the current screen ratio.
: Suppose that the current resolution of the user's machine is 1440x900 (ratio = 1440/900 = 1.6), the window size of your application is 640x400 (ratio = 1.6) and the full screen resolutions available on the user's machines are :
As you can see, the only resolution with the same ratio is 1440x900. So if you want to execute your application in a screen resolution with the exact same ratio, you have no choice, your application will be played in a small 640x480 window in a big 1440x900 screen. If you set a tolerance of 8%, then any ratio between 1.47 and 1.72 will be considered as acceptable (between 8% below and above 1.6). So in this case, the 720x480 resolution will be chosen as it fits in the tolerance interval and is the smallest resolution greater than the window size of your application. The window of your application will be slightly distorted but this distortion is much less than if it was executed in 640x480 full screen mode.
- Resize display to fill window size
Will resize the content of the application window to match the window size. Basically, there will not be any borders. This option might slow down the display.
- ''Do not center frame area in window
If selected, the frame area will begin in the top/left of the window. If unselected, the frame area will be centered in the window.
- Multiple document interface (MDI)
Check this option to make a Multiple Document Interface application. A MDI application allows you to open several windows child of the main application. Practically, the first frame of your application is used to handle the background window and creates a new sub-application object with the "MDI Child Window" option each time it wants to create a new child window. An MDI application can also have docked toolbars, this is done with sub-applications with a Docked option.
Runtime options folder
This folder contains all the options to make the runtime work.
Enter the number of frames per second (FPS) of the runtime, basically the animation speed of the application when it runs. From 1 to 1000. The default setting is 50, 100 will double the speed of all the objects on screen, 1 will make a very slow application, etc.
Machine independent speed
Use this option to maintain the speed of the runtime on slower machines. This option makes the runtime skip the display of the frame when it is not running at the given frame rate. As display operations are usually the more time-consuming ones, this allows the application to keep its frame rate even on slower machines.
Run when minimized
As a default, the application is paused when minimized. Check this option and it will continue to run when minimized.
Run when resizing
Check this option and the application will not stop when you resize or move the window.
Do not stop screen saver when input event
As a default, a screen saver quits as soon as an input event (keyboard, mouse) occurs. With this option, it will not quit. It is up to you to test for input events in your application.
Do not share data if run as sub-application
Check this option if you want to prevent the parent application to access or modify the global values, global strings, scores or live numbers of your application when it is run as sub-application.
If this option is checked, up to 32 samples can be played at the same time. If not only one.
Play sound over frames
Check this option to continue playing a sound or a music from one frame to another. For example you might want to have a music playing while loading the next frame of your application.
Do not stop samples when application looses focus.
As a default, all the samples are stopped when the application looses the focus (when another application is activated). Check this option and the samples will continue playing.
The Standard display mode uses the default drivers to display the image. The Direct X mode uses Direct X to display the image and is usually slower than the standard graphic mode. The Direct X + VRAM mode uses the video RAM for the screen buffers. This mode is usually faster, especially with scrolling applications, but can be much slower if you use ink effects like semi-transparency in your application. Do not use ink effects or fade-like transitions in your application if it uses the DirectX+VRAM mode. Otherwise, use the Standard mode.
If selected, will synchronise the application with the display. Usually provides a smooth display. As the monitor refresh rate is usually between 6O fps and 90 fps, it's a good idea to set the frame rate of the application to 90 or 100 when you select this option.
Enable visual themes
Window XP only. Allows visual themes in the application.
Defines the initial score of all the players, when the game starts.
Initial # of lives
Defines the initial number of lives of all the players when the game starts.
Click on the edit button to define and edit the player controls of the game.
This property allows you to display a picture in a Vitalize! application when the Vitalize! plugin is downloading the application. Simply insert the pathname of a picture here, and the picture will be embedded at the beginning of the Internet application when you will build it.
Do not run from stand-alone applications
If this option is selected, stand-alone applications won't be able to load this CCN file. You must also select this option if you want to use the scripting features of Vitalize!. This option is ignored if you build the application as stand-alone application.
If this option is selected, you can use the following methods and properties of the Vitalize! plugin and ActiveX control :
This property allows you to get or set the URL of the CCN file loaded in the Vitalize! object. For example : Vitalize123.URL = "http://www.clickteam.com/xxx.ccn";
Pause / Resume / Stop
These methods allow you to pause, resume or stop the Vitalize! application loaded in the Vitalize! object. For example : Vitalize123.Pause();
This method allows you to retrieve the value of a global value as integer value. The index of the first global value is 0. For example : var n; n = Vitalize123.getIntValue(5);
This method allows you to set a global value to an integer value. The index of the first global value is 0. For example : Vitalize123.setIntValue(5, 1500);
This method allows you to retrieve the value of a global value as floating point value. The index of the first global value is 0. For example : var d; d = Vitalize123.getDoubleValue(5);
This method allows you to set a global value to a floating point value. The index of the first global value is 0. For example : Vitalize123.setDoubleValue(5, 1525.44);
This method allows you to retrieve the text of a global string. The index of the first global string is 0. For example : var text; text = Vitalize123.getStringValue(5);
This method allows you to modify a global string. The index of the first global string is 0. For example : Vitalize123.setStringValue(5, "Hello");
Note: scripting methods and properties don't work in some old browsers. All the recent browsers like Internet Explorer, Firefox, Opera 9, Netscape 9 support them.
Run only from (URL)
Allows you to define a list of URLs from which your CCN file can be executed. I.e. the CCN file must be on one of the servers in the list otherwise it won't run. For example : if the list contains http://www.yoursite.com, the file can be executed if it's in any sub-directory of http://www.yoursite.com. Note: you can also run the CCN file as local file on the machine where it has been built, but not on others. If this list is empty, then the CCN file can be executed from anywhere.
The values folder contains the default values of the global strings and global values. As a default, global values are equal to 0 and global strings are equal to "". With this property folder, you can change this and define default values for these items. You can also change the names of the values.
Click on New to define a new global value. Double click on the name of the value to edit its name : very handy to make your application clearer. Click on the number to change it. You can also right-click the name of the value and select Rename to rename it, or Delete to delete it. Note: you can delete only the last Global Value.
Click on New to define a new global string. Double click on the name of the string to edit its name : very handy to make your application clearer. Click on the edit zone to change the string. You can also right-click the name of the string and select Rename to rename it, or Delete to delete it. Note: you can delete only the last Global String.
The events folder contains only one property : the Global Events. Global events are a list of events that is global to the entire application.
Click on the button to open an event editor and edit the global events.
The About folder contains all the properties that define your application: name, information etc.
This property contains the name of your application. Note this name is not the filename, it is the internal name of the application.
Shows the icon of the application. Click on the Edit button to open the picture editor. You will notice that the icon is duplicated in different graphic formats : 48x48 pixels, 32x32 pixels and 16x16 pixels, in true colors, 256 colors and 16 colors. You must draw your icon in all the resolutions. Windows picks the better icon to display the application according to its needs. Note: only the 3 true color images can have an alpha channel. These images are displayed under Windows XP only. The 256 color images are displayed under the older versions of Windows when the desktop is in high or true color mode. The 16 color images are displayed when the desktop is in 16 or 256 colors.
Trick: if you want to reset the icon to the default images, press SHIFT+CONTROL when clicking the Edit button.
This property contains the filename of the application.
This line contains a pointer to the help file of your application. This help file will be displayed when the user presses Help.
Enter your name here.
Enter a copyright line here.
Enter a text to be displayed in the about-box of your application.
Enter a short description of your application.
Enter the name of your company (if it exists).
Enter the version number of this application.