NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 392 - Project property "number of threads for mipmaps generation" is lost on re-open save
Project property "number of threads for mipmaps generation" is lost on re-ope...
Status: RESOLVED FIXED
Product: Fiji
Classification: Unclassified
Component: TrakEM2
unspecified
PC Linux
: P2 normal
Assigned To: Albert Cardona
Depends on:
Blocks:
 
Reported: 2012-01-06 21:24 CST by Stephan Saalfeld
Modified: 2012-01-07 15:46 CST
0 users

See Also:

Description Stephan Saalfeld 2012-01-06 21:24:49 CST
The project property "number of threads for mipmap generation" can be set through the respective dialog.  It is saved correctly after setting it in the dialog and re-saved on every successive save.  When opening a project with this property set, it is opened correctly and the number of threads is set correctly. BUT!! The dialog shows the property being 1 (which is the default and wrong here) and on saving the project, the property is lost.  That project re-opened will use only one thread for mipmap generation.  The bug can most likely be fixed by setting the property during opening the project and not only create the correct number of threads.
Comment 1 Stephan Saalfeld 2012-01-06 22:08:38 CST
Pushed a fix to FSLoader, the property needs to remain in the attributes table to be later inserted as a project property.  AlbertpPlease check if this has unexpected side conditions.
Comment 2 Albert Cardona 2012-01-07 15:46:01 CST
(In reply to comment #1)
> Pushed a fix to FSLoader, the property needs to remain in the attributes table
> to be later inserted as a project property.  AlbertpPlease check if this has
> unexpected side conditions.


Looks fine to me, thanks for the fix. It's already in the updater.