[hpsdr] cuSDR64 Linux Settings?

[Berndt Josef Wulf]

G'day Sid,

you're welcome.

You need special permissions to write to /usr/local/bin, which you
wouldn't have as a normal user. This is likely the reason why cuSDR
can't create the ini files needed to remember it's last state when it
was shutdown.

Just create a bin directory inside your home directory, place the binary
inside, and run it from there. You may also want to remove the
executable from /usr/local/bin as to ensure you run the correct binary.

If this doesn't work, have look through the cuSDR.log file. 

AFAIK, the standard location for QT related preference files on *nix
systems is inside /home/<username>/.config/<application>. E.g.
preferences for QtCreator are stored inside /home/wulf/.config/QtCreator


73, Berndt
VK5ABN

On Sun, 2013-10-13 at 23:46 +0100, Sid Boyce wrote:
> Thanks Berndt,
> tindog:/usr/src/cuSDR64 # svn info
> Path: .
> Working Copy Root Path: /usr/src/cuSDR64
> URL: http://svn.tapr.org/repos_sdr_hpsdr/trunk/DL3HVH/cuSDR64
> Relative URL: ^/trunk/DL3HVH/cuSDR64
> Repository Root: http://svn.tapr.org/repos_sdr_hpsdr
> Repository UUID: fab57ed4-c20f-0410-8556-bd0ba87add53
> Revision: 3096
> Node Kind: directory
> Schedule: normal
> Last Changed Author: dl3hvh
> Last Changed Rev: 2897
> Last Changed Date: 2013-02-17 09:28:14 +0000 (Sun, 17 Feb 2013)
> 
> The cuSDR64 binary is in /usr/local/bin and is started as user.
> 73 ... Sid.
> 
> On 13/10/13 23:26, Berndt Josef Wulf wrote:
> > G'day Sid,
> >
> > which version of cuSDR64 are you running?
> >
> > cuSDR64 uses files called settings.ini and WindowsSettings.ini.
> >
> > Looking at the source file, these files are stored in the directory
> > where the cuSDR64 executable resides. In my case its in the
> > ~/cuSDR64/bin directory.
> >
> > cusdr_mainWidget.cpp:2383
> > QSettings settings(QCoreApplication::applicationDirPath() +  "/" +
> > m_windowsSettingsFilename, QSettings::IniFormat);
> >
> > If you saved the file say in /usr/bin, it will not be able to create the
> > settings files due to lack of privileges. In this case, create a ~/bin
> > directory and place the cuSDR64 binaries in there.
> >
> > An easy way of checking that it uses the correct files is by setting
> > your call-sign from the "display-menu" and close the application. Your
> > call-sign should show once you start again.
> >
> > Does this make sense?
> >
> > 73, Berndt
> > VK5ABN
> >
> > On Sun, 2013-10-13 at 21:04 +0100, Sid Boyce wrote:
> >> ***** High Performance Software Defined Radio Discussion List *****
> >>
> >> I see there is settings.ini for Windows.
> >>
> >> With Linux, everytime cuSDR64 is started it always comes up needing
> >> settings to be done.
> >>
> >> I don't see a way of saving the settings.
> >> 73 ... Sid.
> >>
> >
> >
> 
> 




 1381717660.0