Batch Rendering Inefficiencies with 2.7

Please cast your votes in our two ongoing feedback polls here and here!
    Quote from Christian Radowski

    I can add this to our internal UX bug backlog but tbh. I personally disagree with point 3 because that toggle button follows all usual conventions.

    I agree that point 3 is very much subject to debate. To make my critique a bit more specific: I feel the slider is not very discoverable. If you look at it you have no idea what it does. You need to hover over it to see what it does. I think the design could have been more self explanatory. On the other hand, the other items I listed I consider more higher priority (especially the "report the view enscape is linked to" because that's a real pain atm).

    Quote from Christian Radowski

    Update: This issue just shows up more using linked projects it likely already exists for single projects as well but is less visible. Anyhow we are looking into a fix for this right now. We'll try to include this within a service pack of some sort for 3.2

    Thanks for jumping on this, much appreciated!

    Quote from Christian Radowski

    Update: This issue just shows up more using linked projects it likely already exists for single projects as well but is less visible. Anyhow we are looking into a fix for this right now. We'll try to include this within a service pack of some sort for 3.2

    Thanks for looking into this Christian! This has been a feature we’ve been looking forward to. let me know if I could be of any further help!

    Quote from Phil Read

    Agree with @Pieter. Enlarge the slider icon. IMO Get rid of the other icon.

    I won't really engage in a design discussion about these items in this thread guys ;) a different can of worms and tbh. and as Pieter also already said "highly subjective" changing UI with this resolution (on this micro layer I mean) is best done using quantitative analysis. Don't worry we have filed this feedback and have received Phil's feedback regarding this several times already.


    Bottom line for the actual topic of this thread: I'll let you know here once I have an ETA sorry for the wait :)

    Quote from Pieter

    I agree that point 3 is very much subject to debate. To make my critique a bit more specific: I feel the slider is not very discoverable. If you look at it you have no idea what it does. You need to hover over it to see what it does. I think the design could have been more self explanatory. On the other hand, the other items I listed I consider more higher priority (especially the "report the view enscape is linked to" because that's a real pain atm).

    Thanks for jumping on this, much appreciated!

    I also think the tooltip is confusing:


    Usually a tooltip explains was a slider does when turned ON. But in this case the tooltip ("deactivate the geometry export when switching views") describes what the slider does when turned OFF, which I find confusing to be honest. I think this would to give it a permanent label (always visible, not just in the tooltip) : "geometry export", and then have the tooltip describe what it does when it's turned on.


    And as a bonus: show the geometry view when "reload geometry" is turned off. There should be room enough to the right slide of the slider to fit it.

    Quote from Christian Radowski

    I won't really engage in a design discussion about these items in this thread guys ;)

    Sorry posted my previous message before I saw your last reply. I'm always happy to provide more detailed feedback outside this thread. I think a tiny bit of polish could go a long way here ;)

    Quote from Phil Read

    IMO "deactivate the geometry export when switching views" is technically correct but specific to the point of confusion.


    "Refresh View (On/Off)" is brief and clear.

    Quote from Pieter

    Agreed

    Again guys this is not the right place for this discussion and the proposed tooltip is completely missing the mark of what actually happens.

    Quote from Pieter

    Where is a better place to discuss this?

    You can send me a detailed list of ideas via PM and I will gladly pin them to the UX bug I will create for this topic. There is no guarantee that this will be exactly the final outcome of us iterating the UI, which in turn is not currently planned either due to the team working on different things but at least your thoughts and ideas don't get lost that way :)