Hello,
i'm on windows and trying to use FastStoneViewer as the image editor in Scribus.
Both apps are placed into d:\dtp-scribus.
I have a ScribusPortableTest.ini file in the same folder as ScribusPortableTest.exe.
I have added the line UseCustomImageEditor=fsv to the .ini file which should tell the application to use FSViewerPortable instead of the hardcoded GIMPPortable.
This does not work. Scribus still uses GIMPPortable. Do i have to put the user command into another .ini?
Regards.
Do you have the paths as d:\dtp-scribus\ScribusPortableTest (with your Scribus Portable install there) and d:\dtp-scribus\FSViewerPortable (with your FSView Portable install there)? If you alter the directory names it will not work. I have not tested this feature which is only in the test release of Scribus myself yet.
Sometimes, the impossible can become possible, if you're awesome!
Yes, this are the paths where i have both apps installed. I have not changed the names of the apps folders.
I can confirm that this feature does not yet work. The custom code is setting it to FSViewer but then the launcher sets it right back due to the FileWrite1 entry in ScribusPortableTest.ini.
I think I may have this simply default to GIMP and then adjust the paths, alleviating the need for this custom code for a future release.
As a workaround for now, open up the file ScribusPortableTest.ini within the ScribusPortableTest\App\AppInfo\Launcher directory. Adjust the Value entry within FileWrite1 (line 36) to read:
That will let you use FSView for now.
Sometimes, the impossible can become possible, if you're awesome!
This works fine. Thanks.
Is there a chance to see a ScribusPortableTest 1.5.7 soon?
Regards
This is fixed in Scribus Portable Test 1.5.7. You can now select any image editor you'd like within Scribus itself and it will be remembered and the path adjusted. GIMP Portable will be set by default.
Sometimes, the impossible can become possible, if you're awesome!
With today's Scribus 1.6.1 releases, this is now fixed in Stable as well as Test. It's also fixed in the LegacyWinXP build.
Sometimes, the impossible can become possible, if you're awesome!