Changing object to Score with Frosted Acrylic locks all future changes

Community Support
1
  1. Insert sheet of Frosted Acrylic, open app.glowforge.com
  2. Load any svg with any number of objects
  3. Select any object and choose Convert to Score
  4. Attempt to click that object in the sidebar again

Result: Object is “locked,” no longer pops a menu. Other objects are fine, can be switched between Cut and Engrave, as long as you don’t choose Score.

Note that when you do choose Score the first time, the menu is incorrect, but you’ll only get to see it once. :wink:

18 PM
Screen Shot 2017-11-29 at 8.15.18 PM.png836×338 35.9 KB

And get this: it only seems to happen with Frosted Acrylic so far. If you insert Draftboard, no repro. If you insert Draftboard and manually choose Frosted Acrylic, it will repro.

This happens on complex and simple files, and has been a 100% repro since last night, but pretty sure it was OK on Monday evening.

Chrome and Safari react exactly the same way.

Have fun with that one!

EDIT: And it gets better! If you get “locked up” you can manually select Clear Acrylic and regain full control. Once you switch back to Frosted, though, it’ll lock you out again.

11 Likes
2

I was able to replicate with Chrome on Ubuntu.

2 Likes
3

Wow, this one is strange. Thanks for taking the time to capture a detailed set of steps to repro.

I really wish GF would just open their bug database so we could file bugs directly,

3 Likes
4

Just tried it as well. They already had some scores in the part, and they are locked out. I didn’t do anything to it. If I change something else to a score, it locks out as well. That’s a weird one.

image
image948×527 166 KB

4 Likes
5

Nice detective work! :+1:

2 Likes
6

Any way out? reload the page? back to the design catalog?

7

You can always reload, delete that object, or manually choose a different material type.

But it seems that Scores on Frosted Acrylic are just busted.

8

Oopsies.

Uncaught TypeError: Cannot read property 'getHostNode' of null
        at Object.getHostNode (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at u.getHostNode (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at Object.getHostNode (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at Object.updateChildren (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at ReactDOMComponent._reconcilerUpdateChildren (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at ReactDOMComponent._updateChildren (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at ReactDOMComponent.updateChildren (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at ReactDOMComponent._updateDOMChildren (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at ReactDOMComponent.updateComponent (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at ReactDOMComponent.receiveComponent (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at Object.receiveComponent (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at Object.updateChildren (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at ReactDOMComponent._reconcilerUpdateChildren (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at ReactDOMComponent._updateChildren (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at ReactDOMComponent.updateChildren (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)
        at ReactDOMComponent._updateDOMChildren (vendor.bundle-7e98ec096ef965f41df0c9ce05763c69ef1bb1fc0dd211556b29d72cf3c86dc4.js:1)

Pretty obviously because /api/materials contains “score_settings: []” for Medium Frosted Acrylic.

4 Likes
9

Oh, that’s so good. :slight_smile:

10

Thanks for letting me know about this and for writing this thorough report!

I’m looking into it.

1 Like
11

Thanks for your patience. Would you try again and see if it works now?

12

Looks good to me!

13

Great! Thanks for checking.

If you have any other questions or feedback, please post a new topic or email us at support@glowforge.com.