CQRLOG - bugs

small resolutions problem /netbooks/

Submitted by sq9nox on

As netbooks are getting more and more popular (1.2kg, 9 hours on battery, but a low resolution - 1024x600 in my case), the issue of big, not scalable windows of cqrlog becomes a problem. The temporary solution is manually changing the size of virtual screen, with a command like:

xrandr --output LVDS --panning 1024x800

but as far as I know, this doesn't work well on all netbooks.

It would be great to have windows of cqrlog slightly redesigned so they would permit working on 1024x600 resolution.

73 de sq9nox!

Forums: 

Polish national charset in field

Submitted by grzeg on

After upgrade CQRLOG from version 0.7.0 to 0.8.x, I can't write any field with polish charset (for example: Name, QTH, Comment for QSO). Older data is display correct charset. If I edit older data with polish charset and save – this record lost polish charset. The polish charset use UTF-8. I think it's a bug... I have to stay in version 0.7.0 this nice program...
Greg

Forums: 

Exit error

Submitted by mauro_png on

Hi everyone....

when I close the program I see this message:

Saving config file
An unhandled exception occurred at $0807754F :
EInOutError :
$0807754F
$080700B8
$0819A825

in addition, I have noticed sometime program crash that totally freeze the OS...

I am running Slackware 12.2

regards, mauro

Forums: 

Unable to select radio 2 (v.8.2)

Submitted by N8NM on

A small bug:

I seem to be only able to communicate with radio 1 regardless of which radio is selected.

The TRX window's radio 1/radio 2 buttons change color when selected or by using 1 and 2, but the control stays with radio 1.

Both radios are IC-765s; 9600 N81 and using devices /dev/ttyS0 and /dev/ttyS1. I can communicate with each radio if I swap their devices in "Preferences" (set radio 1 as /dev/ttyS1 which is normally radio 2), so it would appear that hamlib and all the hardware is OK.

Forums: 

Edit existing QSO from main window

Submitted by do4nw on

Steps to reproduce:
1. Enter a callsign that you already have in your QSO list.
2. Now you will find the old QSO on the top of the window. Right click on it and choose "edit QSO"

Expected behavior: The values from the old QSO should be filled in and will be editable.

What actually happens here, is: nothing.

Editing a QSO from the QSO list window works without problems.

Forums: 

rig pathname error

Submitted by N8NM on

Hi,

I'm not sure if this is a bug or something on my end, but I'm having a hard time getting the rig control working in CQRLOG. I can control the rigs using the cli command (rigctl -m 329 -r /dev/ttyS0 -s 9600), but the TRX window will not update.

If I launch CQRLOG from a terminal, I get the following message on start-up and when I refresh TRX:

An error has occured setting the rig pathname

I think I have all the configuration settings OK (ID: 329 for IC-765, 9600 N81).

Running Ubuntu 9.04, CQRLOG 0.8.2, and Hamlib V1.2.8.

Forums: 

CQRLOG not working right?

Submitted by kc9fqv on

Hi everyone:

I am a new user of CQRLOG. I come from a WinXP background, and formerly used N3FJP's ACLog. I made the decision a a couple of months ago to move to Linux for my shack PC. I discovered however that while his program ran well under Wine, I could not get the LOTW up/downloads to work properly- that was my main impetus for finding a native Linux logging app.

Forums: 

Incorrect log times

Submitted by g3nrw on

Running cqrlog 0.8.1, hamlib 1.2.9, opensuse 11.0.

Here in the UK, local clock time at the moment = UTC+1. So, for example, the local time is 06:30 (displayed correctly in the system tray), making the UTC 05:30.

However, cqrlog displays the time as 04:30 in the "Start Time" and "End Time" boxes.

(By the way, fldigi reports UTC correctly).

Is there something in cqrlog I need to set up to get the correct time zone?

--
73
Ian, G3NRW

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs