Life In 19x19

fwiffo wrote:Actually, now that you mention that, I have noticed an issue when sliding out the keyboard on my Droid. If I select a move, then want to enter a comment, I'll slide out the keyboard and it will skip back to scanning for games, undoing the move.

Also, something that maybe falls more in the feature request category, it would be nice if the app switched orientation based on the orientation of the phone/keyboard like other apps.

Thanks for the feedback. I will look at intercepting sliding out the keyboard. Android has a lot of interrupt types.

As far as switching orientation automatically, I started that way and found hat it would be a lot more work than I was willing to put into it at that time. Every time you change orientation, Android kills the app and restarts it to switch the selected layout. I did create a landscape layout which you can select from preferences, but I think it is very ugly. Take a look at that, if you have suggestions, let me know. I may some day put in an option to allow automatic orientation, if I can get the landscape layout in better shape.

Huh. I expected switching orientation would be a signal you could intercept. A lot of apps (e.g. KGS) seem to switch on the fly OK (not that it's necessarily easy, and of course, you have to program two layouts). It's not a big deal; I don't type comments mid-game that often.

fwiffo wrote:Huh. I expected switching orientation would be a signal you could intercept. A lot of apps (e.g. KGS) seem to switch on the fly OK (not that it's necessarily easy, and of course, you have to program two layouts). It's not a big deal; I don't type comments mid-game that often.

anDGS was my first Android app so as I was learning the interfaces, I chose to keep it very simple. That enabled me to get something useful that I could use every day up and running fairly quickly. As I said in the earlier post I have a lot of the pieces done, like portrait and landscape layouts, can manipulate the interrupts, etc. It would take some work and code structure change to save off the state and restore it every time Android destroys the app on an orientation change. If I do an auto orientation feature, I would make it optional as I don't like this particular app changing orientation as I am waving may phone around while making moves on DGS.

The keyboard slide out orientation change may be interesting for droid. I am locking it down for the next release so it should not cause the issue you reported while playing on DGS. I already had it locked down in the local game editor, just did notice it for the online player.

Sadly it seems there are still some problems.
After a certain point in the game I was recording it just keept crashing and recovery just returned it to a point a couple of moves earlier. Crashing happned on both returning from sleep and on trying to save the file at any point later than the position it returned to. Saving at the recovery point worked fine.

I have PMed you the sgf and an android log (not sure how much time it covers).

I guess the sgf became corrupt there for some reason and that created the problem. There was a ko involved, not sure if that's important or not.

Next move in the game is capturing to end the ko.

Mcgreag wrote:Sadly it seems there are still some problems.
After a certain point in the game I was recording it just keept crashing and recovery just returned it to a point a couple of moves earlier. Crashing happned on both returning from sleep and on trying to save the file at any point later than the position it returned to. Saving at the recovery point worked fine.

I have PMed you the sgf and an android log (not sure how much time it covers).

I guess the sgf became corrupt there for some reason and that created the problem. There was a ko involved, not sure if that's important or not.

Next move in the game is capturing to end the ko.

Thanks, the log looks like enough time as a quick look showed a stack overflow in trying to save a recovery file or the sgf file. The sgf you sent does show a truncated record i.e. no closing parenthesis.

mike

Looks like the last update finally fixed the crashing bug, got 2 full games recorded now without any problems.

Mcgreag wrote:Looks like the last update finally fixed the crashing bug, got 2 full games recorded now without any problems.

Thank you for the report and thank you for your patience while I fixed the bug.

Now that this stable release is out, I can start working again on annotations in the local editor.

If I may make a feature request then I would like a jump to move feature. Either jump to move number or jumping to point when stone was played. It has happen several times now then I been looking at games post playing that I accidentally hit last move instead of next move and when that happens it can take a long time to get back to where I was.

Mcgreag wrote:If I may make a feature request then I would like a jump to move feature. Either jump to move number or jumping to point when stone was played. It has happen several times now then I been looking at games post playing that I accidentally hit last move instead of next move and when that happens it can take a long time to get back to where I was.

Done!

Version 1.17 has a new Options menu in the game editor which had a Mode selector to switch between "edit" and "browse" modes. "edit" works as before and inserts moves on the board, "browse" goes to the first move at the location specified which can be earlier in the game or later (or does nothing if there was no move in the main line of the game record there.) You can even browse to a move, switch modes to edit and insert variations.

A little gift for your loss of complete recordings in the early early rounds in the EGC.

BTW, I could easily add an option to jump to a move number if it was useful, but move numbers are not always counted the same way by everyone and not as intuitive as the new feature above, so it is less attractive to me.

Another feature I could add is a preference in the main menu to control the "double arrow" buttons on the editor, for example instead of going to the beginning, I could make it jump forward or backward by some number of moves, for example 10. I think that is a general preference rather than an option settable for a particular game editing session.

You have got me thinking about the editor again.

Thank you for one of the few apps I use everyday
I have two feature requests for you

• Pass and Resign "moves"
• List ongoing games (clickable links for the game record would be nice)

I apologize if these things are possible to do already, but I failed to understand how to do it.

Another thing that might be nice would be if the app could notify me if that I have games waiting for my move. This is not very important though.

pel wrote:Thank you for one of the few apps I use everyday
I have two feature requests for you

• Pass and Resign "moves"
• List ongoing games (clickable links for the game record would be nice)

I apologize if these things are possible to do already, but I failed to understand how to do it.

Another thing that might be nice would be if the app could notify me if that I have games waiting for my move. This is not very important though.

Thank you for the comment and requests.

- Pass and Resign "moves"
I would have liked to have implemented this already, but the current "Robot" interface on DGS does not support this. When the next version of the interface is ready, I will support it. I may become impatient and figure out how to do it through the browser interface as it is such a basic needed feature.

-List ongoing games
I could implement this. I have been thinking of redesigning some of the pages to allow for more features like this (I personally want to see messages.) But a lot of new features are driven by an update to the DGS Robot interface.

-Notifier
I could do it and would like to do it, but, as you said, has so far been a low priority item.

It is great to get requests, it often motivates me to work on the client some more. The standard board marks in version 1.19 was from a user request.

In recording mode isn't possible to add an option for autosaving the game move-by-move?

If enabled, after each move (or after each 2), the sgf is updated automatically. Maybe the user can type wrong moves, so there are several trees you can calmly delete with any sgf editor later.

kaliya wrote:In recording mode isn't possible to add an option for autosaving the game move-by-move?

If enabled, after each move (or after each 2), the sgf is updated automatically. Maybe the user can type wrong moves, so there are several trees you can calmly delete with any sgf editor later.

On any Android device or app state change the local editor saves the current sgf game tree in a file called recovery. The first line of the file is some inforation for anDGS, but the rest is the entire game tree in standard sgf format. You should never have to look at the recovery file as you are prompted to recover (or not) when reentering anDGS editor if the recover file is there from the last session. But it is all there if you want to look.

When you are at some point you want to save, you can always save in the original sgf file or a different one or even ignore all the changes. So nothing is ever lost, unless the user takes a specific action to cause the loss.

This covers the situations that I can think of, so even if you forget to save at the end of a session, you will be prompted to be able to recover then save on the next session. The only possibility that I can think of is if you have some other app tracking the sgf record move by move as the anDGS editor is updating it. But that seems extreem and if someone ever does that I can add an option.