basicCalculator | Basic Calculator , allows you to input any two numbers | Apps library

Does this solve your question?
TOTAL TIME: 1 to 2 seconds

Here I'm using the JSON library to do the computation as it is written in C(DONT GET CONFUSED WITH JSON'S FULL FORM) so its computationally efficient and fast.

After hacking around a bit with the GdkEventWindowState enums, I figured I can compare against the tiled state with the window maximized state together

ie., make sure to switch orientation to vertical only if the window is tiled and not maximized

Because the code

I found the solution. The magic words are jar { enabled = true } and bootJar { enabled = false }. I put it into the project which contains the library (backend classes) for the application.

Passing a function as a parameter to a flow is probably a bit ambitious. The node needs to evaluate it, after all, and checkpoint it so it can be evaluated later. If you really want to do this you can like so:

val lambda = @CordaSerializable Runnable { whatever() }

or

val lambda = @CordaSerializable fun() { whatever() }

.... but I'd suggest keeping it simple and just passing into plain old data objects. Yes, object serialization is powerful. But with great power comes great responsibility!

Inside your add and multiply methods you are using (uninitalized) member variables instead that the actual arguments.

Try with:

import java.lang.System;

This is unnecessary. java.lang is imported without you saying so, so you can already just write System in your code without this line. You can safely remove it.

Scanner inputScan2 = inputScan.useDelimiter("\\+|\\-|\\/|\\*|\\^|\\s");

Just because useDelimiter returns a Scanner doesn't mean you need to put it into a variable. You never use inputScan2 again except to close it (and in any case, inputScan2 is equal to inputScan after this line, making it redundant.) So I would shorten the line to this:

inputScan.useDelimiter("\\+|\\-|\\/|\\*|\\^|\\s");

and also remove the corresponding line that closes this unused scanner.

It's kind of weird to have loopCount2 and loopCount3 as separate variables when they're always just one away from each other. It seems like you could get rid of one of them.

I notice you don't have any methods except the main method. That's not so bad for a relatively small program, but it's best to get into the habit of splitting your code up into methods.

I notice you don't have any code comments. Comments often help you (and others) understand your code. Especially when the variables are named things like inputScan3 - that name gives a very general idea of the variable, but it doesn't really say why it's different from inputScan, for example. Comments would help with that.

A line like if(inputI.contains("+")){ is never going to be much good for compound statements - you're checking whether the entire String contains a +, which is not all that relevant if you're processing 4+2*3 because that doesn't tell you whether you're currently doing the addition or the multiplication. You're pretty much going to have to redo the way you check which operation you are doing if you want to handle compound statements.

I notice you set your answer array to a size of 1000. This is perhaps understandable with your other arrays because you don't know their size when you create them, but for this one, you already know the size - it's loopCount3 + 1. So you can write double[] answer = new double[loopCount3+1]; and save some memory.