nothing working after updating to 0.2

[JVanBuskirk]

Hello,
I just updated to 0.2 using atom 0.124 on OSX 10.8.5. Everything was working well using atom-supercollider 0.13.

I also installed supercolliderjs globally since the last time I used atom-supercollider. I don't know if this makes a difference.

I love the work you are doing. Thank you!

[JVanBuskirk]

Here is the output from the console.

Failed to activate package named 'supercollider' TypeError: Cannot read property 'path' of null
at new Controller (/Users/jeremy/.atom/packages/supercollider/lib/controller.coffee:11:29)
at Object.module.exports.activate (/Users/jeremy/.atom/packages/supercollider/lib/supercollider.coffee:9:23)
at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app/src/package.js:163:27)
at Package.module.exports.Package.handleActivationEvent (/Applications/Atom.app/Contents/Resources/app/src/package.js:551:12)
at HTMLDivElement. (/Applications/Atom.app/Contents/Resources/app/src/package.js:3:61)
at HTMLDivElement.jQuery.event.dispatch (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:4676:9)
at HTMLDivElement.elemData.handle (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:4360:46)
at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app/node_modules/atom-keymap/lib/keymap-manager.js:399:16)
at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app/node_modules/atom-keymap/lib/keymap-manager.js:180:22)
at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:146:20)

[crucialfelix]

Hi, I think this means that atom.projectRootDirectory returned null. Maybe you have to open and save a project. In any case it shouldn't break. I'll try to replicate it. Thanks !

[JVanBuskirk]

The error message I sent before shows when I try to save a project.

When I open a .scd file and then try to open a post window, a slightly different error message occurs.

Failed to activate package named 'supercollider' TypeError: Cannot read property 'path' of null
at new Controller (/Users/jeremy/.atom/packages/supercollider/lib/controller.coffee:11:29)
at Object.module.exports.activate (/Users/jeremy/.atom/packages/supercollider/lib/supercollider.coffee:9:23)
at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app/src/package.js:163:27)
at Package.module.exports.Package.handleActivationEvent (/Applications/Atom.app/Contents/Resources/app/src/package.js:551:12)
at HTMLDivElement. (/Applications/Atom.app/Contents/Resources/app/src/package.js:3:61)
at HTMLDivElement.jQuery.event.dispatch (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:4676:9)
at HTMLDivElement.elemData.handle (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:4360:46)
at Object.jQuery.event.trigger (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:4594:12)
at HTMLDivElement. (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:5119:17)
at Function.jQuery.extend.each (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:590:23)
at [object Object].jQuery.fn.jQuery.each (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:237:17)
at [object Object].jQuery.fn.extend.trigger (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:5118:15)
at Ipc. (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:32:50)
at Ipc.EventEmitter.emit (events.js:107:17)
at process. (/Applications/Atom.app/Contents/Resources/atom/renderer/api/lib/ipc.js:20:29)
at process.EventEmitter.emit (events.js:110:17)

[crucialfelix]

the second error post is actually the same bug as the first, it just starts at a different place. ends up in the same bug.

fixed, you can update now