Calculus v3.3.1 with zooming of graphs

I have updated Calculus to version 3.3.1. Now the graphs can be zoomed in.

The zooming isn’t very useful if one doesn’t have “Make y limits equal to x limits” on, what is now by default turned on.

I will try to find time to make the app still better..

New Year 2019

The year has started quite slowly for me.. Or has it? I’m again a full time student. That really slices quite a lot of hours of my day. At least I try to find time for my Android app Calculus. Some other projects are also in my mind.

Last summer I started coding a “space game” (I called it Androrace), but I lost my interest in it. Video below:

Calculus v3.2.0 to Android

I’ve been on fever for several days now, when I’m writing this. Nevertheless, now Calculus is at version 3.2.0 beta. Finally saving to Pictures folder work properly — also in later (>=6) Android versions.

One new feature is also possibility to make y limits equal to x limits With this button one can get results like this:

Graph saved in Calculus

The video below is recorder directly from my phones screen:

Let’s see if I manage to implement some new features to Calculus in near future.

Three tunes that were left out from Memorable Melodies

When I made the short old school synth tunes for Memorable Melodies, I made them all in one night.

There are three tunes I left out from the game. I guess these were just experimental tunes to set me in the “composing” mood. I made today a YouTube video from those three tunes:

Try the free game to get a impression, how the tunes turned out to be, that were included in the game. Remember, there is a cheat in the game: By tapping top right corner of the screen during game play, all the mistakes are cleared.

The latest version of Memorable Melodies is 1.4.

As you can see from the ProTrekkr window in the video, I’ve been making an Air Wolf cover with ProTrekkr. If I ever get it finished, I will publish a blog post here, where you can here the result.

On Easy Math Challenge development

I’d like to tell, why and what kind of bugs there were in my Android game Easy Math Challenge in its early versions.

The smallest bug was that there was “difficulty level 0”. If the user tapped somewhere else than the difficulty level buttons, the game gave “puzzles” like “3 = 3”. Well, those “puzzles” were always correct. This was fixed later.

The more annoying bug was, that in early versions the puzzles sometimes might be impossible.

The reason for that was, that I’ve used numbers also for the operations of puzzles. If for example + (plus) was 45, while calculating the result, the result got wrong so that 45 was part of the calculation numbers, not an operation. This was fixed later.

Video of the version 1.7.2 (no known bugs):

I wrote the program from scratch without any planning and often the usual mistake of mine: Work was done too at too late of hours.

If you still find some bugs, please let me know.

 

 

How to get timestamp in Monkey 2 with libc and in C

This morning I got implemented a little code, that can be used to get timestamp based on ANSI C code using Monkey 2 programming language’s libc.

Let’s take first look at the Monkey 2 code:

Namespace myapp

#Import "<std>"
#Import "<libc>"

Using std..
Using libc..

Function Main()

		Local seconds:time_t
		Local p:tm_t Ptr
		Local date:String
		
		libc.time(Varptr seconds)
	
		p = localtime(Varptr seconds)
		
		date = String(p->tm_sec) + "-" + String(p->tm_min) + "-" + String(p->tm_hour) + "-" + String(p->tm_mday) + "-" + String((p->tm_mon)+1) + "-" + String(1900 + p->tm_year)
		
		Print date
	
End

At the moment the output of the program is as follows: 40-31-8-26-10-2018

Year 2018, month 10, day 26, hour 8, min 31, sec 40.

Reversed order might be more useful in practice…

Let’s take a look at the C version:

#include <stdio.h>
#include <time.h>

void Date (char date[10+1]);

void main (void) {

	char datum[10+1];
	
	Date(datum);
	printf("%s",datum);

}


void Date (char date[10+1]) {
	time_t seconds;
	struct tm *p;
	
	time (&seconds);
	p = localtime(&seconds);
	
	sprintf(date, "%02i.%02i.%02i",
		p->tm_mday,
		p->tm_mon + 1,
		p->tm_year+1900);
}

To the year is again added 1900. This gives following output: 26.10.2018

The tm_mon is between 0..11, tm_year between 1900 + 0..n.

That’s it for now, lots of things to do…

How I made it on Music Game Jam 2018

My contribution to Music Game Jam 2018 was very quickly made. There was 2 weeks time and later some more time was given, but I made my game practically in two days. My ranking on the jam was 78th / 99. The Plus-version was made even in shorter time.

Below is a video from Build a Tune Plus, which is my thank you for your comments and downloads:

I probably should start (or learn) to make again music.. The short ending music for the Plus-version is made recently. The downloads are available below:

I signed today the exe files with the OV code signing certificate.

On Signing a Windows App

First I would like to tell you, that I have purchased an OV code signing certificate for one year. I found out from a blog, that K Software has at the moment the cheapest OV code signing certificate, $84 for one year.

As MicroSoft says in their documents, you must have a certificate, if you want to distribute or sell Windows apps.

There are three main categories of certificates on Windows platform: Open Source code signing, OV code signing and EV code signing.

The first is the cheapest — in the best case free — the last is the most expensive.

Open source code signing suits you if you do open source projects. You can check the definition of open source development here.

In the other cases the other two mentioned certificates are for you.

The OV certificate doesn’t prevent at first the smart screen to appear. In time, when you get enough downloads the smart screen won’t appear anymore. The EV certificate that is the most expensive, gives you immediate trust and no more smart screen to your apps.

The main benefit of OV certificate is, that none of the AV software programs considers your precious application a harmful file.

Once you have the certificate, signing the exe is as easy as follows:

signtool sign /a /f yourCertificate.pfx /p yourPassword yourApp.exe

The signtool.exe can be found at c:program files (x86)Windows Kits… The appropriate path should be added to your system’s %path% environment variable. If you don’t have …Windows Kits search the internet for Windows SDK version 8.1 or 10.

I have today signed most of my Windows apps. Smart screen will at first still warn you, but the file is no more considered a harmful file.