Thanks for your response srvaldez, it turned out to be downloading the wrong iup version.
The instructions in the manual.pdf are a bit vague there.
Anyhow up and running.
Regards
(1) You can try poseidonFB_x64_revXXX.AppImage, no need install IUP
(2) The #1 post in this thread, I'll show what version of IUP using in new poseidonFB
I have written a small application which changes the compiler paths programmatically but must be run before poseidonFB is opened. If poseidonFB read the compiler paths before each compilation then I could add my little application as a tool allowing us to change compiler paths 'on the fly'. There is currently some interest in having more than one compiler build and being able to switch between them without closing poseidonFB will increase poseidonFB's power.
I have written a small application which changes the compiler paths programmatically but must be run before poseidonFB is opened. If poseidonFB read the compiler paths before each compilation then I could add my little application as a tool allowing us to change compiler paths 'on the fly'. There is currently some interest in having more than one compiler build and being able to switch between them without closing poseidonFB will increase poseidonFB's power.
Would you consider this?
OK, but I think we can do it by another method.
I'll expand the poseidonFB plugin command to change the 32bits/64bits FBC paths directly, and I think it's not too difficult to code a plugin that can select the different versions of FBC
This weekend......
deltarho[1859] wrote:It will be interesting to see what you come up with.
Try to this one( include dll and source ) http://www.mediafire.com/file/pq37qw7k8 ... in.7z/file
(1)Download cPathPlugin.7z and extract
(2)poseidonFB -> Options -> Tools -> Set Custom Tools..., create a new one tool( name and set the dll fullpath )
(3)poseidonFB -> Options -> Tools -> click new tool
Add: Create a new item( include name and the paths )
Del: Delete a selected item
Edit: Edit an existed item
Apply: Change the FBC path!
Note:
(1)The cPath.ini is put in settings\ dir
(2)Open Preference dialog and click new plugin "Apply" button, check how works
(3)The changes in new plugin will be saved while poseidonFB closing
Last edited by Kuan Hsu on Sep 08, 2019 6:18, edited 1 time in total.
The main difference between your method and my method is that you build the ini file for us which some users may prefer.
The important thing is the ability to change compiler paths 'on the fly' and, on testing, your method does just that.
In the future FB may be including several builds in its package and poseidonFB is now prepared for that. There are some folk who have several builds now so poseidonFB V0.421 will be a welcome version for them.
Thank you for this update.
Added: Instead of calling the tool 'cPath' I would suggest 'Set compiler paths'.
Yours truly wrote:Added: Instead of calling the tool 'cPath' I would suggest 'Set compiler paths'.
To that end I removed 'cPath' from 'Set Custom Tools...' but found cPath.ini still existed so I killed that.
I then started from scratch to use 'Set compiler paths' as the tool name.
All seemed well but on clicking on the tool, now called 'Set compiler paths', the window title was still 'cPath' and cPath.ini was created so cPath had not been removed in its entirety.
Yours truly wrote:Added: Instead of calling the tool 'cPath' I would suggest 'Set compiler paths'.
To that end I removed 'cPath' from 'Set Custom Tools...' but found cPath.ini still existed so I killed that.
I then started from scratch to use 'Set compiler paths' as the tool name.
All seemed well but on clicking on the tool, now called 'Set compiler paths', the window title was still 'cPath' and cPath.ini was created so cPath had not been removed in its entirety.
(1)Change window title need modify the source and re-compile the dll (2)poseidonFb read editorSettings.ini first, while poseidonFB closing, poseidonFB save editorSettings.ini then save the cPath.ini, so we can save the cPath.ini settings into editorSettings.ini by modifiy source code
Last edited by Kuan Hsu on Sep 08, 2019 6:07, edited 1 time in total.
When using the .AppImage to run Poseidon in Linux 19.2. WHERE does the "editorsettings.ini" hide out ??
A search does not find it.
The reason is that I have a lot of Keywords that I want to use and want to copy from another installation.
Regards
EDIT: Found it in home/username/.poseidon/settings
Another issue I have been struggling with for a few days.
Until now I have used Linux Mint 18.3
Making a backup of my new laptop which is Mint 19.2 on a mSata usb drive.
Used the bitbucket download of Poseidon.AppImage V0.420 which is the same version as my Mint 18.3
The Run button appears to do nothing.
It does not open a Terminal , even though I have nominated "/usr/bin/gnome-terminal" as the Terminal Path in Preferences.
(happens to be the same as Mint 18.3)
I can run the application from the Terminal (if I open one manually) and in Gede debug, but NOT using the Run button.
If I remove the Terminal Path in Mint 18.3 , then it also wont open the Terminal.
Put it back in, and it all works again. But not in Mint 19.2using .AppImage
Anyone have any ideas as to why.??
Regards
EDIT: On the same computer , but on the HDD I have Poseidon installed normally (not the .AppImage) and it works correctly ?
Another issue I have been struggling with for a few days.
Until now I have used Linux Mint 18.3
Making a backup of my new laptop which is Mint 19.2 on a mSata usb drive.
Used the bitbucket download of Poseidon.AppImage V0.420 which is the same version as my Mint 18.3
The Run button appears to do nothing.
It does not open a Terminal , even though I have nominated "/usr/bin/gnome-terminal" as the Terminal Path in Preferences.
(happens to be the same as Mint 18.3)
I can run the application from the Terminal (if I open one manually) and in Gede debug, but NOT using the Run button.
If I remove the Terminal Path in Mint 18.3 , then it also wont open the Terminal.
Put it back in, and it all works again. But not in Mint 19.2using .AppImage
Anyone have any ideas as to why.??
Regards
EDIT: On the same computer , but on the HDD I have Poseidon installed normally (not the .AppImage) and it works correctly ?