WIP to address issue 153 and sketching out some ideas #791
Conversation
|
CLA Assistant Lite bot: I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request |
antonszilasi
changed the title
Importing design days appears to be working
|
|
||
| // Evan note: do not remove existing design days | ||
| //for (model::SizingPeriod sizingPeriod : m_model.getModelObjects<model::SizingPeriod>()){ | ||
| // sizingPeriod.remove(); | ||
| //} | ||
|
|
||
| //m_model.insertObjects(ddyModel.objects()); | ||
| designDaysToInsert = showDesignDaySelectionDialog(summerdays99, summerdays99_6, summerdays2, summerdays1, summerdays0_4, winterDays99, winterDays99_6, winterDays2, winterDays1, winterDays0_4,allNonAnnual); |
There was a problem hiding this comment.
I would pass all the design days in in a single vector. Then the widget could do all the sorting, doing all this pre-sorting up front is kind of messy.
|
Thanks @antonszilasi! I think the first thing to do is to create a mockup of the UI that we want to make, the unmethours post suggested this from Trace:
Once we have the mockup, we can create the widget to match it. |
|
What about something like below:
We would look through the file and identify all the design day types and levels, then group them in a table. Each row would allow selecting one radio button. Each column would have a select all button to select all in that column |
|
@macumber thanks for the feedback, I need to work on the presentation but I think this will do in terms of functionality I just want to keep it basic with not too many bells and whistles we can expand on it later if other users request it
|
WIP to address issue 153 and sketching out some ideas