# Bugginess after update

**URL:** <https://discourse.shapr3d.com/t/bugginess-after-update/31183>\
**Category:** Modeling Questions\
**Created:** [April 7, 2024, 12:03pm UTC](https://discourse.shapr3d.com/t/bugginess-after-update/31183 "2024-04-07T12:03:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Xdrakosha](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.shapr3d.com/xdrakosha/32/24881_2.png) [@Xdrakosha](https://discourse.shapr3d.com/u/Xdrakosha)\
**Post date:** [April 7, 2024, 12:34pm UTC](https://discourse.shapr3d.com/t/bugginess-after-update/31183/2 "2024-04-07T12:34:01Z")

</div>

> [@dmf92](#):
>
> Also, one thing seems permanent and so maybe a feature and not a bug, but clearly worse than before imo: when I select e.g. a face, and the number comes up representing thickness or whatever parameter, despite the number being highlighted, I can’t just quickly type in a new number as before. Instead, I have to physically click the number every time and only then can I change the number. So the workflow became less seamless than before, with additional steps.

> [@Keyboard UX changes](https://discourse.shapr3d.com/t/keyboard-ux-changes/30691):
>
> Hi community, just a quick heads up before the next release, that comes with a UX change that probably some of you will find annoying first, as it is breaking your muscle memory. Paving the way to introduce variables, in our most recent release we made a number of subtle changes around keyboard interaction, more specifically around how input focus is handled. You might not even notice some of them, but others might require you to slightly alter your workflow. We understand that re-learning flow…

---

_[View the full topic](https://discourse.shapr3d.com/t/bugginess-after-update/31183)._