Skip to content

Commit 45ceab4

Browse files
committed
Release notes for v1.0.6.
Also added in some comments to main.js and DetectorEdit.cpp for future work. Added in Wt::WString default encoding to be UTF-8 for macOS (not doing this before was an oversight).
1 parent 357d60e commit 45ceab4

File tree

4 files changed

+28
-10
lines changed

4 files changed

+28
-10
lines changed

docs/releases/index.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,24 @@
1+
## v1.0.6 (November 4, 2019)
2+
This release is mostly stability improvements, small UX improvements, and bug fixes.
3+
Download Windows, Linux, and macOS binaries from: [https://github.com/sandialabs/InterSpec/releases/tag/v1.0.6](https://github.com/sandialabs/InterSpec/releases/tag/v1.0.6)
4+
5+
* Improvements and fixes:
6+
- For Windows and Linux made running application more robust by compiling the InterSpec C++ code to a node.js module, rather than a separate executable that had to be run by, and communicate with node.js.
7+
- Updated to using [Electron](https://electronjs.org/) v7.0.1.
8+
- Fixed a few potential JS issues when starting up that could prevent app from fully loading.
9+
- Added checking for a file 'do_restore' in the applications OS-provided data directory; if it exists, it will be deleted, and `InterSpec` will try to load were you left off in your last session. When the app successfully fully loads, the file will be written again. If the file doesnt exist when the application is started, the previous app state will not be restored.
10+
- On the "Peak Manager" tab you can export the currently fit peaks as a CSV file. Now, if you open up a different spectrum file, you can drag the previously exported CSV file onto the app, and the peaks defined in that file will be fit for. Additionally there is a new options (Help -> Options-> Ask to Propagate Peaks) you can enable so that when you load a new spectrum from the same detector as your current one, peaks will be propagated (and re-fit) from the old spectrum to the new one. In both cases a dialog showing the newly fit peaks will be presented to the user so they can select which peaks to keep. These feature are useful if you frequently deal with spectra from the same detector with similar isotopes.
11+
- Improved suggesting peak assignments for single and double escape peaks from the right-click "Change Nuclide" sub-menu. Further improvements are expected in the future.
12+
- Fix potential issue if google maps widget was shown more than once in a session.
13+
- Fix a few issues assigning x-rays or reactions to peaks.
14+
- Increase peak label sizes.
15+
- Added a "Feature Marker" widget that allows easier, and more complete, selecting to show escape peak lines, Compton Edge, Compton Scatter and sum-peaks.
16+
- Fix a few more instances of trouble loading files when there name/path contained some non-ASCII characters.
17+
- Many smaller fixes and improvements.
18+
- Added some less-common spectrum file formats and N42 variants.
19+
20+
21+
122
## v1.0.5 (August 23, 2019)
223
This release is mostly small bug fixes, improvements, and the addition of the **Flux Tool**.
324
Download Windows, Linux, and macOS binaries from: [https://github.com/sandialabs/InterSpec/releases/tag/v1.0.5](https://github.com/sandialabs/InterSpec/releases/tag/v1.0.5)

src/DetectorEdit.cpp

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1131,7 +1131,7 @@ GadrasDirectory::GadrasDirectory( std::string directory, GadrasDetSelect *parent
11311131
m_deleteBtn->clicked().connect( boost::bind( &GadrasDetSelect::removeDirectory, parentSelect, this ) );
11321132

11331133

1134-
//If we wanted to actually select directories, could do similar to file query widget...
1134+
//If we wanted to actually select directories, could do similar to file query widget... which webkitdirectory no longer seems to work, so see file query widget use of electrons dialog
11351135
//#if( BUILD_AS_ELECTRON_APP )
11361136
// m_pathSelectedSignal.reset( new Wt::JSignal<std::string>( this, "BaseDirSelected", false ) );
11371137
// const string uploadname = id() + "PathPicker";

target/electron/app/main.js

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -23,17 +23,9 @@
2323

2424
/* ToDo list (partial):
2525
- Finish setting up launch_options.json (see get_launch_options())
26-
- Setup building/packaging Electron app as a single, or easy set of commands.
27-
- Test out opening files (macOS and Windows; somewhat works on mac)
28-
- Setup, or figure out, signing app on Windows and macOS
29-
- On mac you can 'codesign-electron.sh InterSpec.app' to sign
30-
- Handle errors in c++ by sending through IPC socket once its open
26+
- Setup, or figure out, signing app on Windows
3127
- Handle fatal errors with dialog.showErrorBox(...)
3228
- Catch 'IntializeError' in stderr during startup, and handle
33-
- Catch death in C++ code and display an error
34-
- Could probably setup general error displaying mechanism of looking if
35-
there is a window showing loading.html, and if so, display there, and
36-
if not create a dialog. Needs more thought.
3729
- Look at creating a backup preferences file, and if the C++ fails to start
3830
2 or 3 times, go back to the previous preferences file (should be done for
3931
all targets maybe).

target/osx/AppDelegate.mm

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,8 @@
4141
#undef require
4242
#endif
4343

44+
#include <Wt/WString>
45+
4446
#include "InterSpec/InterSpec.h"
4547
#include "InterSpec/InterSpecApp.h"
4648
#include "InterSpec/InterSpecServer.h"
@@ -244,6 +246,9 @@ - (void)applicationDidFinishLaunching:(NSNotification *)aNotification
244246
{
245247
NSLog(@"Finished Launching");
246248

249+
250+
Wt::WString::setDefaultEncoding( Wt::UTF8 );
251+
247252
/*
248253
//Could maybe get rid of using XIB/NIB by manueally creating a window like:
249254
NSRect frame = NSMakeRect(0, 0, 300, 300);

0 commit comments

Comments
 (0)