You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The talk list and related talk view should be sorted in ascending or descending order.
Sort direction should be saved and restored from user defaults.
This is a better use of space than the static title and gives the layout more room.
In the future, this segmented control could be collapsed into a toggle button to be placed in a toolbar.
Instead of arrows, it should show fading bars, black, dark gray, and light gray lines representing topics fading as they age, from darkest to lightest or vice versa.
The text was updated successfully, but these errors were encountered:
* The talk list and related talk view can now be sorted in ascending or descending order via a control in the navigation bar. (Refs #38)
* This is accomplished with a boolean property and the sort descriptor of the fetch request.
* Sort direction is saved and restored from user defaults.
* The title is now the topic, i.e. the topic of the selected issue. (Refs #33)
## Refactoring
* Pare down the fetch request automatic accessor to make it easier to refresh the fetch request, potentially with new data, and do so.
* The reloadList: method now serves a legitimate purpose, reloading the fetch as well as the table view, which can still be reloaded directly.
## Style
* Took out all that commented table view code from the talk list.
* That code was replaced with the simple, naïve implementation. It remains implemented this was in the talk view controller, so we can compare the two.
In the future, this segmented control could be collapsed into a toggle button to be placed in a toolbar.
Instead of arrows, it should show fading bars, black, dark gray, and light gray lines representing topics fading as they age, from darkest to lightest or vice versa.
The text was updated successfully, but these errors were encountered: