Summary:
I clicked on a migrant that I had just accepted, and got the following error. Steps to reproduce:
Accept a new migrant
Click on migrant in the main window (not the civilians menu)
Expected Results:
Information on the migrant appears in the bottom left
Actual Results:
Error report
Notes:
develop-3362 (x64)
Uncaught Error: Computed Property declared without a property function
Error: Computed Property declared without a property function
at r (radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:4:18375)
at m (radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:4:9901)
at Object.l.property (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:8:6340)
at c (radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.min.js:4:26036)
at Object.fireWith [as resolveWith] radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.min.js:4:26840)
at k (radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.min.js:6:14258)
at XMLHttpRequest.r (radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.min.js:6:18646)
Had to remove http:// from every “link” in the error as otherwise it wouldn’t let me post
Version Number and Mods in use:
Develop-3362 (x64) System Information:
windows 7
Can you show us a screenshot of what you’re seeing? A save would be helpful. You can use google drive or dropbox to upload the file and then paste a public / shareable link here.
savegame is here. I believe it’s from after the error.
I’ve unfortunately not been able to get a screenshot as I’ve not been able to replicate the error. It was an error code that showed up in one of the “close permanently/continue” error boxes that’s in the game, so was a caught exception rather than an uncaught return straight to windows exception.
Summary:
The “Saving…” does not disappear after saving manually. Here’s the error log that appeared before I saved manually, while viewing the crafting queue:
release-707 (x64)[M]
Uncaught Error: Computed Property declared without a property function
Error: Computed Property declared without a property function
at r (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:4:18375)
at m (http://radiant/stonehearth/ui/root/js/libs/ember-1.8.1.min.js:4:9901)
at Object.l.property (http://radiant/stonehearth/ui/root/js/libs/ ember-1.8.1.min.js:8:6340)
at c (http://radiant/stonehearth/ui/root/js/libs/jquery-1.10.2.min.js:4:26036)
at Object.add [as progress] (http://radiant/stonehearth/ui/root/js/libs/ jquery-1.10.2.min.js:4:26346)
at String.<anonymous> (http://radiant/radiant/js/radiant/trace.js:318:20)
at Function.each (http://radiant/stonehearth/ui/root/js/libs/ jquery-1.10.2.min.js:4:5347)
at SimpleClass._expand_array_properties (http://radiant/radiant/js/radiant/ trace.js:301:12)
at SimpleClass._expand_object (http://radiant/radiant/js/radiant/ trace.js:138:25)
at Array.<anonymous> (http://radiant/radiant/js/radiant/trace.js:255:24)
Open Wood crafting queue with more than 1 worker active
Wait for a worker to complete an item
Save the game manually
Expected Results:
The game remains playable and UI elements can still be clicked.
Actual Results:
The main menu can still be opened, but clicking elements yields no results.
The bottom toolbar cannot be clicked. Also, no elements in the world can be clicked - they still light up, though.
Restarting the game works fine. The loading screen appears and no data is lost.
Notes:
As previously stated, I am using a Terrain colour mod. Other than that, I also imported quite a few builds and removed the item limit and upped the population limit.
Also, it seems like this person got the exact same exception string.
This type of error usually appears at the right side of the screen, and can be fixed by pressing F5 (it is recommended to do so to avoid other parts of the UI breaking too. I think we need to increase the font size for that tip, which appears at the bottom of the error window).
Unfortunately, these errors are hard to reproduce. So thanks for the steps and for the savefile, this seems to be a different way to get the error.
It’s hard to tell where it originated from since the only file that’s ours is that object.js, which is a generic library so it could have been triggered by any UI view
