philipstarkey
commented
9 years ago Original comment by Philip Starkey (Bitbucket: pstarkey, GitHub: philipstarkey).
I would suggest that rather than displaying the hierarchy as a True tree, you "fake" the same format of tree by adding white-space indentation to the first column.
This has the following benefits:
- Reordering the list becomes easier. We already have code to do most of this (see downsides list below).
- You can use the child rows of an entry to display the global names that are part of the zip group
This has the following downsides:
- When re-ordering, you have to strip the whitespace from the first column and re-add it correctly for the two items which have swapped. This adds some complexity to the sorting algorithms we already employ.
I think that the first upside and downside probably cancel each other out in terms of coding complexity. So the net benefit is probably only a nicer way of displaying the names of globals in zip groups!
Original report (archived issue) by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
There is a half-written tab in runmanager labelled 'Axes', with a big blue Kronecker product icon on it.
This is a tab supposed to provide an overview of the currently described parameter space. It will have a nested treeview, with one entry for each axis being outer-producted, each as a child row of the one above it. This nesting, which will give each row indentation compared to the row above it, will reflect and dictate the order in which the axes are to be looped over while producing shots out of the parameter space. The order will be like that of a nested 'for' loop in code — the top level with the least indentation will be the one iterated over most slowly, and the bottom level iterated fastest.
Each axis will have a 'shuffle' checkbox for whether that axis is to have its order randomised. This makes the global shuffle button a little redundant, but I think we should leave it in as a global switch to flick all the checkbuttons on and off, and visually show it as ambiguous (in whatever the most standard way to do that on a pushbutton is, I'll have to look up - otherwise maybe stick an icon of a checkbox on it showing the ambiguous state) if there is a mix of shuffle states on the axes.
An axis might be an outer-producted global, or a zip group. In the latter case the name of the zip group will be shown instead of the name of the globals therein, though perhaps we could show the globals too at an equal level of the heirarchy. But if that's hard, I'll put it in a tooltip instead.
The loop order will be reorderable via buttons on the side that move an item up or down, or possibly by drag and drop if it's easy enough to do.