Page 1 of 1
not forward compatible?
Posted: Sat Nov 06, 2021 12:11 pm
by leavereality
So I made a little app with RapaGUI 1.2, Amilion, works fine but just been informed and tested myself that it works fine on 1.2 but if RapaGUI 2.0 or 2.1 is installed, the software refuses to start with the following message: "This program requires RapaGUI.hwp!"
I will be updating my little program with RapaGUI 2.1, but should it not be forward compatible? Ie old stuff works on the new, I get it newer made stuff not working on older RapaGUI just thought Id ask. cheers
Re: not forward compatible?
Posted: Sat Nov 06, 2021 1:54 pm
by leavereality
Actually this is a bit more of an issue as RapaGUI 2.x needs Hollywood 9, I only have Hollywood 8, so I cant update my app at the moment, any suggestions? (yes I know I could upgrade but dont know if i use the program enough, I do love it, but Im very much a amateur / part time mess around program so all the new features are kind of wasted on me)
Re: not forward compatible?
Posted: Sat Nov 06, 2021 6:12 pm
by mrupp
I would recommend to recompile your app and this time to include RapaGUI 1.2 with the { link = True } option. With this, RP is included in your binary file and your app is independent from what the end user has installed on his machine.
Re: not forward compatible?
Posted: Sat Nov 13, 2021 1:41 pm
by leavereality
So only just had time to try this today, when I use
@REQUIRE "RapaGUI", {Link = True}
and compile it I keep getting requester "Requires RapaGUI.hwp"
I see the size of the program is about 300Kb bigger the same size as RapaGUI.hwp so I guess the code is working, so why would the requester pop up?
Plus my original question still stands, why is a RapaGUI 1.2 made program not compatible with RapaGUI 2.0?
Final question, would any one be willing to recompile my app to make it RapaGUI 2.0 compatible if there no solution? Or any chance of a cheeky discount to upgrade to hollywood 9?
Re: not forward compatible?
Posted: Sat Nov 13, 2021 2:12 pm
by plouf
rapagui 2.0 has an issue on older hollywood version, maybe its relevant to that
But also, as an alternative, Hollywood loads plugins in programdir FIRST, so maybe a workarount is to copy the "working" plugin in same dir ?
Re: not forward compatible?
Posted: Sat Nov 13, 2021 3:58 pm
by plouf
leavereality wrote: ↑Sat Nov 13, 2021 1:41 pm
Final question, would any one be willing to recompile my app to make it RapaGUI 2.0 compatible if there no solution?
if only need recompile (And no coding) .. yes
but maybe my idea to copy plugin in programdir may work
also hollywood has an upgrade option for only 39 euro..
Re: not forward compatible?
Posted: Sat Nov 13, 2021 5:39 pm
by airsoftsoftwair
leavereality wrote: ↑Sat Nov 13, 2021 1:41 pm
Plus my original question still stands, why is a RapaGUI 1.2 made program not compatible with RapaGUI 2.0?
There was a major design flaw in 1.2 which I had to break with in 2.0. You can read about it
here. Still, most RapaGUI 1.2 scripts will work just fine with 2.0.
Re: not forward compatible?
Posted: Sat Nov 13, 2021 9:21 pm
by leavereality
I find it surprising then that my very simple app would not work on RapaGUI 2.0, I beginning to think I should of just made it with MUI Royal but thought learning RapaGUI would be better for maybe future cross platform apps.
Anyway here the code, if anyone can help that be great,
Code: Select all
#BLACK
@REQUIRE "RapaGUI"
@APPTITLE "LionGUI"
@APPVERSION "$VER: 1.1"
@APPCOPYRIGHT "(C) Copyright 2021 by Leave Reality Studio"
@APPAUTHOR "Vincent Perkins"
@APPDESCRIPTION "LionGUI"
moai.CreateApp([[
<?xml version="1.0" encoding="iso-8859-1"?>
<application>
<window title="LionGUI">
<vgroup>
<pageview>
<vgroup title="Pi">
<vgroup frame="true" frametitle="OpenURL">
<button id="o1">Google</button>
<button id="o2">AmigaWorld</button>
<button id="o3">Aminet</button>
<button id="o4">WhdDownLoad</button>
<button id="o5">EAB Forum</button>
<button id="o6">AmigaNG</button>
<button id="o7">Wikipedia</button>
</vgroup>
<vspace height="3" />
<vgroup frame="true" frametitle="Rabbit Hole">
<button id="b1">Browser</button>
<button id="b2">Audacious</button>
<button id="b3">Office</button>
<button id="b4">Host Settings</button>
<button id="b5">File Manager</button>
<button id="b6">Terminal</button>
<button id="b6b">Exit UAE</button>
<button id="b7">Power Off</button>
</vgroup>
</vgroup>
<vgroup title="Windows">
<vgroup frame="true" frametitle="OpenURL">
<button id="o8">Google</button>
<button id="o9">AmigaWorld</button>
<button id="o10">Aminet</button>
<button id="o11">WhdDownLoad</button>
<button id="o12">EAB Forum</button>
<button id="o13">AmigaNG</button>
<button id="o14">Wikipedia</button>
</vgroup>
<vspace height="3" />
<vgroup frame="true" frametitle="Rabbit Hole">
<button id="b9">Browser</button>
<button id="b10">Paint</button>
<button id="b11">Office</button>
<button id="b12">NotePad</button>
<button id="b13">Steam</button>
<button id="b14">CommandLine</button>
<button id="b14b">Exit UAE</button>
<button id="b15">Power Off</button>
</vgroup>
</vgroup>
</pageview>
</vgroup>
</window>
</application>
]])
InstallEventHandler({RapaGUI = Function(msg)
Switch msg.class
Case "Button":
Switch msg.Attribute
Case "Pressed":
Switch msg.ID
Case "o1": ;
OpenURL ("http://google.com")
Case "o2": ;
OpenURL ("http://amigaworld.net")
Case "o3": ;
OpenURL ("http://aminet.net")
Case "o4": ;
OpenURL ("http://whdownload.com")
Case "o5": ;
OpenURL ("http://eab.abime.net")
Case "o6": ;
OpenURL ("http://amigang.com")
Case "o7": ;
OpenURL ("http://en.wikipedia.org")
Case "o8": ;
OpenURL ("http://google.com")
Case "o9": ;
OpenURL ("http://amigaworld.net")
Case "o11": ;
OpenURL ("http://whdownload.com")
Case "o10": ;
OpenURL ("http://aminet.net")
Case "o12": ;
OpenURL ("http://eab.abime.net")
Case "o13": ;
OpenURL ("http://amigang.com")
Case "o14": ;
OpenURL ("http://en.wikipedia.org")
Case "b1": ;
Execute ("host-run exo-open --launch WebBrowser")
Case "b2": ;
Execute ("host-run audacious")
Case "b3": ;
Execute ("host-run loffice")
Case "b4": ;
Execute ("host-run xfce4-settings-manager")
Case "b5": ;
Execute ("host-run exo-open --launch TerminalEmulator")
Case "b6": ;
Execute ("host-run exo-open --launch FileManager")
Case "b6b": ;
Execute ("Run C:UAEQuit")
Case "b7": ;
Execute ("host-run poweroff")
Case "b9": ;
Execute ("C:winlaunch >NIL: Chrome")
Case "b10": ;
Execute ("C:winlaunch >NIL: C:\\windows\\system32\\mspaint.exe")
Case "b11": ;
Execute ("C:winlaunch >NIL: soffice")
Case "b12": ;
Execute ("C:winlaunch >NIL: Notepad")
Case "b13": ;
Execute ("C:winlaunch >NIL: C:\\Program Fies\\Steam\\Steam")
Case "b14": ;
Execute ("C:winlaunch >NIL: cmd")
Case "b14b": ;
Execute ("Run C:UAEQuit")
Case "b15": ;
Execute ("C:winlaunch >NIL: Shutdown /S")
EndSwitch
EndSwitch
EndSwitch
EndFunction})
Repeat
WaitEvent
Forever
hollywood has an upgrade option for only 39 euro..
I would of normally, but I slight overspent at the moment, treated myself to a new office chair, should gone cheaper really but it cost me £350, As now I had to have some dental work done, hurt like hell and cost £280!, Add to that my Power company gone bust, so in the UK we got a huge Power Price issue going one, not too sure how much its going to go up by, so little worried by that, then add to that petrol that use to cost 130p a litre now gone up to 148p a litre and weekly food shopping gone up £10 so Brexit going well over here
(i voted remain), I not that rich of guy, just careful with money but I need to cap all my luxury spending for now, at least till Christmas.
Re: not forward compatible?
Posted: Sun Nov 14, 2021 1:26 am
by plouf
copying plugin in the same directory works or not ? (usefull information for future reference)
this hw9 compiled 68k exe seems to work, check ..
https://www.file.io/download/refJBm5nDzHo
Re: not forward compatible?
Posted: Sun Nov 14, 2021 1:06 pm
by leavereality
thanks for doing that for me plouf, but the file not on there, could email me maybe
ngamiga@gmail.com
It seem to make no difference weather or not RapaGUI.hwp is in the same directory or not