Sometimes I need to compare code on a long and complicated event sheet. Right now I keep scrolling up and down. Is there a better way of doing this?

I would like to be able to view the same event sheet as a split screen and scroll to different sections of code. And be able to jump back and forth for editing. If editing is done on one split-screen-view-panel, then the other view-panel (being a different view of the same event sheet) is updated immediately.

Thanks for the reply. It will be a few days until I can try it.

I am making a Cribbage game and I am having trouble figuring out the logic of how to recognize a card run. In Cribbage you can score points for card runs that are played out of order sequentially but are still connected as a group. eg. 4-5-6 is a run and 6-4-5 , 5-6-4 are also runs.

Each card has a variable for the face value, 1-13. I am placing each card in the order they are played into an array. So using the example above, when the third card being played is a 6, how do I check if the last two cards played are both a 4 or a 5. (there can be no other cards played in between any of the cards in the run)

I would need it to recognized longer runs too. eg 5-3-1-2-4 (when the 2 is played it becomes a 3 card run(3-1-2) and when the 4 is played it becomes a 5 card run)

I do not believe any other apps were affected.

It correctly keeps the saved settings when I restart or turn off the phone.

I had the save game function working properly until my phone updated and then is was all erased. How do I get the saved game to never erase?

This is my code:

+ Function: On "SaveGame"

-> LocalStorage: Set item "SaveGame" to ArrayStats.AsJSON

Really? That's interesting. My C2 has always remembered what was being watched, even AFTER you close the program.

What are other people seeing in C3 and/or C2?

The "watch" feature is not working in debug mode. It does not remember the flagged properties when the window is closed and reopened. Is anyone else seeing this?

In C2, the watch feature allows you to flag and isolate properties that you want to view often in debug mode. These properties will be available in the watch tab in ALL future debug windows until you delete them.

I am actually having the opposite problem, and I posted something last light about it looking for help.

What I am seeing is the system preview, and APK working perfectly, but the remote preview is the one with lag problems switching between layouts (sometimes 5 seconds when it should be instant) and timing trigger issues. The wait related triggers were giving me very unpredictable results only seen in the remote preview. When I increased the wait time by a tiny bit, the trigger problems went away.

Has anyone experienced a remote preview timing problem? My program works 100% fine on the system preview but on the remote preview it is hit and miss. The wait related triggers were giving me very unpredictable results only seen in the remote preview. When I increased the wait time by a tiny bit, the trigger problems went away.

Also the delay times from layout to layout are much longer (sometimes 5 seconds went it should be instant) on the remote preview than on the system preview. The final APK seems to work like the system preview.

This tutorial gave me the exact solution I was looking for.

https://www.scirra.com/tutorials/4973/m ... t-controls

The trouble can only be demonstrated through mobile preview...

When you touch the top or bottom of the screen with a single touch the sprites are generated in the correct position, but during multitouch the second sprite appears on the wrong side of the screen. What code am I missing to correct this?

https://www.dropbox.com/s/20hmba0ngzhvo ... t.c3p?dl=0

I am finally able to access https://scirra.com on my main computer using my home Wi-Fi, but I can only do this using https://kproxy.com/ proxy server. Does this my my main IP address was somehow banned?