1. wxEuphoria Problem
- Posted by Lone_EverGreen_Ranger Aug 19, 2009
- 1255 views
Hello,
Whenever I try to run a wxEuphoria program, I get the error runtime error (Traceback unavailable).
Here is my code
without warning without type_check include std/wxeud.e constant ID_SAVEALL = 1, ID_FROSTOPTIONS = 2, ID_MAKEEXE = 3 constant MainWin = create(wxFrame,{0,-1, "Frost Editor - DarkScar Games", -1, -1, 800,600}), Mainwin = create(wxPanel,{MainWin}) constant MainBar = create(wxMenuBar,{MainWin}), File = create(wxMenu,{MainBar,"&File"}), File_New_Project = create(wxMenuItem,{File,wxID_NEW,"New Project"}), File_Open_Project = create(wxMenuItem,{File,wxID_OPEN,"Open Project"}), File_Close_Project = create(wxMenuItem,{File,wxID_CLOSE,"Close Project"}), File_Sep = create(wxMenuItem,{File,wxID_SEPARATOR,"-"}), File_Save_Project = create(wxMenuItem,{File,wxID_SAVE,"Save Project"}), File_SaveAs_Project = create(wxMenuItem,{File,wxID_SAVEAS,"Save As Project"}), File_SaveAll_Files = create(wxMenuItem,{File,ID_SAVEALL,"Save All Files"}), File_Sep2 = create(wxMenuItem,{File,wxID_SEPARATOR,"-"}), File_Frost_Option = create(wxMenuItem,{File,ID_FROSTOPTIONS,"Frost Options"}), File_Sep3 = create(wxMenuItem,{File,wxID_SEPARATOR,"-"}), File_Make_Exe = create(wxMenuItem,{File,ID_MAKEEXE,"Make Exe"}), File_Sep4 = create(wxMenuItem,{File,wxID_SEPARATOR,"-"}), File_Exit = create(wxMenuItem,{File,wxID_EXIT,"Exit"}) procedure onMenu_File_Exit(atom this, atom event_type, atom id, atom event) exit_main() end procedure set_event_handler(File,wxID_EXIT,wxEVT_COMMAND_MENU_SELECTED, routine_id("onMenu_File_Exit")) wxMain(MainWin)
2. Re: wxEuphoria Problem
- Posted by euphoric (admin) Aug 19, 2009
- 1233 views
That code runs fine for me!
I get the Frost Editor screen with a File menu...
3. Re: wxEuphoria Problem
- Posted by Lone_EverGreen_Ranger Aug 19, 2009
- 1201 views
That code runs fine for me!
I get the Frost Editor screen with a File menu...
I just ran it, it does run, but when I click on "exit" I get that error.
4. Re: wxEuphoria Problem
- Posted by mattlewis (admin) Aug 19, 2009
- 1210 views
Whenever I try to run a wxEuphoria program, I get the error runtime error (Traceback unavailable).
Which versions of euphoria and wxEuphoria are you using? And which platform?
Matt
5. Re: wxEuphoria Problem
- Posted by Lone_EverGreen_Ranger Aug 19, 2009
- 1187 views
Whenever I try to run a wxEuphoria program, I get the error runtime error (Traceback unavailable).
Which versions of euphoria and wxEuphoria are you using? And which platform?
Matt
I am using Eu 4.0 the bleeding edge of wxEuphoria 0.13.0 or 0.12.0 Windows OS
6. Re: wxEuphoria Problem
- Posted by euphoric (admin) Aug 19, 2009
- 1208 views
- Last edited Aug 20, 2009
That code runs fine for me!
I get the Frost Editor screen with a File menu...
I just ran it, it does run, but when I click on "exit" I get that error.
When I click the X to close, or select "File>Exit," I get this:
Warning ( not_used ): <0229>:: c:/euphoria/include/machine.e - local variable 'check_calls' is not used Press Enter...
Is that what you're talking about?
I'm using Euphoria 4.0 r2543.
Matt, what's the smallest code necessary to determine what version of wxEuphoria one is running? Is there a commandline command that can be used to determine this? If not, maybe there could be?
7. Re: wxEuphoria Problem
- Posted by Lone_EverGreen_Ranger Aug 19, 2009
- 1198 views
- Last edited Aug 20, 2009
That code runs fine for me!
I get the Frost Editor screen with a File menu...
I just ran it, it does run, but when I click on "exit" I get that error.
When I click the X to close, or select "File>Exit," I get this:
Warning ( not_used ): <0229>:: c:/euphoria/include/machine.e - local variable 'check_calls' is not used Press Enter...
Is that what you're talking about?
I'm using Euphoria 4.0 r2543.
Matt, what's the smallest code necessary to determine what version of wxEuphoria one is running? Is there a commandline command that can be used to determine this? If not, maybe there could be?
No, I get the runtime traceback error.
8. Re: wxEuphoria Problem
- Posted by mattlewis (admin) Aug 20, 2009
- 1103 views
That code runs fine for me!
I get the Frost Editor screen with a File menu...
I just ran it, it does run, but when I click on "exit" I get that error.
Matt, what's the smallest code necessary to determine what version of wxEuphoria one is running? Is there a commandline command that can be used to determine this? If not, maybe there could be?
In wxeud.e, you'll find these definitions:
wxEuphoria_Version = {0,13,0} wxNEED_BUILD = 14
They are global. If you are running eu v4, then you need v0.13.0, along with the dll that comes with it. If you use an earlier version of the dll, you'll get lots of crashes. The wxEuphoria_Version constant is self explanatory. wxNEED_BUILD is the version of the dll. As you can see, it isn't the same as the wxEuphoria_Version.
You could probably get away with running v0.12.0 so long as you were using build 14 of the dll. wxEuphoria works with raw euphoria objects, and the definitions of sequences and atoms has changed a little with euphoria 4.0.
Matt
9. Re: wxEuphoria Problem
- Posted by Lone_EverGreen_Ranger Aug 20, 2009
- 1096 views
That code runs fine for me!
I get the Frost Editor screen with a File menu...
I just ran it, it does run, but when I click on "exit" I get that error.
Matt, what's the smallest code necessary to determine what version of wxEuphoria one is running? Is there a commandline command that can be used to determine this? If not, maybe there could be?
In wxeud.e, you'll find these definitions:
wxEuphoria_Version = {0,13,0} wxNEED_BUILD = 14
They are global. If you are running eu v4, then you need v0.13.0, along with the dll that comes with it. If you use an earlier version of the dll, you'll get lots of crashes. The wxEuphoria_Version constant is self explanatory. wxNEED_BUILD is the version of the dll. As you can see, it isn't the same as the wxEuphoria_Version.
You could probably get away with running v0.12.0 so long as you were using build 14 of the dll. wxEuphoria works with raw euphoria objects, and the definitions of sequences and atoms has changed a little with euphoria 4.0.
Matt
OK, now it works, I wasn't using the bleeding version as I thought I was.
10. Re: wxEuphoria Problem
- Posted by Jerry_Story Aug 20, 2009
- 1102 views
In wxeud.e, you'll find these definitions:
wxEuphoria_Version = {0,13,0} wxNEED_BUILD = 14
They are global. If you are running eu v4, then you need v0.13.0, along with the dll that comes with it. If you use an earlier version of the dll, you'll get lots of crashes. The wxEuphoria_Version constant is self explanatory. wxNEED_BUILD is the version of the dll. As you can see, it isn't the same as the wxEuphoria_Version.
You could probably get away with running v0.12.0 so long as you were using build 14 of the dll. wxEuphoria works with raw euphoria objects, and the definitions of sequences and atoms has changed a little with euphoria 4.0.
Matt
I hope some day the process of installing wxEuphoria is automated. If Euphoria programmers have difficulty installing wxEuphoria, imagine the difficulty people outside the Euphoria community have. Typically they are less familiar with the Euphoria world and besides have less motivation. Every program based on wxEuphoria and intended for the general public will have this problem until the process of installing wxEuphoria is automated.
11. Re: wxEuphoria Problem
- Posted by ghaberek (admin) Aug 20, 2009
- 1097 views
I hope some day the process of installing wxEuphoria is automated. If Euphoria programmers have difficulty installing wxEuphoria, imagine the difficulty people outside the Euphoria community have. Typically they are less familiar with the Euphoria world and besides have less motivation. Every program based on wxEuphoria and intended for the general public will have this problem until the process of installing wxEuphoria is automated.
There isn't much "installation" required. Currently, wxEuphoria is a single DLL/SO file and a single library "wrapper" file. If you're binding or translating your application for distribution, just include the wxEuphoria DLL/SO as well. For Windows, you also need to include a single compiled wxWidgets DLL, and on Linux, you can typically install wxWidgets with your favorite package manager (e.g. sudo apt-get install libwxgtk2.8-dev libwxgtk2.8-dbg).
Matt is (or was) also working on a Euphoria 4.0 interpreter with the wxEuphoria routines built-in. This would make the "wrapper" file nothing more than a bunch of call_func/proc() routines.
-Greg
12. Re: wxEuphoria Problem
- Posted by mattlewis (admin) Aug 20, 2009
- 1065 views
There isn't much "installation" required. Currently, wxEuphoria is a single DLL/SO file and a single library "wrapper" file. If you're binding or translating your application for distribution, just include the wxEuphoria DLL/SO as well. For Windows, you also need to include a single compiled wxWidgets DLL, and on Linux, you can typically install wxWidgets with your favorite package manager (e.g. sudo apt-get install libwxgtk2.8-dev libwxgtk2.8-dbg).
Nevertheless, on Linux there are dependencies that need to be installed, and not everyone is capable of getting a shared object installed if it's not done by their package manager.
Matt
13. Re: wxEuphoria Problem
- Posted by gbonvehi Aug 21, 2009
- 1070 views
A good solution to this problem would be to statically link wxWidgets, the size executable size will be bigger but at least you won't have the dependencies problem. Skype is a good example of a program that does this (it's QT actually).
http://www.wxwidgets.org/docs/technote/install.htm#other
Cheers,
Guillermo