Opened 4 years ago
Closed 4 years ago
Last modified 3 years ago
#9771 closed Patch - Bug Fix (fixed)
Disk free bar shows 0.0%, 0GB
| Reported by: | Jonatan <mythtv@…> | Owned by: | beirdo |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | MythTV - General | Version: | 0.24-fixes |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
Upon entering Watch Recordings, the disk free bar can show "0% used, 0 GB free", and will stay that way until for example a new recording starts or is deleted.
The issue seem to be present both in master and 0.24-fixes, http://www.gossamer-threads.com/lists/mythtv/users/479652
The attached patch attempts to solve this by sending an UPDATE_USAGE_UI event to PlaybackBox? from PlaybackBoxHelper::UpdateFreeSpace?(). When PlaybackBox? receives the event it calls UpdateUsageUI() to update the displayed disk free bar.
Attachments (1)
Change History (7)
Changed 4 years ago by Jonatan <mythtv@…>
comment:2 Changed 4 years ago by beirdo
- Owner set to beirdo
- Status changed from new to accepted
comment:3 Changed 4 years ago by Github
Load the disk free bar in the PBB on each UPDATE_FREE_SPACE
On startup, the playbackbox's disk free display states 0% until the first recording is made, or the first file is deleted. This patch makes it also update any time an UPDATE_FREE_SPACE event is received from the backend.
Refs #9771
Signed-off-by: Gavin Hurlbut <ghurlbut@…>
Branch: master Changeset: 4426dd65762dbc286b74e1fe5d85945d0b745ccf
comment:4 Changed 4 years ago by Github
- Milestone changed from unknown to 0.25
- Resolution set to fixed
- Status changed from accepted to closed
Make the free space updates start in PBH
Make it so as soon as the playbackboxhelper thread starts, it forces an update of the free space so the bar can start updating. Once it has been started, the free space will update on a timer basis (looks like every 15s).
Fixes #9771
Branch: master Changeset: 62d70845b46387bf16e0a1e1c75f7a0082ba61f3
comment:5 Changed 4 years ago by beirdo
- Milestone changed from 0.25 to 0.24.2
Seems to apply both to 0.24-fixes and master