Re: [Audacity-devel] Platform Specific Essentials

[James C. <cr...@in...>]

James Crook wrote
Richard Ash wrote
>> ...on Linux, and I nearly wrote it off as unrepeatable because it took
>> about 4 attempts to get it to happen. I'll try and do it again in a
>> debugger tonight and see if I can fix it then.

> I think the track stopping moving after a few drags is a separate issue 
> and not as difficult to understand.  It happens on windows too.  I've a 
> good idea what causes that, am looking at that aspect today and will 
> send an update if I track it down.

The track stopping movement after a few drags was down to a 
miscalculation of the item size.  The size was being measured as that 
for one of the tracks rather than the combined size of both tracks when 
in a stereo pair.

I've fixed that and that is in CVS.


Julian Foad wrote:
> I pointed out what I believe to be the buggy code in my email of 2007-08-11, 
> subject "Seg fault moving tracks up and down". It was buggy 
> linked-pair-of-tracks handling in MoveUp and MoveDown. It looked like the 
> problem should be identifiable and fixable by inspection even if you can't 
> reproduce it. I can test it for you afterwards.

> - Julian

Julian, please try with the latest CVS.  As well as the change described 
above I've also put guards around the NULL pointers.  This should now 
give us an ASSERT dialog in debug builds and avoid a crash in release 
builds.  From your comments and inspecting the code it looks like 
Audacity was trying to move a track down that was already at the bottom. 
  It could be that that was in turn caused by miscalculation of the 
track size - it's not 100% obvious from inspecting the code.  Anyway, 
please give it a try and let us know if it fixes the problem.


--James.