I've been trying to get a working copy of Scribus 1.3.9, and I've run into an issue where when I start ScribusPortableTest.exe, scribus.exe gets started like it should, but it doesn't do anything, other than use up my memory - taking it to 100% in no time. Here's my launcher.ini, properly named of course: http://pastebin.com/k3KQ3Zdu
If that isn't the issue, could someone take a look the package for me, and tell me if I'm doing something else wrong that's causing this?
http://sourceforge.net/projects/scribusportable/files/1.3.9/ScribusPorta...
MD5: 0bad6e8eb551297cf6e6a6f38cf09d15
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
How could it be PAL's fault? Whether it's normal Scribus behaviour or something in a feature of its not usually used but activated by something in the portable version, it's got to be in Scribus. PAL can't make another process guzzle memory.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
I didn't think it was PAL, but figured maybe I'd messed something up. I'll ask the Scribus devs, maybe they can help sort it out.
If you look at the post
https://portableapps.com/node/22525
You will see that the download link for 1.3.9 Development Test 1 is followed by
(Delayed while I try to fix a critical error in the launcher)
So the answer is, something's broken, and the developer is actively trying to fix it.
I made this half-pony, half-monkey monster to please you.
If you look at the post you'll see who the developer is.
Hmm.. I should get un touch with that developer.
That's what I get for posting without enough coffee!
I made this half-pony, half-monkey monster to please you.
*facepalm*
I've discovered that when I was running the app compactor, it was compacting the main executable, which caused it to stop functioning. I'll be posting a working package sometime before 2011.
You mean the launcher? Because it'll skip that if you select AppNamePortable as the main directory and it sees an App\AppInfo directory in it. If you mean of the app itself, that could be one of the the few EXEs that doesn't compact properly and still passes the UPX test. In that case, you can tell AppCompactor to exclude it in the PA.c settings so you don't have to worry about it specifically each time:
https://portableapps.com/development/portableapps.com_format#appcompactor
Sometimes, the impossible can become possible, if you're awesome!
It was compacting scribus.exe and still completing successfully. I've already made the appcompactor.ini, just need to upload a new package to sourceforge.