New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arch_Schedule Objects column should work with labels instead of internal names #13787
Comments
Labels need not be unique which makes implementing this a little more complex than you may think. |
Note that it's already possible to do that with filters. You leave the Name column blank (all objects), and you add a filter such as Label:MyName Maybe actually we should remove the "Name" column. And have a kind of "filter editor" dialog to help people to create complex filters |
Thank you. I added a note with that workaround at https://wiki.freecad.org/Arch_Schedule.
Regarding removing the "Objects" column (I believe that's what you meant), I think it's still useful to have it, as it allows quickly selecting an object and adding it there with "Add selection". Unless the "filter editor" idea would provide an easy way to replicate this functionality (i.e. "Add selection" would by default add "Label:MyName").
I had not thought of that, good point. However, after having tried the setting of not requiring unique names, the amount of things that broke in different places (sorry for the vague statement, as I did not manage to file issues for all) made me go back to unique labels. That is, I feel other things would break earlier before breaking Arch_Schedule :-) |
Also when using the filters, the selection is very greedy (it matches part of names too). So in that case, the possibility to have several objects with a same label is not really a problem. Same for the Objects column, the only result would be that there are several objects selected. |
Is there an existing issue for this?
Problem description
On the Arch_Schedule command, the "Objects" column works with internal names of objects only. For better usability, it should work with labels instead (or in addition to).
Full version info
Subproject(s) affected?
Arch
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: