[mythtv-commits] mythtv commits

[mythtv at cvs.mythtv.org]

----------------------------------------------------------------------------
Changes committed by cpinkham on Sun Feb  6 06:21:27 2005

Modified Files:
   in mythtv/programs/mythbackend:
        mainserver.cpp mainserver.h 
   in mythtv/programs/mythfrontend:
        playbackbox.cpp playbackbox.h 
Log Message:


* Fix bug in taglist/playlist functionality on Watch Recordings screen
  when tagging the bottom item for a title.  Previously the item would
  not change color/font when tagged, now it should.

* Changed Watch Recordings screen to change font to "inactive" when
  deleting a recording.  Because of the recent delete thread changes
  on the backend, the recording will not disappear from the Recordings
  list immediately, so changing the font to "inactive" is meant to
  give the user an indication that their delete action is taking effect.
  Made similar change in the PlaybackBox::doPlaylistDelete() delete method.

* Fixed bug in Watch Recordings screen where we would load the recordings
  list twice from the backend after doing a delete.  The first was
  a manual load and the second was automatic after receiving a delete
  confirmation from the backend.  The frontend no longer does the manual
  load via fillList(), it does not reload until it receives the message
  from the backend saying it needs the recording list has changed.
  Made similar change in the PlaybackBox::doPlaylistDelete() delete method.

* Moved ScheduledRecording::signalChange(0) call from the doRemove()
  method on the frontend to the actual doDeleteThread() method on the
  backend which does the actual recording deletion.  This signalChange()
  method signals the scheduler to recompute so it makes more sense to
  have the backend signal this rather than the frontend since the backend
  is the process doing the actual delete.
  Made similar change in the PlaybackBox::doPlaylistDelete() delete method.

* Create a mutex for MainServer::doDeleteThread.  There isn't any technical
  reason this method can't be run multiple times at the same time, but
  sequentializing multiple deletes will help cut down on the impact to
  the database because of multiple deletes against recordedmarkup at the same
  time.  Same goes for multiple deletes on the filesystem.


----------------------------------------------------------------------------