This seems to be an issue in the way Safari handles webworkers and is nearly impossible to debug because of how Safari treats them (breakpoints, console.log, etc. do not work in webworkers).

Options: revert to old version of webworker.js or ignore support for Safari until its treatment of webworkers is more sane.

@Roceso1337

we should be caching things, not sure when this broke.

Glyphicons also don't render except during the short period of time when everything appears correct, after clicking a button, moving slider, etc.

So far, this appears to potentially be a Mac-only issue, although Firefox on Mac does not show signs of this issue.

Commenting out this line in base.scss seems to fix the font issue as well, but doesn't affect the glyphicons.

If we switch primary application endpoint to / or /stepnc , and load the file we serve from a command line argument, we can remove the Backbone.js dependency, as well as simplify the serving.

This causes the boundingbox to be rendered incorrectly, and may cause excessive memory use.

Side bar workingsteps that have a name that goes onto a second line should have their second and subsequent lines indented the same as the first line.

Currently outdated and not effective way to onboard people.

How to reproduce:
have two models named model.stpnc with different project names
load one project
load the other project
get an error

This might be a lower level problem

After downloading the StepNCViewer I tried to set it up like described at the readme file. But I always receive following massage from the tool when landing on the Frontend:

[email protected] start-dev /root/cad.js
node src/server/api_server.js -e development

info: CAD.js API Server listening on: 8080
info: Redis Connected.
info: Configuring auth/auth plugin: permit
info: Setting User-Validation function
info: Setting User-Authorization function
info: Configuring storage plugin: filesystem
info: Assembly Root: /root/cad.js/data
info: NC Root: /root/cad.js/data
GET /cad.js?resource_url=/data/cutter/index.xml 304 - - 101.958 ms
GET /js/main.css 304 - - 47.866 ms
GET /js/main.js 304 - - 72.403 ms

and then finish. The tool is not showing anything on 127.0.0.1:8080..
Is there a bug or am I doing something wrong?

To recreate, start the server and attempt to load a project that doesn't exist:
Messages:

GET /stepnc/asdf 304 - - 125.858 ms
This project doesn't exist
Finder: no file open
GET /v2/nc/projects/asdf/workplan/ 500 1259 - 10.850 ms
TypeError: Cannot read property 'map' of undefined
    at exeFromId (/Users/ianchamberlain/step/StepNCViewer/src/server/api/v2/step.js:19:54)
    at _getMwp (/Users/ianchamberlain/step/StepNCViewer/src/server/api/v2/step.js:38:24)
    at Layer.handle [as handle_request] (/Users/ianchamberlain/step/StepNCViewer/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/ianchamberlain/step/StepNCViewer/node_modules/express/lib/router/route.js:131:13)
    at Route.dispatch (/Users/ianchamberlain/step/StepNCViewer/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/Users/ianchamberlain/step/StepNCViewer/node_modules/express/lib/router/layer.js:95:5)
    at /Users/ianchamberlain/step/StepNCViewer/node_modules/express/lib/router/index.js:277:22
    at param (/Users/ianchamberlain/step/StepNCViewer/node_modules/express/lib/router/index.js:349:14)
    at param (/Users/ianchamberlain/step/StepNCViewer/node_modules/express/lib/router/index.js:365:14)
    at Function.process_params (/Users/ianchamberlain/step/StepNCViewer/node_modules/express/lib/router/index.js:410:3)
GET /v2/nc/projects/asdf/state/loop/ 304 - - 2.261 ms
Assertion failed: (val->IsString() == true), function Write, file ../src/string_bytes.cc, line 358.
This project doesn't exist

Process finished with exit code 134

I'm guessing this has something to do with the fix for #18 @funnymanpatrick

In the Edge browser, the slider spacing so the buttons below the slider are positioned incorrectly.

@williamgrh

-t option

The extra spacing on the left of the first child makes it look a little off. Also, the border that appears when hovering over the button is cut off on the left.

Refers to the folders within the data folder but pull request #109 might have made this less prevalent

Needs to scale to model or view

prolly should move to a newer version of most packages

@funnymanpatrick @UuqV @sam-son
The tool will sometimes re-position itself but the conditions are not consistent or immediately obvious.

Who knows why.

There are no scrollbars and the mouse wheel appears to do nothing

When the server first spins up, the first workingstep is the current workingstep. When the client loads the server, the sidebar scrolls and the workingstep is cutoff. This isn't an issue for other workingsteps, just the first one.

Main piece of the puzzle for v1.2

Releases need to be shrunk to facilitate mobile connections etc

Always have to go into task mangler to kill the process...

To see this, begin with a full-sized desktop window, then resize until the view is narrow enough to switch to a mobile view. Then, resize back to full size – the CAD.js area will typically (in my case) stop expanding right at some point, leaving a white bar on the far right side of the screen.

When a client first loads up the server, if it is on a workingstep below the initial scroll point, the sidebar should scroll so that it is in view.

We always have to kill process, which usually causes it to hang, which means finding it in the task mangler.... Really need to add proper server exit ability.

works fine in mobile view

@ian-h-chamberlain

We always have to kill process, which usually causes it to hang, which means finding it in the task mangler.... Really need to add proper server exit ability.

Possibly related to #51 but it doesn't seem like the issue is the same

when you play a project it stops the other projects without updating the play/pause button to reflect that it's paused. then if you pause and play another project, pausing the original project that was stopped will update a playing project to display the play button.

WTF, SAM?!?!?