wmayer wrote: ↑
Wed Feb 19, 2020 11:26 am
[*]In the list box I can select several elements but in the 3d view only one is highlighted
This is by design. I thought about it a lot and the dialog as it is, is the result of playing with it for hours with real-life documents.
I found out it is not helpful to highlight all object in the dialog list but only the one one clicked.
But of course, others might want to highlight all. I designed it so that the dialog selection is about their deletion.
[*]The multi-selection in the list box allows it to click on an item and move the mouse while keeping pressed the mouse button, i.e. I don't have to press Ctrl+mouse click.
As stated, the dialog selection is not about highlighting. Only one item is highlighted. The method you describe is however useful to select multiple items to delete them.
[*]Is there a reason why setSelection() is not connected to currentItemChanged() any more but itemClicked()? Before it was possible to select items with the arrow keys and now you must always use the mouse
With the current solution you can use the arrows to select.
At first I used currentItemChanged() but it annoyed me when playing with real-world files because of this issue:
- open an existing fillet with only one edge
- result: you cannot highlight the single edge because this would only be triggered if the selection is changed. But there is only one item.
Also entering selection mode and leaving it leads to this situation if no further object is added.
Therefore I experimented with itemClicked() and it suited me more. And again, the selection is not about highlighting.
[*]Currently the feature is recomputed each time an edge is being removed. And even worse: it's recomputed several time when removing several edges in one go.
See below, but of course if several objects are deleted, there should only be one computation.
[*]Is this intended behaviour to show the (recomputed) feature when removing an edge?
Yes, because i want to see it directly. In my work i have t deal with objects of several ten fillet edges and sometimes they are not compatible - OCC only does the right thing when I e.g. add one fillet set, then a second one and i need to find out what edges I can fillet at once and what not. By getting the immediate feedback I see what OCC can fillet and what not. So it is often a kind of try and error.