I have a maybe silly question:
Some devices have the same screen resolution (e.g. Edge 530 and Edge 540) but are different to handle because of different fontsizes.
I do it by testing a teststring length by pixel to check which device it is. That works but I wonder:
is there no other possibility to ask which device it is?
All I found is DeviceSettings.partNumber, but that returns a string which (at first sight) has nothing to do with the device name.
For Java, the string-switch works in the following way:
The switch statement compares the String object in its expression with the expressions associated with each case label as if it were using the String.e…
I believe Monkey C designers were not so poor at making string comparisons in the switch by reference, not by actual value. With comparison by reference, it has pretty much no sense.
So, I believe, the…
Little bit off topic here - but:
it's not easy to develop for a device you don't own.
A user sent me screenshots from the real device so that I could "optimize" the layout.
As described…
All I was saying if it's something a bit non-typical in Monkey C, you may want to make sure it works in monkey c, as I've seen things that don't and sample code can live forever... 
I tried it with this in an app
var str="abc";
switch(str) {
case "123":
System.println("found 123");
break;
case "abc":
System.println("got abc");
break;
default:
System.println("nothing");
break;
}
And it does work
Little bit off topic here - but:
it's not easy to develop for a device you don't own.
A user sent me screenshots from the real device so that I could "optimize" the layout.
As described in the posts above: there is a huge difference in fontsizes and font-top-origins !
This isn't java or python, where you can do
if(str="aBc")
in both. I happen do be doing a bunch of Java and python right now. In Monkey C, to compare strings you need to use equal(). Kind of like of like C where you use something like strcmp()
Java and Python are very different languages. In Java, it isn't the case *in general* that you can use "==" to compare two strings.
Yes, due to Java string "interning", you can *usually* use "==" for comparison, but it doesn't always work. Of course, no one wants to write code that only works in a specific set of cases, which is why modern Java linters will flag the use of "==" for string comparison and ask you to use String.equals() instead.
https://stackoverflow.com/questions/767372/string-equals-versus
www.tutorialspoint.com/compile_java_online.php
public class HelloWorld
{
public static void main(String []args)
{
String a = "hello";
String b = "hello";
System.out.println("a: " + a); // "hello"
System.out.println("b: " + b); // "hello"
System.out.println("a == b: " + (a == b)); // true
System.out.println("a.equals(b): " + a.equals(b)); // true
String c = "hello";
String d = "hell";
d += "o";
System.out.println("c: " + c); // "hello"
System.out.println("d: " + d); // "hello"
System.out.println("c == d: " + (c == d)); // false
System.out.println("c.equals(d): " + c.equals(d)); // true
}
}
I believe Monkey C designers were not so poor at making string comparisons in the switch by reference, not by actual value. With comparison by reference, it has pretty much no sense.
Some people always think they know stuff which they don't, even to the point of posting replies which were already refuted by the comment they were replying to. e.g. You posted that Java is smart enough to compile switch statements with string cases so that String.equals() is used, so of course he had to reply that "but '==' works for comparing strings in Java!" (which isn't even true in general), as if he didn't even fully read what he replied to (which is often the case.)
If you were so smart you would have tried it in Monkey C if you've never used it, as I did to verify it worked...
Or do you trust that everything works they way you think it should? Are there no bugs in Monkey C?