OpenScore

The Exiting avscore.swt.Baseframe action should trigger a write of any changes still waiting in memory

Bug #368576 reported by Ken McLean
8
Affects Status Importance Assigned to Milestone
OpenScore
Fix Released
Critical
Tudor Holton
OpenScore heatwave

Bug Description

The Exiting avscore.swt.Baseframe action should trigger a write of any changes still waiting in memory.

May be related to the looping upgrade bug.

Ken McLean (kenmclean)
Changed in openscore:
assignee: nobody → tudor
importance: Undecided → High
milestone: none → heatwave
status: New → Confirmed
importance: High → Critical
Revision history for this message
Craig Mahony (cmahony) wrote :

Fixed this. Seems to work. Needs someone else to also check.

Changed in openscore:
status: Confirmed → Fix Committed
Revision history for this message
Ken McLean (kenmclean) wrote :

This will require a modified version of Score that locks the file for an indefinite amount of time, so that the application hangs and waits on closure.

Tudor will have to help me out with this one, so I will defer testing until then.

Chris Hodgen (bivhitscar)
Changed in openscore:
status: Fix Committed → Fix Released
Revision history for this message
Ken McLean (kenmclean) wrote : Re: [Bug 368576] Re: The Exiting avscore.swt.Baseframe action should trigger a write of any changes still waiting in memory

That was me. I was accidently logged in as a friend of mine.

Ken

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.