In other words, create something on Screen 1, go to Screen 2, make code, run app, try to switch screens via button or whatever..... doesn't work.
We're using Win7, AI2, Chrome, and Nexus and Samsung Tab tablets.
Yes you can switch screens on the Emulator. Be aware, the more glitz you got on the screen: buttons, layouts, images; the 'harder' the emulator has to work to re-render the screen. Things that can also affect this is: how hard the local network is being loaded (if your network is designed for 10 and you use 30 seats?), the cpu and amount of RAM on individual PC's etc.
A technique I often recommend is to code, especially when you change or modify a layout, button or other graphic control on the screen, is NOT to CONNECT at all. AI2 can be used to code blocks and the Designer screen without Connect > Emulator. To do so, save an aia frequently or Projects>Save project as...with a serialized name. You do not have to code with 'live' testing all the time.
Be aware, projects with lots of glitz take longer to render and use lots of PC resources. One reason WIFI or USB is the preferred method of live testing. Yes, we realize this is not possible in many environments.
Often, using a button on the app to switch screens while in the emulator may not work. Why? I do not know. Other times it will. What I do when that fails is switch screens using the Buttons for the screens:
Try that. Just do the screen switching there; if on Screen2, press Screen1 or whatever the student uses. Does switching like that ameliorate the issue?
Also, are you and your class aware of the pitfals of switching between screens without closing the screen you leave? Screen1 is an exception, it is always live.
Is that what you wanted to know or did I answer the wrong question?
how to do switching screen ?
@Budiman: see here
댓글 없음:
댓글 쓰기