Filesystem layout conflicts

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install ommp2x in its default fashion and editing config files
2.
3.

What is the expected output? What do you see instead?
It doesn't return to gmenu unless it is at root.

What version of the product are you using? On what operating system?
I think both gpes have this problem

Please provide any additional information below.
I think it just needs to be reorganized by default to conform with a more
standard layout like the one on the standards website.

Original issue reported on code.google.com by gohmif...@gmail.com on 3 Nov 2007 at 6:45

[GoogleCodeExporter]

I know this is old, but I'm just now getting another gp2x and starting 
development again.

I think I'm going to need more information to better understand the issue.  
With the
latest build there should be one gpe, 'ommpc2x.gpe'.  Technically it's just a 
script
that launches the actual executable(called ommpc2x, earlier versions had the 
actual
executable named ommpc2x.gpe and the script run_ommpc2x.gpe, so there might be 
some
confusion there) and returns to the gp2x menu when finished.  It's been a few 
months
since I've had a gp2x, but from what I remember this kicks off the autorun and 
gets
you back to gmenu.  

Now, if I had to guess, I would say you're directly running the executable and 
not
the script that will return you to the menu.  And the reason is probably 
because the
script doesn't work to actually start ommpc(without editing) unless ommpc is in 
the
root directory. 

So the short of it is that I think all that need to be done is editing of the 
startup
script to match you're install location as described(albeit poorly) in the 
README. 

Although using a standard directory structure would be nice, that structure is 
up to
the user and it's unlikely it will ever be uniform.  I personally would never 
have an
"applications" folder...it would be "Apps".  That's the beauty and downfall of 
an
open system. 

All of that being said, I can fix this particular issue with a little work.  The
script can be made to not be dependent on the install directory...so at the very
least that is what the issue will become...

Original comment by codert...@gmail.com on 3 Feb 2008 at 4:33

• Changed state: Accepted
• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Closed. 

Original comment by codert...@gmail.com on 10 Aug 2009 at 6:50

• Changed state: WontFix