Automated testing and a scripting language Was: [Rosegarden-devel] Problem with BasicSelectionCommand

[Heikki Johannes Junes]

I am sorry to not have digged to this particular problem. I tried some time ago to fix
some problems in NotationView, but unsuccessfully. My critic was that
it is difficult to find the real source of error in some cases. These means
that the code is not easy to maintain. Any change which increases maintainability
is welcome. 

It would be nice to have some automated testing for each release. This would lead into more stable releases. If the program had a scripting language of its own, it would be easy to automate such testings.

Heikki

Most probably I did not answer to your question. 

Heikki

2007/6/1, Arnout Engelen <address@hidden>:

Heikki Johannes Junes schreef:
> I cannot not answer to your question, but rather I would like to raise
> a general challenge to improve the code of the notation engine. Most
> of the notation code may be ok, but the the code is not everywhere
> very transparent. Therefore, there may be a need of reconstructing the
> notation code in a more transparent packets. Only good looking code
> can be easily maintained.
So you gather the problem is probably in the NotationView rather than
the BasicSelectionCommand? I tried tracing it a bit (some pointer is
dereferenced but turns out not to contain an object of the expected type
it seems iirc), but didn't find the real cause of the corruption. I'll
try to dig in further...

Personally I'm hesitant to make any big changes as I'm not familiar with
the code, but I try to make sure any change I make is an improvement :).


Arnout

-- 

Heikki