I'm not sure, not having a copy of your total code. I expect you initially set the global index to 1 then change it when your TouchedRedValue on Screen2(???) is 91, when you need to set the Index to 1; when TRV is 8, then the Index should be 2; etc. to point to and select the appropriate question/answer pair.
There are several ways you could handle changing the question/answer on a single screen.... code like this might work
Keep the Lists on Screen2 or Screen3 but probably not both! A developer can code copies on both. Why place copies on a Screen that is not needed?
Providing advice with minimal information available for your project is getting complicated and a guessing game Meghan. You do realize no one can see what you are doing unless you share all your Blocks with images or post a copy of your aia here in the forum. Sharing is the only way someone can look at ALL your logic and make meaningful suggestions. We want to help but we don't know what you are doing. Are you trying to use virtual screens now or using 3 or 2 screens or what?
In Initialize, make these changes and in Answerbutton add the upcase so when someone answers false or False or FALSE the answer is always treated the same.
Added a Boolean variable touchSuccess to inhibit Canvas touches anywhere but in a cell to avoid a âscreenâ change when touching outside of a cell.
Since all the âanswersâ (except the first (false)) require entering numbers, set the TextBox to use NumbersOnly (see Screen1.Initialize). This simplifies answer entry for the USER by only allowing numeric input. Changed the first question to read 'enter 0 for false and 1 for true and changed the correct answer from false to 0 . This works if all the answers are numerical values. If future questions are multiple choice, the choices would have to be numerals rather than A,B,C.
Added a marker (a red ball) to show the current cell selected.
Added a WebViewer.GoToUrl block with a âtemporaryâ url
Issues/ possible improvements to consider:
If the USER clicks on one of the black polygons (triangle, trapezium, pentagon) the USER is clicking on a BLACK color space. The app hasnât any code to handle that. Either eliminate those black images from the cell or code the Touched event to provide a response when touching them.
Add a simple scoring mechanism. (Use the Blocks in the Answerbutton event handler to increment a counter when correct (subtract when wrong answer perhaps?)
Add sound.
Finish adding questions and answers.
Provide for alternative questions/answers
1 - Provide an alternate questionList, QuestionImage and answerList using Blocks
2 - Source the questionList, QuestionImage and answerList from a Google shared Spreadsheet.
3 - Provide alternate Lists using a TinyDB and code a mechanism to determine which list should be used, either by using a MENU or a random selection.
I think virtual âscreen changesâ are smoother and faster than real Screen changes. What do you think?
When working with the Designer, tick the box Display hidden components in Viewer so you can
view all the virtual screens. Also set Screen1 Property to Scrollable (at least while you are developing) so you can view all the virtual screens in the Designer.
Good luck with this interesting Project whether you choose to use virtual screens or real Screens as you continue. Keep exploring.
So I decided to try to make a virtual screen for the questions, but now its not doing what I anticipated. Would someone be able to take a look and tell me what I need to do to fix it?
Also, I was trying to do a score and I couldnât get that to work either. Numberville (1).aia (657.1 KB)
Did you post the aia you intended? The Project just posted does not contain a single virtual screen! It contains four Screens (1,2,4 and 5). See Building Apps with Many Screens , itâs about virtual screens. It is possible the file you sent was corrupted; it loaded but is missing large sections of your Project
Did you look closely at the example using virtual screens posted two days ago titled NumbervilleVirtualScreens? Load the aia and consider modifying it; the example might save some time if use that example as the basis for your app and start again or post the correct aia since you âdecided to try to make a virtual screen for the questionsâ but that did not appear to be in the aia you sent.
The blocks you used to â trying to do a score and I couldnât get that to work eitherâ donât exist.
âwhat I need to do to fix it?â Try again and post the correct aia. Create an image of the blocks you used to to create a scoring feature and post that image too.
So, do you want to give up? What were you doing when the score feature failed? An error message; did it say to give up or what? You didn't tell us. Do you want more advice? If so, it means sharing information I would expect.
Here are two guesses (you don't have to score them):
Remove these blocks, they are the culprit for one error message I saw. Removing 'fixed' the issue.
Virtual Screens but a second real Screen. OK. On Screen2 you have this disastrous code.
When a developer does x , he/she creates a memory leak by re-opening Screen1. This creates an additional instance of Screen1 in memory every time it is done. Do this often enough and the app will crash the device. Instead code this like the check mark; close screen closes the current Screen gracefully and returns to Screen1.
Fix these two issues and the app might work as you intended.
Oh, sorry, one more issue: Move the location of the game piece to anywhere other than on the first cell or any cell. Starting at the first cell causes issues. Since you now have the 'capability' of restarting the game, you also need to re-position the red ball and reset Score to 0 with code. This issue arises because you added the ability to re-start the game.
Of concern, but not necessarily a fatal issue is
. You might want to change the TTS pitch Block location.
Pitch sets the speech pitch for the TextToSpeech. The values should be between 0 and 2 where lower values lower the tone of synthesized voice and greater values raise it.
The default value is 1.0 for normal pitch.
Change pitch possibly by placing the block in the Screen1.Initialize , then pitch is called once. Calling pitch in Answerbutton.Click attempts to change the pitch to normal pitch each time the Button is clicked un-necessarily using system resources.
TTS and Scoring are nice additions as are the instructions. Be aware, making changes in your app may have consequences you do not expect, even small changes. Be prepared to debug. (For instance, while your basic scoring works, a clever student can re-answer a previous cell question and get additional points. Debugging is just part of the development process. A developer can not anticipate everything.
Thank you for you help! It is working now! I am wanting to use my app in multiple classrooms within the next months. Would the app work on tablets, or how could I make the app accessible to all of our students?
Wonderful Meghan! Very glad you got your app working satisfactorily.
Yes, the app will work on tablets. I tested on a tablet, the emulator and a small cell phone. It seems to work well on all. The 'secret' is to set ScreenSizing to Responsive (which is already part of your code).
How to distribute to your students
Here are three ways:
1 - Build the app apk file using option market 2a. ( Step 1, then 2a)
Doing that provides a QR code that can be scanned with a student's Android device. This provides a one time QR code that will work for two hours only.
There are other, more complex ways to get the apk on to an Android. This link explains how Share an App. The recommendation to send an apk as an attachment to an eMail and have the recipient does not work if using gMail since Google initiated greater security protocols last year. Some alternatives are discussed for installing an apk on an Android in the link. And here is advice from Google.
Try the first method with a 'guinea pig' and see how it works for the student or teacher you share with.
using the index with something like Index= 1,2,3 etc.
Remove these blocks, they are the culprit for one error message I saw. Removing 'fixed' the issue.
Move the location of the game piece to anywhere other than on the first cell or any cell. Starting at the first cell causes issues. Since you now have the 'capability' of restarting the game, you also need to re-position the red ball and reset Score to 0 with code. This issue arises because you added the ability to re-start the game.
. You might want to change the TTS pitch Block location.
Very glad you got your app working satisfactorily.
