-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
how to create a trial program ?
- Thread starter gjoisa
- Start date
- Similar Threads Similar Threads
It is not an 100% secure way, but you can write a regestry key on first run, on some part of the regestry thet only you know, and that should have nothing to do with your program...containing the date of the first run...
Then, in the subsequent runs, check that same regestry key, anad compare withe the current date...
if the time span returned is bigger than you allow, then just close the app.
Then, in the subsequent runs, check that same regestry key, anad compare withe the current date...
if the time span returned is bigger than you allow, then just close the app.
Hi gjoisa,
There are several ways to do a trial version of your program.
You can for example disable some functions (for example Save). To do so, simply comment out the Sub that does this. Or even easier, remove (or hide) the buttons that command the actions.
You can also limit the use of the program to a certain duration (10 minutes, for example).
To do this, you can use the Tick count, and after a certain level, you simply close the application, with an explanation.
It depends of your application. You need the user to be able to use it, but not too much. Or too long.
There are several ways to do a trial version of your program.
You can for example disable some functions (for example Save). To do so, simply comment out the Sub that does this. Or even easier, remove (or hide) the buttons that command the actions.
You can also limit the use of the program to a certain duration (10 minutes, for example).
To do this, you can use the Tick count, and after a certain level, you simply close the application, with an explanation.
It depends of your application. You need the user to be able to use it, but not too much. Or too long.
A simple flow chart to do this would look like this...
On every RUN:
* Check if start date exists, if not then this IS the first run, so write the date to the regestry.
*If start date exist then compare with the current system date...
(To avoid the user to workaround this protection, by altering the system date, one could also write the number os times the program as been runned...)
* If the date diference is bigger than the number of days you specified, then terminate the program...
PS. I'm a bitt busy these days, but I am plannig on building a stand alone protection system, that should be easy to integrate in any app....
Let's just wait and see...
On every RUN:
* Check if start date exists, if not then this IS the first run, so write the date to the regestry.
*If start date exist then compare with the current system date...
(To avoid the user to workaround this protection, by altering the system date, one could also write the number os times the program as been runned...)
* If the date diference is bigger than the number of days you specified, then terminate the program...
PS. I'm a bitt busy these days, but I am plannig on building a stand alone protection system, that should be easy to integrate in any app....
Let's just wait and see...