Introducing CanAce

[Lawrence Woodman]

Hello All,

I have recently forked xAce (http://lawrencewoodman.github.com/xAce/) to
create
CanAce. This was done because I wanted to speed up development using a
proper
GUI library and wanted to make the emulator less platform dependent.

CanAce uses a combination of C and Tcl for the logic while the display
is created using
a mixture of Tk and SDL.

It is still early days, but to see the results so far you can download
the latest code at:
https://github.com/LawrenceWoodman/CanAce/archive/master.zip

and the Repo itself is at:
https://github.com/LawrenceWoodman/CanAce

I hope you like the direction this is going in.


Lorry

--
vLife Systems Ltd
Registered Office: The Meridian, 4 Copthall House, Station Square, Coventry, CV1 2FL
Registered in England and Wales No. 06477649
http://vlifesystems.com

[Marcos Cruz]

En/Je/On 2012-12-31 15:06, Lawrence Woodman escribi� / skribis / wrote :

> The interface is a little bit slow at the moment but will get quicker.

Yes, I realised, but forgot to mention. I thougth it was because of my
computer.

> > I will post there about a problem I
> >have with CanAce and text spooling.

> Unfortunately I noticed this morning that there is an awkward
> problem with text spooling. I'm pretty sure I know
> how to fix it and will try tomorrow morning. I'll post on
> canace-dev as a follow-up once I know what's happening.

Text spooling doesn't work fine for me, normal or fast. The input
eventually gets corrupted. I tried to change the value of set_itimer()
in fast_speed() but it's already 250, not 1000 as in xAce (is it
intended, by the way?). Nevertheless I tried lower values without
result.

I'll follow the thread in canace-dev.

Marcos

--
http://programandala.net

[Lawrence Woodman]

On 31/12/12 15:40, Marcos Cruz wrote:
> Text spooling doesn't work fine for me, normal or fast. The input
> eventually gets corrupted. I tried to change the value of set_itimer()
> in fast_speed() but it's already 250, not 1000 as in xAce (is it
> intended, by the way?). Nevertheless I tried lower values without
> result. I'll follow the thread in canace-dev. Marcos

I have uploaded a commit, which I should make spooling much quicker,
remove the dependency on the speed of your machine (so you won't need to
change any values) and not corrupt.

The commit is at:

https://github.com/LawrenceWoodman/CanAce/commit/423c3351ec7da952ffdff97bc4e352e79f62b2b0

You may also be interested that your name also helped me identify
another bug where the letter 'z' wasn't being spooled properly. The
commit to fix that is at:

https://github.com/LawrenceWoodman/CanAce/commit/45d91115fd5797de34f3b3a7fd756792ddf9126c

I noticed the 'z' problem when I was spooling in your beetle brick chase
code and saw that it kept missing off the 'z' from your last name.

bfn

[Marcos Cruz]

En/Je/On 2013-01-02 08:11, Lawrence Woodman escribi� / skribis / wrote :

> I have uploaded a commit, which I should make spooling much quicker,
> remove the dependency on the speed of your machine (so you won't
> need to change any values) and not corrupt.

I tried the -S parameter and I had no problem, thank you. Now it worked
without corruption. By the way, the menu option does the slow spooling.
If finally fast spooling finally works fine, is it useful to keep the
slow one? Does it have any advantage? If so, also fast spooling should
have its menu option.

> You may also be interested that your name also helped me identify
> another bug where the letter 'z' wasn't being spooled properly.

I'm proud of my effortless contribution to the C debugging techniques!
[:-)]

Marcos

--
http://programandala.net

[Lawrence Woodman]

On 02/01/13 13:33, Marcos Cruz wrote:

En/Je/On 2013-01-02 08:11, Lawrence Woodman escribió / skribis / wrote :

I have uploaded a commit, which I should make spooling much quicker,
remove the dependency on the speed of your machine (so you won't
need to change any values) and not corrupt.

I tried the -S parameter and I had no problem, thank you. Now it worked
without corruption.  By the way, the menu option does the slow spooling.
If finally fast spooling finally works fine, is it useful to keep the
slow one?  Does it have any advantage? If so, also fast spooling should
have its menu option.

I have been mulling this over and have decided to add a normal/warp speed mode accessible via the menu and a key combination (Alt+W).  Spooling from the menu will start at normal speed but will increase if you go into warp mode.  This is because as machines get faster it is impossible to see properly see what is flying by, so this will allow a user to toggle in and out of warp mode as needed if they see an error.

Ultimately there could be a configuration option which could specify whether spooling from the menu also switches the emulator into warp mode.  BTW, thanks for the idea of using the XDG Base Directory Specification in a previous post, I had never heard of it until your mentioned it.  I have been looking into it since then and think this could be a good way to go.