QDir::homePath() inside app
while deploying you shouldnt copy anything to home. /usr/share for const
predefined data. $HOME/.local/share/appname for any downloaded/created
internal (!) application data like caches. Downloaded media you can save
in Video/Pictures/Music folders.
For settings us
Den 09. mars 2014 18:33, skrev Iosif Hamlatzis:
When deploying a game/application where should its resources
(images/sounds/settings files) be stored so that the game/application
can have both read and write permissions?
You should clarify why you need write permissions, so that it's possible
On 09 Mar 2014, at 18:56, Iosif Hamlatzis wrote:
> ok and the next logical question is: How to get the $HOME folder of the
> emulator or later the actual device in my .pro file? I think it shouldn't be
> hard-coded.
The Harbour FAQ has several detailed answers about where to ship (sic)
read-on
ok and the next logical question is: How to get the $HOME folder of the
emulator or later the actual device in my .pro file? I think it shouldn't
be hard-coded.
I tried to use: "/$$(HOME)/.local/share/$${TARGET}" but it seams this
translates into /home/*mersdk*/.local/share/FarWest/Home/ which is
/usr/share/appname is read only for applications
$HOME/.local/share/appname is read and write
On 09.03.2014 23:33, Iosif Hamlatzis wrote:
When deploying a game/application where should its resources
(images/sounds/settings files) be stored so that the game/application
can have both read and wr
When deploying a game/application where should its resources
(images/sounds/settings files) be stored so that the game/application can
have both read and write permissions?
I tried to use the /usr/share/$$(TARGET) folder where $$(TARGET) is the
name of my game but it seams the game doesn't have pe
