Idea generation 2023 - Part 1

[david.welts]

Hello all,
As part of our idea and feedback generation for 2023, I would like to ask you all a “funny” but important question:

If you could get rid of one (or more) feature in Solibri, what would it be and why?

[dph]

I would have removed the X-button for close classification! or atlest made an “are you really really really sure” that you wanna close this classification?

[david.welts]

@dph
Are you referring to this one:

Is the problem that you click it accidentally when trying to click “add classification”, or is it something else?

[JSN]

@david-polanski said in Idea generation 2023 - Part 1:

Is the problem that you click it accidentally when trying to click “add classification”, or is it something else?

And don’t forget the context menu … it’s too damnclose to the settings option. Although adding a warning might be the more purposeful solution.

https://society.solibri.com/topic/2067/prevent-accidental-closing-of-classifications-and-stop-collapsing-folders

Besides that I would like to get rid of the “Update your software now” button if you are already on the latest built anyhow.

[Ricardo]

Hi David,

One of the ‘features’ that I would like to get rid of is the following: columns where I have adjusted the with, will automatically change back to their original width after I click on something else.

As an example, in the picture below not all of the text is visible on the right, while there is a lot of empty space on the right. This is something that I experience daily, and results in me adjusting the colums a lot of the times.

(link to the original FR; https://society.solibri.com/topic/711/width-adjusted-columns-should-retain-their-position-after-selecting-new-elements )

[Alex.J]

Hi @david-polanski and everyone and best of wishes to the Solibri Team and the Solibi Community.

One feature I can think of right now is the automatic update of classifications on model load (opening SMC file or updating IFC). I’d sometimes rather have them updated when the classification is called (by itself through the UI or by a rule or an ITO), since this can slow down the update a lot even though it is not necessarily needed. Same goes for the footprints.

Another feature that I never managed to use correctly is the Compartmentation, although I quite like the idea (I usually use normal classifications instead).
I’d be interested if someone makes good use of it.

I also think that everything related to the result/issue/slide/BCF management should be streamlined (many features are kind of duplicated but still work quite differently, which makes it hard to find an optimized workflow, as addressed in multiple other posts)