#60 closed task (released)
Add UI to add/remove/edit weapons in GTK
Reported by: | ibboard | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | WarFoundry 0.1 |
Component: | WarFoundry-GUI-GTK# | Version: | Unknown or N/A |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #86 |
Description
The WinForms interface is currently slightly ahead of the GTK# interface as it lets users add/edit/remove weapons. We need a matching interface for the GTK# version of the app.
Change History (27)
comment:1 Changed 11 years ago by
Blocking: | 86 added |
---|
comment:2 Changed 11 years ago by
Owner: | ibboard deleted |
---|
comment:3 Changed 10 years ago by
Status: | new → confirmed |
---|
Move tickets to new "confirmed" status to show that they've been checked
comment:4 Changed 9 years ago by
comment:5 Changed 9 years ago by
(In r656) Re #60: Add UI to add/remove/edit weapons in GTK
- Remove "not implemented" exceptions and add first implementation of setting equipment list
- Add widgets to add equipment form
- Subscribe to Clicked instead of Activated to hook on to correct event
- Extract tree rendering method into helper class
Also:
- Improve exception handling of unhandled exceptions (print full stack trace with "caused by" hierarchy)
comment:6 Changed 9 years ago by
comment:7 Changed 9 years ago by
comment:8 Changed 9 years ago by
comment:9 Changed 9 years ago by
comment:10 Changed 9 years ago by
(In r661) Re #60: Add UI to add/remove/edit weapons in GTK
- Make enabling/disabling fit the values passed (copied from existing WinForms checks)
- Add extra interface methods and properties to get necessary values from UI to use in command
- Implement new interface methods
- Implement command execution
- Make use of IDisposable interface instead of defining Dispose ourselves
Also:
- Use existing method of printing exception stack traces in main window
comment:11 Changed 9 years ago by
comment:12 Changed 9 years ago by
comment:13 Changed 9 years ago by
comment:14 Changed 9 years ago by
comment:15 Changed 9 years ago by
comment:16 Changed 9 years ago by
(In r667) * FrmAddEquipment.cs: Re #60: Add UI to add/remove/edit weapons in
GTK
- Cache more values in the controller so that we don't rely on the UI as a the model/data store
- Move enable/disable of amount controls to controller (assumes minimum numeric and percentage, so implementation has its own custom implementation to handle "Equip All")
- AddEquipmentUIControl.cs:
- IAddEquipmentUI.cs:
comment:17 Changed 9 years ago by
comment:18 Changed 9 years ago by
comment:19 Changed 9 years ago by
comment:20 Changed 9 years ago by
Version: | → Unknown or N/A |
---|
Add/Edit/Remove now implemented - just need "replace".
comment:21 Changed 9 years ago by
comment:26 Changed 9 years ago by
Resolution: | → fixed |
---|---|
Status: | confirmed → closed |
Closing ticket - Extra "TODO" task can be completed later.
Note: See
TracTickets for help on using
tickets.
Remove owner so that the team can more easily see bugs. Using default owners seems good at first but is bad practice when a team can be working on any part of the project.