OK, last question what do you mean by building and testing it out on a real device. Sorry for all these questions I’m just starting.
Another question if you are doing a build would I do it on android or windows, if I am working on a windows but wanting to upload my app for android devices. Also please answer my last question I am still a little confused about the concept.
The Corona Simulator is just that a simulator. It runs either on Windows or macOS and has to abide by the rules of that operating system. For instance, if you want to run Google in-app purchases. Google makes libraries that we can use to allow Android devices to make purchases. But that library does not work on Windows or macOS. Almost all Ad and analytics plugins fall into this category. The Facebook plugin does as well. It could be something not obvious like Windows and macOS have case insensitive operating systems while Android and iOS are both case sensitive. This can cause problems if you have a file named: Player.PNG on your computer, but in your Corona code you say:
local player = display.newImage(“player.png”)
It will work just fine in the simulator because neither Windows or macOS cares about if the letters are upper or lower case. When a person runs your app on their phone or tablet, it will crash because “player.png” is not equal to “Player.PNG”. These are easy mistakes to make when developing that won’t be exposed until you tell Corona to build your app and you plugin your test device (phone, tablet) into your computer via it’s USB charging cable and install your app on your device and test it there. The splash screen only works on a device, not the simulator. If you plan to have any text fields for people to type into, that behavior is really different between mobile operating systems and desktop/laptop operating system.
In other words, if you want to avoid a bunch of 1 star reviews, you should test your app on real device and don’t depend on the simulator as your only testing.
But this isn’t something you need to worry about today. Worry about your app first. The splash screen is probably one of the last things I’d work on.
Rob
You will do most of the work on Windows. Then with the Corona menu’s choose Build then choose Android. We will output a .apk file. There are multiple strategies on how to get the .apk file onto your device. There is a lot of information that we don’t need to repeat here in the forums. This is why we have our great Documentation, some of which are “Guides” designed to help walk you thru all of this. See:
https://docs.coronalabs.com/guide/index.html
As for this particular question, it’s covered in this guide: “Signing & Building – Android” https://docs.coronalabs.com/guide/distribution/androidBuild/index.html
Rob
Does velocity.png exist in the same folder as main.lua or is it in an “images” folder?
For the community benefit, this is a continuation of a support email. The poster is currently getting just a black screen after adding the splashScreen block to the build.settings.
What’s in your console log? (the text window behind the simulator)
Rob
velocity.png is in a seperate folder of images. I did not put main.lua in a folder, should I. This is the console log.
15:11:42.793 15:11:42.793 Windows simulator build date: Mar 31 2017 @ 14:34:46 15:11:42.793 15:11:54.074 15:11:54.074 Copyright (C) 2009-2017 C o r o n a L a b s I n c . 15:11:54.074 Version: 3.0.0 15:11:54.074 Build: 2017.3068 15:11:54.074 Platform: SM-G900S / x64 / 10.0 / Intel(R) HD Graphics 630 / 4.4.0 - Build 21.20.16.4541 / 2017.3068 / en\_US | US | en\_US | en 15:11:54.074 Loading project from: C:\Users\bathw\OneDrive\Documents\Corona Projects\Balloon Chaos 15:11:54.074 Project sandbox folder: C:\Users\bathw\AppData\Local\Corona Labs\Corona Simulator\Sandbox\balloon chaos-39C7784870EF88519FAF5298CB69BEE5\DocumentsYou need to point to the image by its actual location. If you put it inside a subfolder, you need to specify that to the plugin.
Brent
I changed that what you said, before so th log console is what it is. i put images = “images/velocity.png”
I also have another question it is when I bought the $99 splash control plugin how does my text editor sublime text editor 3 know I have bought the splash control because I didn’t put any password in my app to let it know or anything.
It has no impact on Sublime Text 3. The Splash Screen plugin is special. Normally for plugins you have to put them in your “plugins” table in build.settings, however for the splash screen you just need the splashScreen table that you’ve added. The Corona simulator reads your build.settings file and downloads any required plugins like the splash screen. You at one point logged into the simulator with your password.
Rob
OK , then do you have any recommendations of what text editor to use. Something that professionals and maybe you would use.
That would also fit the plugin, of course.
Here are some options we recommend:
https://docs.coronalabs.com/guide/programming/01/index.html#text-editors
Would the ones that work be the add on packages.
which one would you choose because I’m just a beginner and i don’t know much.
It’s really up to you. If you’re on Windows (I believe you are), many people like Sublime… but it’s not free. A lot of people are turning to Atom because it’s highly customizable. You should check out a few options and decide which one “feels” good to you.
Brent
Would atom work with the SplashScreen control plug in.
Your text editor is a completely separate tool that Corona. You can use any text editor that you like and Sublime Text is a great editor. It’s what I use. But at the end of the day, all Sublime Text (or any other text editor) is a way for you to write and edit code and save it. After that the Corona simulator reads those text files and runs your app for you.
Any editor will work. Atom is a good editor too. But your problem isn’t with the editor, something else is going on with your code. That’s happening in the Simulator.
What are you expecting to see?
What does your main.lua file do? Or are you trying to see the splash screen before you write the rest of your app?
Rob
Yes I am trying to see the splash Screen before I start the app, and to make sure the text work I put some text in the main.lua to make sure it changes. So I can see. This is how my main.lua looks.
local options = { text = "Hello World", x = 140, y = 220, width = 128, font = native.systemFont, fontSize = 18, align = "right" -- Alignment parameter } local myText = display.newText( options ) myText:setFillColor( 1, 0, 0 )Are you seeing the text in the simulator? If so everything is working as expected. You won’t see the splash screen until build for a device and install it and run it on that device.
Rob