The expiry options allow you to place limits on how long users will be able to use your applications.
1. Enable this option if you want your application to expire a specific number of days after the application is run by your customer for the first time. Note: The expiration timer starts from when the application is first run, not from when it is built.
2. The number of days (after the first run) before the application expires. You can select any value from 0 up to 999 days. If you select 0 days, the application will expire the first time it is run. This is only a desirable option when combined with the On Expiry setting below.
3. Enable this option to choose an absolute expiry date for your application by choosing the month, day and year. You won't be allowed to select an invalid combination such as the 31st of February, SWF Studio will automatically correct dates to avoid this. SWF Studio will also generate a warning in the build results if you select a date that is not a future date.
4. Select the expiry month. If you select a month that has less than the displayed number of days, the expiry day will automatically be adjusted down to the maximum number of days for the selected month.
5. Select the expiry day from 1 to the maximum number of days for the selected month and year.
6. Select the expiry year
7. Normally, every time your application runs the current date and time should be higher than on the last run. If you enable this option, SWF Studio will enforce aggressive back-clocking detection to help precent date tampering in your applictions. If SWF Studio determines that the date has been tampered with, the application will report that it has expired.
Note: If you are using the expiry options it is important that the time and date on your computer are set correctly. If the time and date are not set correctly your application may expire at the wrong time on your customers computer. Setting your time and date correctly ensures the expiry options in SWF Studio can be enforced on your customers computers to protect your work.
8. Supply a path to the SWF file you want to be displayed when your application is expired. You can supply an absolute path or a relative path to the SWF File.
Note: The SWF you specify as the expiry SWF will always be launched in hidden mode. This gives you the chance to determine whether to let the application continue running or to display the expiry SWF. If you want to let the application continue to run then you should call ssCore.Security.loadMainMovie and SWF Studio will load the main movie you specified on the Movie Tab. If you want the expiry movie to appear then all you have to do is call Win.show. Even after you show the expiry movie you can call ssCore.Security.loadMainMovie to let the application run.
You can use the Security commands in your security SWF to determine whether or not your application should be expired, change the criteria that are used to make that determination, or simply override the settings. The combination of the expiry SWF and the Security commands allow you to create a custom expiration system that can be as simple or as complicated as you like. You can even connect to a server to create an online activation system using the server to determine when the application should expire.
If you don't supply an SWF to be displayed on expiry then when your application expires your users will see the default expiration message below.
9. Opens a standard Windows File Open dialog that allows you to select an SWF file. If the expiry SWF field is already populated, that value will be used to initialize the start directory for the File Open dialog, otherwise the system default folder will be used.