Re: [Xlog-discussion] andy's email address bouncing
Andy, A direct message to your comcast account seems to work! Thanks, Joop Op 27 sep. 2013, om 13:39 heeft Andy Stewart andystew...@comcast.net het volgende geschreven: HI Joop, Are people sending to my kb1...@arrl.net email address and receiving this message? I had this problem fixed once before. If this ISP (comcast) continues to block my legitimate email, I may need to switch. I think they're blocking my email from SourceForge, too. My direct email address is: andystew...@comcast.net Thanks for letting me know that there is a problem. 73, Andy -- Andy Stewart (KB1OIQ) Founder: Worcester Linux Users' Group Founder: Chelmsford Linux Meetup Group President: PART of Westford, MA (WB1GOF) signature.asc Description: Message signed with OpenPGP using GPGMail ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] new xlog maintainer: Andy Stewart
Hello, I am happy to announce that Andy Stewart KB1OIQ will take over xlog maintenance. Andy has a fair amount of experience both in programming and linux distributions. He is also founder and president of two local linux user groups and an active ham. Andy has shown interest in taking xlog further. Quoting from one of his emails: I would like to see xlog survive in its current form, with bug fixes and updates as needed. I think there is plenty of room in the ham radio community for a more casual logger (xlog) I hope you will all support Andy and keep xlog alive. I will do as much as I can to get Andy going. I will step back, since I pretty much lost interest in programming, sorry about that. My thanks goes to Andy and I hope to see you all on the air! Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org https://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog-2.0.5 released
Hi people, I have squashed most of the bugs which where reported on the savannah project page. This release also adds patches from Gentoo and Ubuntu. Download from http://download.savannah.gnu.org/releases/xlog http://download.savannah.gnu.org/releases/xlog/ (you may need to wait for your mirror to catch up). Here is a the full changelog: - Changes for xlog version 2.0.5 - 2011/02/23 * Swedish translations updated by Peter, SM4ABE * 2 patches from the Gentoo repository: ADIF field should be named TX_PWR instead of TX_POWER. Xlog now exports the QSLIN and QSLOUT fields. Thanks to Tom DL1JBE. * When printing the log, the last QSO would not print. This has been fixed. Reported by Bruce, WB0GAG (fixes bug #29941). * Make sure the '~' macro for the keyer does not crash xlog when there is no log open. * Fix a crash when hitting enter in the RX(RST) field when the keyer is active, see Ubuntu bug #608718. Also, the QSO is now added to the log correctly (fixes bug #27888). * Update some GTK Calls with newer calls which have become deprecated since version 2.20. Patch by Charles AA1VS, thanks! Done the same for GTK version 2.22. This means you need at least version 2.18 of GTK+ to compile xlog. * Fixed ADIF file corruption when a non-ham frequency is filled in. Reported by Pierfrancesco, IK5PVX (fixes bug #29122). * Done some work on type and find. Xlog would look up a callsign with every key pressed. This has a disadvantage as Graeme, ZL2APV, has pointed out. Suppose we log AH6V which is already in our logs, xlog will fill in name and QTH. But if we want to log AH6VA, the same name and QTH will appear, xlog will stop after the 'V'. The new behaviour is much better. Lookup will be activated when the callsign field loses focus, so after using the TAB key or clicking the mouse somewhere else (fixes bug #27477). * When there is no log open and another application wants to send data to xlog, the warning dialog with No log open while receiving remote data will be displayed only once, so we don't block the gui (fixes bug #31635). * Changing the name of the free fields in the log now updates the column names in all the logs which are opened (fixes bug #27251). * To speed up logging, typing ENTER in the callsign field will jump to the TX(RST) field. Suggested by Graeme, ZL2APV. * cty.dat updated to version 20110121. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Re: bug #27477
On Mon, 07 Feb 2011 12:04:48 +1300, Graeme wrote:
Hi Joop,
Thanks for looking at this. A few comments to help you decide the
best approach to the problem:
At present as each character is typed in for a call, a name and qth
lookup occurs if the name and qth fields are blank which of course
means that if you are entering say zl2cde and zl2cd exists then the
name and qth will be filled in as this is entered and the lookup will
fail when the e is entered.
Two approaches (possibly more) can be made:
1. Don't do a lookup until {Enter} or {Tab} are keyed or the call
edit box is exited.
2. On each key stroke, erase the name and qth edit boxes and let the
lookup occur in the normal way.
Unfortunately this will introduce another problem:
If you have recorded zl2cd as the call and missed the last letter of
what was really zl2cde due to qrm etc. and record the name and qth
and
later in the qso realise that there is an error in the call and fix
it, amending the call will erase the correct name and qth you have
already recorded.
Possibly using {tab} to exit the call edit box could allow you to
exit without doing a lookup and any other method does a lookup.
Sorry I don't have a solution but at least I have flagged some of
the problems.
73 Graeme ZL2APV
Wo, sounds like a though one Graeme! Thanks for explaining things.
Can I send you a patch when I have found a solution? In other words,
do you know how to compile source code and apply patches?
Thanks,
Joop PG4I
___
Xlog-discussion mailing list
Xlog-discussion@nongnu.org
http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] errors on install
On Thu, 24 Dec 2009 19:08:06 -0500 Stewart Whitehouse ke...@tampabay.rr.com wrote: Hi, I've been away for awhile and am kind of rusty with installing programs in Ubuntu. I tried to install Xlog 2.0.3 and get recursive errors during the 'make install' part. I'm running Ubuntu 9.04 and keep up with the updates. I used to run Xlog 1.** with no problems. Any suggestions will be appreciated. Hi Stew, it helps if you send the exact errors in the next mail (a copy/past from your terminal). Recursive errors doesn't tell me much. Also, please describe how you install xlog. Also, is XDX still being supported? Yes, but only bugfixes, no new features. The next version of xlog will have an integrated dx-cluster client. Because my time is limited, xdx will eventually be phased out. Thanks, Stew ke4yh Regards, Joop -- Joop Stakenborg p...@xs4all.nl ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] xlog and PCLinuxOS
On Wed, 23 Dec 2009 11:44:52 -0500 Jan Ditzian ditz...@windstream.net wrote: Joop, This does not work. The buttons appear, but only the default values come up in the frequency or mode window. However, I can clearly see the current VFO frequency at the bottom of the xlog data entry window. Don't fill in any default values when you want to use hamlib. The default values will always overwrite current values. Jan, KX2A -- Joop Stakenborg p...@xs4all.nl ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] people wanted for the xlog test team
I am looking for people who want to test CVS versions of xlog. This will give you to opportunity to see what future versions of xlog will be like. You may also suggest improvements and changes for the upcoming version. Coordination of the test team will be through private email. You will need experience with compiling source code. Measures have been taken to avoid the loss of QSO data, the CVS version now uses a separate configuration directory. Please send me a private e-mail if you would like to join. You will have time until Friday evening 23.59 UTC to respond. Thanks, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog project changes
Now that we have more people working on xlog, I have moved all of the parts of the xlog project to savannah. Here are some URL's: Homepage: http://www.nongnu.org/xlog/ Download: http://savannah.nongnu.org/download/xlog You are encouraged to use the bugs, patch and task manager at the project page: http://savannah.nongnu.org/projects/xlog , but sending bugs, comments and suggestions to the mailing list will also work of course ;-) The task manager will become an important tool for tracking and coordinating xlog development. Regards, Joop PG4I attachment: face-wink.png___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog-2.0.3 released
This is an important bugfix release, here's the changelog: * xlog will now display an exit confirmation dialog whenever you want to exit the program. * This release fixes crashes when the function keys are used for the keyer. Thanks Jack, AK7O for reporting. * Remote logging now adds a ?: string, which is used by eepkeyer written by Mike K6EEP, see http://www.hamsoftware.org. You will have to set add data to QSO frame in the first page of the preferences dialog. Eepkeyer now wil send one character at a time for the callsign, which can be used for dupe checking. Patch by Mike, K6EEP. * When bands are removed or added from the scoring window through Settings - Dialogs and Window, the scoring window will now get updated correctly. Reported by Ron, W6FM. * Dupe checking did not work when checking against other bands. This has been fixed. * A new tool has been added. When Tools - Find unknown countries is selected, xlog will show a list of contacts for which DXCC lookup fails. You can then correct this by using a DXCC- string in the awards column. * There were several minor bugfixes. * cty.dat updated to cty-1912. I have uploaded the source to http://pg4i.chronos.org.uk/download/xlog-2.0.3.tar.gz Debian packages and WIN32 executable will follow later this week. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] xlog keyer
Op woensdag 17-06-2009 om 13:43 uur [tijdzone -0600], schreef jack User: Xlog seems to be working fine in Ubuntu 8.10. however the keyer does not respond well to any F-key command. in fact pushing any one of the F-keys 1-12 causes Xlog to quit completely. does anyone know a fix for this? Thanks for the report Jack and sorry for the delay. It looks like xlog is crashing. If you start xlog from a console, do you see any output on the screen? Does clicking on the F-keys (instead of using the key itself) also crash xlog? Can you provide a gdb backtrace? jack ak7o Thanks, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog-2.0.2 released
* This fixes distance and azimuth calculation for stations west of Greenwich. Thanks to Dana, AF7Z for reporting. * Changing the locator in the preferences dialog now correctly updates the corresponding latitude and longitude entries. * You might need to re-configure your location in the preferences dialog with this release. * cty.dat updated to cty-1909. See http://pg4i.chronos.org.uk/download/xlog-2.0.2.tar.gz regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] a fix for bearing and azimuth errors in 2.0.1
The attached diff fixes the errors reported by Dana. It appears the N/S
E/W options in the preferences dialog were not saved correctly. Also,
changing the locator field in the same dialog would enter incorrect
values for latitude /longitude because the minus sign needs to be
ignored.
This diff needs a clean xlog-2.0.1 source tree. After recompiling and
installing xlog check your location, especially the N/S and E/W options.
I will release an updated xlog version (2.0.2) for this bug in about 2
weeks time.
Regards,
Joop PG4I
diff -u -r xlog-2.0.1/src/dxcc.c xlog-2.0.1.fixed_qrb/src/dxcc.c
--- xlog-2.0.1/src/dxcc.c 2009-01-28 20:47:15.0 +0100
+++ xlog-2.0.1.fixed_qrb/src/dxcc.c 2009-05-06 12:15:22.0 +0200
@@ -830,11 +830,11 @@
if (lookup.country 0)
{
- if (preferences.NS == 0)
+ if (preferences.NS == 1)
lat = -1.0 * preferences.latitude;
else
lat = preferences.latitude;
- if (preferences.EW == 0)
+ if (preferences.EW == 1)
lon = -1.0 * preferences.longitude;
else
lon = preferences.longitude;
Only in xlog-2.0.1.fixed_qrb/src: dxcc.c.orig
diff -u -r xlog-2.0.1/src/gui_preferencesdialog.c xlog-2.0.1.fixed_qrb/src/gui_preferencesdialog.c
--- xlog-2.0.1/src/gui_preferencesdialog.c 2009-01-04 21:32:19.0 +0100
+++ xlog-2.0.1.fixed_qrb/src/gui_preferencesdialog.c 2009-05-06 12:15:22.0 +0200
@@ -81,12 +81,18 @@
/* update widgets */
if (lat 0.00)
+ {
+ lat = -1.0 * lat;
gtk_combo_box_set_active (GTK_COMBO_BOX (NScombo), 1);
+ }
else
gtk_combo_box_set_active (GTK_COMBO_BOX (NScombo), 0);
if (lon 0.00)
+ {
+ lon = -1.0 * lon;
gtk_combo_box_set_active (GTK_COMBO_BOX (EWcombo), 1);
+ }
else
gtk_combo_box_set_active (GTK_COMBO_BOX (EWcombo), 0);
@@ -841,13 +847,13 @@
/* location */
temp = g_strdup_printf (%3.2f, preferences.latitude);
gtk_entry_set_text (GTK_ENTRY (latentry), temp);
- if (preferences.NS == 1)
+ if (preferences.NS == 0)
gtk_combo_box_set_active (GTK_COMBO_BOX (NScombo), 0);
else
gtk_combo_box_set_active (GTK_COMBO_BOX (NScombo), 1);
temp = g_strdup_printf (%3.2f, preferences.longitude);
gtk_entry_set_text (GTK_ENTRY (longentry), temp);
- if (preferences.EW == 1)
+ if (preferences.EW == 0)
gtk_combo_box_set_active (GTK_COMBO_BOX (EWcombo), 0);
else
gtk_combo_box_set_active (GTK_COMBO_BOX (EWcombo), 1);
@@ -1049,8 +1055,8 @@
else
preferences.longitude = atof (temp);
- preferences.NS = gtk_combo_box_get_active (GTK_COMBO_BOX (NScombo)) + 1;
- preferences.EW = gtk_combo_box_get_active (GTK_COMBO_BOX (EWcombo)) + 1;
+ preferences.NS = gtk_combo_box_get_active (GTK_COMBO_BOX (NScombo));
+ preferences.EW = gtk_combo_box_get_active (GTK_COMBO_BOX (EWcombo));
preferences.units = gtk_combo_box_get_active
(GTK_COMBO_BOX (unitscombo)) == 1 ? 0 : 1;
Only in xlog-2.0.1.fixed_qrb/src: gui_preferencesdialog.c.orig
___
Xlog-discussion mailing list
Xlog-discussion@nongnu.org
http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Azimuth Error in Xlog
Op maandag 04-05-2009 om 11:01 uur [tijdzone -0600], schreef Dana Rees: Thank you for the response. I quickly check the hamlib qrb function and found that it was working properly, so I tracked down in the xlog code where it was being called in gc.c and found on line 61 and 62 the following: /* data in cty.dat uses a negative number for eastern longitudes */ retcode = qrb (lonmy, latmy, -1 * londx, latdx, distsp, bsp); When checking the values of lonmy and londx, it lonmy had the wrong sign, needing to be negated also. This may be a function of something upstream, but with that change, gridsquare information in preferences looks correct, and azimuth and distance appear correctly. updated code and looks like: /* data in cty.dat uses a negative number for eastern longitudes */ retcode = qrb ((-1.0 * lonmy), latmy, (-1.0 * londx), latdx, distsp, bsp); Thank you 73. Dana Thanks Dana, with your modification I seem to be getting wrong values for locations west of greenwich. So I guess it needs a bit more investigation. I will come up with a solution within the next few days/weeks. Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] ADIF-Import Problems
Op zondag 29-03-2009 om 19:21 uur [tijdzone +0200], schreef Juergen Matthes: Hi everyone, can someone give me a hint on an import-problem into xlog version 2.0.1 running on a Debian/GNU-Linux (squeeze) System, AMD-64 Machine. I have converted my old Logbook to ADIF-Format (about 2000 records) and try to import that into xlog. Somehow I discovered that some fields are just not imported, no matter what. So I created a test-log in xlog with just one entry (record) and exported that to ADIF. Closing the test-log and then trying to re-import the exported file shows the same behaviour: The fields TX-POWER, OWN-QTH and RIG are always left empty! On my own converted data, even more fields are left empty. No idea what's going on! Below is the exported ADIF-file. Would appreciate some advice! Thanks in advance, 73's from SW-Germany Juergen Hello Juergen, the answer is simple. xlog will only import ADIF data for fields which are present in xlog. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog-2.0.1 released
Hi folks, xlog-2.0.1 is on the air! It is a minor bugfix release, see: http://pg4i.chronos.org.uk/download/xlog-2.0.1.tar.gz changelog at: http://pg4i.chronos.org.uk/linux/xlog.changelog win32 version: http://pg4i.chronos.org.uk/download/xlog2.0.1-setup.exe If you are familiar with patch, find the diffs against version 2.0 attached. You will need to run autoconf after patching. Regards, Joop PG4I diff -u -r xlog-2.0/ChangeLog xlog-2.0.1/ChangeLog --- xlog-2.0/ChangeLog 2009-02-09 20:33:46.0 +0100 +++ xlog-2.0.1/ChangeLog2009-02-23 18:54:06.0 +0100 @@ -1,3 +1,17 @@ +- Changes for xlog version 2.0.1 - 2009/02/23 + * Compiler flags have been fixed to avoid conflicts between different +versions of GTK+ and GLIB. + * Add a compilation fix for 64 bit architectures. + * The desktop menu entry has been fixed. + * The win32 version will now use the native windows fork function for +displaying the handbook so the gui will not get blocked. + * When Options - Country Map is displayed for the first time, xlog will +display a map if the awards or callsign fields are filled correctly. +Reported by Larry, W4LK. + * Using ctrl-k no longer unselects a possible selected QSO. This way you +can update a logged QSO with the help of ctrl-k. + * cty.dat updated to cty-1902. + - Changes for xlog version 2.0 - 2009/02/10 * A fix has been added for displaying Help - Keys from the menu. * Fixed a crash after creating a new log which already exists. diff -u -r xlog-2.0/configure.in xlog-2.0.1/configure.in --- xlog-2.0/configure.in 2009-01-31 16:14:02.0 +0100 +++ xlog-2.0.1/configure.in 2009-02-21 16:05:22.0 +0100 @@ -1,7 +1,7 @@ dnl Process this file with autoconf to produce a configure script. AC_PREREQ(2.60) -AC_INIT(xlog, 2.0, p...@amsat.org) +AC_INIT(xlog, 2.0.1, p...@amsat.org) AM_INIT_AUTOMAKE AM_MAINTAINER_MODE AC_ISC_POSIX diff -u -r xlog-2.0/data/desktop/xlog.desktop xlog-2.0.1/data/desktop/xlog.desktop --- xlog-2.0/data/desktop/xlog.desktop 2007-11-05 16:27:53.0 +0100 +++ xlog-2.0.1/data/desktop/xlog.desktop2009-02-21 16:34:28.0 +0100 @@ -7,6 +7,6 @@ Exec=xlog %F Icon=xlog-icon.png Terminal=false -Type=ApplicationHamRadio +Type=Application Categories=Utility;Database;HamRadio;GTK MimeType=text/x-xlog diff -u -r xlog-2.0/data/doc/ChangeLog xlog-2.0.1/data/doc/ChangeLog --- xlog-2.0/data/doc/ChangeLog 2009-02-09 20:33:46.0 +0100 +++ xlog-2.0.1/data/doc/ChangeLog 2009-02-23 18:54:06.0 +0100 @@ -1,3 +1,17 @@ +- Changes for xlog version 2.0.1 - 2009/02/23 + * Compiler flags have been fixed to avoid conflicts between different +versions of GTK+ and GLIB. + * Add a compilation fix for 64 bit architectures. + * The desktop menu entry has been fixed. + * The win32 version will now use the native windows fork function for +displaying the handbook so the gui will not get blocked. + * When Options - Country Map is displayed for the first time, xlog will +display a map if the awards or callsign fields are filled correctly. +Reported by Larry, W4LK. + * Using ctrl-k no longer unselects a possible selected QSO. This way you +can update a logged QSO with the help of ctrl-k. + * cty.dat updated to cty-1902. + - Changes for xlog version 2.0 - 2009/02/10 * A fix has been added for displaying Help - Keys from the menu. * Fixed a crash after creating a new log which already exists. diff -u -r xlog-2.0/data/dxcc/cty.dat xlog-2.0.1/data/dxcc/cty.dat --- xlog-2.0/data/dxcc/cty.dat 2009-01-15 19:39:13.0 +0100 +++ xlog-2.0.1/data/dxcc/cty.dat2009-02-23 18:52:47.0 +0100 @@ -106,7 +106,7 @@ West Malaysia:28: 54: AS:3.20: -101.60:-8.0: 9M2: 9M1,9M2,9M4,9W2,9W4; East Malaysia:28: 54: OC:5.80: -118.10:-8.0: 9M6: -9M6,9M8,9W6,9W8,=9M1CSQ,=9M1CSS,=9M4SEA,=9M4SMO; +9M6,9M8,9W6,9W8,=9M4SEA,=9M4SMO; Nepal:22: 42: AS: 27.70: -85.30: -5.75: 9N: 9N; Rep. of Congo:36: 52: AF: -4.30: -15.30:-1.0: 9Q: @@ -138,7 +138,7 @@ Scarborough Reef: 27: 50: AS: 15.10: -117.50:-8.0: BS7: BS7; Taiwan: 24: 44: AS: 23.80: -121.00:-8.0: BV: -BM,BN,BO,BP,BQ,BU,BV,BW,BX; +BM,BN,BO,BP,BQ,BU,BV,BW,BX,=VERSION; Pratas Island:24: 44: AS: 20.40: -116.40:-8.0: BV9P: BM9P,BN9P,BO9P,BP9P,BQ9P,BU9P,BV9P,BW9P,BX9P; China:24: 44: AS: 40.00: -116.40:-8.0: BY: @@ -187,11 +187,12 @@ ANT,AX0,FT0Y(30)[70],FT2Y(30)[70],FT4Y(30)[70],FT5Y(30)[70],FT8Y(30)[70], LU1Z[73],R1AN,VH0(39)[69],VI0(39)[69],VJ0(39)[69],VK0(39)[69],VL0(39)[69], VM0(39)[69],VN0(39)[69],VZ0(39)[69],ZL5(30)[71],ZM5(30)[71],ZS7(38)[67], -=8J1RF(39)[67],=8J1RL(39)[67],=CE9/K2ARB(30)[71],=DP0GVN(38)[67], -=DP1POL(38)[67],=KC4/K2ARB(30)[71],=KC4AAA(39),=KC4AAC[73], -
Re: [Xlog-discussion] new user
Op zaterdag 21-02-2009 om 10:47 uur [tijdzone +0100], schreef f5gvh: Hello the list I am Francois F5GVH ,near Nevers/Magny cours (F1 circuit) new user from Xlog program and new suscriber to the discussion.52 year old,radio amateur licence from 1981 Have a good radio day Francois Hello Francois, welcome to the list. I hope you will enjoy using xlog as much as I do... Let us know if you have any questions or wishes. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Hamlib error in 1.9
Op zaterdag 14-02-2009 om 21:13 uur [tijdzone -0500], schreef John B. Egger: Thanks for your advice. Sorry for the delay in responding, but it's taken me a while to solve the issue. In the hamlib help forum, Martin (AA6E) suggested the latest CVS build of hamlib. When I downloaded and compiled it, the hamlib problem with Xlog 1.9 was solved. The country maps are terrific. Thanks for reporting back John, glad to help out. Of course now you have 2.0 out, so I'm still a step behind... Have fun with the new version! Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog-2.0 released
This release fixes some important bugs and updates all of the language translations. Upgrade is recommended. Changelog at http://pg4i.chronos.org.uk/linux/xlog.changelog Download at http://pg4i.chronos.org.uk/download/xlog-2.0.tar.gz (size 11 Megabyte) Win32 NOTE: * A first win32 binary release is distributed, which lacks the following: - There is no data exchange with other applications. - Printing has been disabled. - There is no keyer available. Reports are very welcome, especially about the hamlib functionality. I don't own a windows OS, the binary was tested on linux/wine, so YMMV. See http://pg4i.chronos.org.uk/download/xlog2.0-setup.exe Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] newline breaks logs
Op zondag 08-02-2009 om 11:53 uur [tijdzone +0100], schreef Pierfrancesco Caci: Hello, I've just noticed that if I include a newline in the remarks/comment field in fldigi, xlog will happily include the newline as it is, instead of escaping it somehow. Hence, when you close and reopen the log, it will not read log lines after the offending one. Xlog should sanitize log entries received over the pipe. Okay, see why does fldigi include newlines in log entries? I think there is enough reason to not include them... Anyway, I will fix it in the upcoming 2.0 release, because it is an easy fix ;-) Thanks for the report! xlog 1.9, fldigi 3.10 Pf Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Question on producing ADIF files
Op zaterdag 31-01-2009 om 20:43 uur [tijdzone -0600], schreef WB5BKL: When I attempt to produce an ADIF file using a number greater than 1 in the first QSO selection box, I get a file with normal headers but no QSO data - just the appropriate number of EOR entries. If I make the same attempt and keep the defaults in the Export QSO boxes (say from QSO 1 through QSO 2743), it appears to work just fine. What am I doing wrong? It is probably a bug. I will have a look and try to fix it in the 2.0 release. cln WB5BKL Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] anyone having trouble compiling 1.9?
Op zaterdag 10-01-2009 om 21:06 uur [tijdzone +0100], schreef G.Timmermann: Xlog 1.9 compiled flawlessly on sidux with kde and kernel 2.6.28-0.slh.8-sidux-amd64 x86_64. Thanks for the new version. 73, Gunter PA3HGC Thanks for testing this Gunther! Regards, Joop ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] anyone having trouble compiling 1.9?
Op zondag 11-01-2009 om 02:53 uur [tijdzone +], schreef Matt Dawson: Thanks, Joop, that's much appreciated. Just for my own peace of mind, does anyone else have this issue, or is it FreeBSD specific? It's odd, because I'm not missing gettext: [...] pkg_add hamlib-1.2.8_1.tbz pkg_add gettext-0.17_1.tbz pkg_add glib-2.16.5_1.tbz [...] and configure is being called with --with-included-gettext (which it really doesn't need; NLS is the default and you have to specifically disable it, according to the readme) but I'm still getting: The --with-included-gettext needs a intl directory in the xlog source tree. I have removed it a long time ago, because I did not see any use for it. So you should not use this flag I guess, but depend on the external gettext support. Can you please try building without with-included-gettext? checking for GNU gettext in libintl... no checking whether to use NLS... no disabled updating of the mime database Most peculiar. It's definitely there: pkg_info -W /usr/local/lib/libintl.so.8 /usr/local/lib/libintl.so.8 was installed by package gettext-0.17_1 Anyway, I shall hold off updating the port until we've decided one way or another if there's an error. Best regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] xlog-1.9 released
Op zondag 11-01-2009 om 18:19 uur [tijdzone +0100], schreef Pierfrancesco Caci: Hello Joop, all looks fine except the locator map that crashes the program, same as happened in 1.8. Now, if no one else has this problem, it may be something related to my setup: I downloaded the dsc, diff and orig.tar.gz from debian, and recompiled it for ubuntu hardy withouth changing anything. The crash happens as soon as I try to narrow down the locator map to a single band. I have the scoring and the qso before windows open, together with the main log window. Hello Pierfrancesco, the same problem has been reported by Boris 4Z5ST. However, I can't reproduce it, xlog does not crash here. So it is impossible to debug this. Boris send me a couple of gdb backtraces, there was nothing useful in the output. ik5...@penny:~ $ xlog Segmentation fault Full strace output at http://snoopy.tippete.net/~ik5pvx/xlog.trace.gz This does not tell me mucht other than a crash appearing just after opening /usr/share/xlog/maps/worldmap.jpg Pf It might be helpful if you could narrow the bug down. For example of you start xlog with only one log open, or with a smaller log to see of the crash still occurs. Thanks, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] xlog-1.9 released
Op zondag 11-01-2009 om 21:08 uur [tijdzone +0100], schreef Pierfrancesco Caci: Let's see, I tried: 4 qso on different bands, no locator field filled - crash 1 qso, no locator field - crash 3 qso, locator field filled, selecting one of the bands - crash 3 qso as above, but seleting a band that was not among the one of the qso - crash 1 qso with locator fielt - crash maybe it has nothing to do with the logs? :-) Yes, this was a good test, it has nothing to do with the logs ;-) I see that you link to hamlib.h too, in that file, let me see if disabling hamlib makes a difference... no, it doesn't :( What else can I do? Maybe I can throw in some printf in those functions and see the last one that get printed ? (debugging for dummies :-) That's what I tried with boris. Pages and pages of print outputs, but it would never crash in the middle of a function. All of the functions would exit nicely. It definitely has something to do with redrawing of the map. I am thinking about setting up a second partition and install ubuntu on that. Will keep you informed. Thanks again, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] anyone having trouble compiling 1.9?
Op zaterdag 10-01-2009 om 15:03 uur [tijdzone +], schreef Matt Dawson: On Saturday 10 January 2009 05:34:55 Joop Stakenborg wrote: anyone having trouble compiling version 1.9? I have had one report the the configure script does not work. Hi Joop, It configures and builds fine on BSD, but I am having problems configuring the build in such a way that it builds with NLS. What I have in the Makefile is: .if defined (WITHOUT_NLS) CONFIGURE_ARGS+=--disable-nls WITHNLS=@comment .else CONFIGURE_ARGS+=--with-included-gettext WITHNLS= .endif and yet I'm getting nothing at all in $PREFIX/share/locale relating to xlog. The WITHNLS= lines relate to pkg-plist handling and don't affect the build. The port builds and packages fine, however: https://tinderbox.chronos.org.uk/tb/logs/7-amd64-Exp/xlog-1.9.log Any ideas? Hi Matt, never looked at the NLS stuff, but I will take a look later this week and will send you a solution, hopefully... Regards, Joop ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog-1.9 released
Country maps have been added in 1.9! The following release will be 2.0 and focuses on translation updates (send them in), bugfixes and map updates. Let me know if any of the maps need improvements! Download: http://pg4i.chronos.org.uk/download/xlog-1.9.tar.gz Sources are 11 Megabyte now, because of the added maps. Here is the full changelog: - Changes for xlog version 1.9 - 2009/01/09 * Czech translation updates by Martin, OK1RR. * cty.dat has been updated to version 1817. * When doing a TSV export, records can now be sorted by DXCC and callsign. Sorting by callsign is especially useful for printing multiple QSO's on one label when using glabels. Thanks Stephane, F8FCE. You can determine how many QSO's per label are printed by changing the TSV export settings in the Dialogs and Windows - export page. * Patch by Jon, LA4RT so xlog can send latin-1 character to cwdaemon. * xlog can now extract the version of cty.dat, it will be displayed when showing the about dialog. * It is now possible to load logs by alphabet or by last modification date, the setting for this is in the Logs page of the preferences dialog. Thanks Pierfrancesco Caci, IK5PVX for suggesting. * The print dialog now adds a page where you can decide what columns to print. Suggested by Ed, W3NR and Boris, 4Z5ST. * Ctrl-a is no longer used for adding a QSO. Instead, you should use ctrl-w (write to log). This means ctrl-a (select all) is available for selecting text in xlog's text entries. For closing a log, you now need to use ctrl-shift-w. Thanks Len, WT6G for the idea. * The documentation has been moved to /usr/local/share/doc/xlog. The glabels template has moved to /usr/local/share/doc/xlog/glabels. * Country maps have been added. Use Options-Country map to display it. * A button next to the callsign entry has been added. When clicked it will lookup the callsign with your internet browser on your preferred server. The settings for this server is on the Info page of the preferences dialog and takes the form http://www.qrz.com/call, where call will be replaced with the callsign. Suggested by Rob, KL7NA and Boris, 4Z5ST. * It is no longer possible to view scoring for an award when the scoring window is not active. * A new macro has been added to the keyer. '~' stands for the last exchange message received. It can be used in contests where you forward the last exchange. The initial message can be set in page 2 if the preferences dialog. For more information read the manual. Thanks Jon, LA4RT for the initial patch. Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] anyone having trouble compiling 1.9?
anyone having trouble compiling version 1.9? I have had one report the the configure script does not work. Thanks, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] The problem with ctrl-a (suggestions?)
Op woensdag 10-12-2008 om 18:25 uur [tijdzone +0100], schreef Pierfrancesco Caci: ctrl-w is consistently a close file/window all throughout gnome, do you really want to get into this? I currently don't see a better solution. Ciao, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Re: QSL info
Op maandag 08-12-2008 om 21:17 uur [tijdzone +0200], schreef Boris Sorochkin: I just realized that all of my previous QSL send/receive info disappeared from the log. Fortunately I have another database that handles QSL's. Have no idea how to back-trace this. You must mean debug, not backtrace. Backtraces are only useful with crashes. You may have used the log-editor and removed the QSL column, that's the only possibility. I never had this kind of report, so let's consider this 'human failure'... ;-) Is it possible to add some more QSL info handling options like these: 1. mass fill of QSL sent field. 2. instead X in s/r use something like: B -buro, D - direct, E - eQSL, O - other. 3. probably make additional field for SWL conformation since xLog can handle different awards that counts SWL conformation. 4. probably add QSL manipulation dialogue with these features. I think this may be useful. Okay, all nice ideas but not very urgent. You could consider using one of the free columns for QSL handling. I will add your stuff to the version 2 todo's. Boris. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] The problem with ctrl-a (suggestions?)
As you guys may know, ctrl-a is used by xlog to add a QSO to the log. The problem with this is, the same key combination is also used by all of the text entries on xlog, it means select all. You would for example use it when copying text from one field to another (copy/paste): ctrl-a - ctrl-c, move to another field, ctrl-v Right now this does not work, ctrl-a will always add a QSO. So I am thinking of changing Add QSO and use some other key combination. Here are some thoughts: Ctrl-i (short for Insert QSO, you may need 2 hands for this) Ctrl-Shift-a (can be used with one fingerstroke, but may be to complicated) What do you think? Anyone have another suggestion? Thanks, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] The problem with ctrl-a (suggestions?)
Op dinsdag 09-12-2008 om 11:39 uur [tijdzone -0800], schreef Leonard J. Umina: Writelog uses Ctrl-w which might be Write QSO to move you to the QSO entry dialog. This is easy to hit with your left hand. As you make an entry you can tab to the fields which works well. When you hit ENTER the QSO entry is transferred to the log. Thanks Len! ctrl-w seems like a good idea... A related feature I've tested is a hot key in the entry window which is the space bar. I know it sounds a bit crazy, but I wrote some logging software once and it worked really well. Since nothing requires spaces except a comment field if you hit the space bar from any field the software would clear all fields and abort the entry. After you get used to it its VERY fast - especially for search and pounce and pileups. You can enter the call into the form - if it comes up a dupe you hit space bar and its gone, resetting to a blank interface. It needs to be active in all fields where space is not permitted - so if you start to copy part of a previous exchange you can abort as soon as you realize the callsign is a dupe. Okay, sounds interesting. But also sounds a bit risky. Maybe I should give it a try in one of the contests and see how it works. Tab and shift tab should move you between the entry fields. Yes, that is how it works in xlog. Does anyone know if there is a way to use a USB LPT port for CW Keying? I added one and I still get an error message from the cw deamon.That's my hangup right now. My linux PC has no parallel port which is how I key with writelog. I'd very much like to get away from Windows completely. Oh boy, the next best thing, USB LPT ports... ;-) I guess it should have some kind device name. The USB serial ports are called /dev/ttyUSB0, /dev/ttyUSB1, etc. Maybe there is something similar for LPT ports. When you plug the device into the computer, do you see anything reported in the system log when running linux (use dmesg for this)? /Len WT6G Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] The problem with ctrl-a (suggestions?)
Op dinsdag 09-12-2008 om 15:31 uur [tijdzone -0500], schreef Ed: Good idea, but Ctrl-w is also close log. But I would prefer the Ctrl-w to add the qso. I never close the log, I always exit xlog, so the close could be moved to another key (Ctrl-i ?). Yes, we need to move some keys around! It will probably be in the next release.. Ed W3NR Thanks, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Re: locator map - bug
Op vrijdag 05-12-2008 om 15:53 uur [tijdzone +0200], schreef Boris Sorochkin: I get segmentation fault when trying to change band in locator map dialog. Also reported on Russian forum cqham.ru Hello Boris, one question, do the crashes also occur when the scoring window is open? Is it possible extend usage of the map? 1. add gray line 2. add layers of locators, prefixes, CQ and ITU zones view? Yes of course, this is for version 2.0 or later. It would help if you know any freely available maps without copyright. Drawing my own maps is to much work. The next version (1.9) will have contry maps added. Most of these maps come from the CIA world fact book because they are free. Boris, 4Z5ST. Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Re: locator map - bug
Op maandag 08-12-2008 om 19:02 uur [tijdzone +0100], schreef Pierfrancesco Caci: did you check Wikipedia Commons? http://commons.wikimedia.org/wiki/Map Plenty of maps here, all with reasonable licenses. Yes, wikipedia is one of my sources. In fact, most maps they use are from the CIA factbook. They distribute some maps under the GFDL license, which I can't use because it is GPL incompatible :-( They also use the Creative commons license, another pain in the ass. Regards, Joop ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Re: locator map - bug
Op maandag 08-12-2008 om 20:19 uur [tijdzone +0200], schreef Boris Sorochkin: Hi, Joop, The crash occurs both if scoring window is open or closed. Thanks Boris, It doesn't crash here, so I would be interested in receiving a gdb backtrace. Do you know how to do this? Boris. Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Re: locator map - bug
Op maandag 08-12-2008 om 20:30 uur [tijdzone +0200], schreef Boris Sorochkin: #0 0xb79824a6 in ?? () from /usr/lib/libgobject-2.0.so.0 #1 0xb79728a8 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #2 0xb7972acd in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #3 0xb79683d4 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #4 0xb795ac4b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #5 0xb7971095 in ?? () from /usr/lib/libgobject-2.0.so.0 #6 0xb79727ac in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #7 0xb7972c26 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #8 0xb7bd3649 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #9 0xb7bd4f7f in gtk_combo_box_set_active_iter () from /usr/lib/libgtk-x11-2.0.so.0 #10 0xb7bd507e in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #11 0xb79683d4 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #12 0xb795ac4b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #13 0xb7971095 in ?? () from /usr/lib/libgobject-2.0.so.0 #14 0xb79727ac in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #15 0xb7972c26 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #16 0xb7d80477 in gtk_widget_activate () from /usr/lib/libgtk-x11-2.0.so.0 #17 0xb7c72f70 in gtk_menu_shell_activate_item () from /usr/lib/libgtk-x11-2.0.so.0 #18 0xb7c74b4d in ?? () from /usr/lib/libgtk-x11-2.0.so.0 ---Type return to continue, or q return to quit--- #19 0xb7c6b4fb in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #20 0xb7c65036 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #21 0xb79593c9 in ?? () from /usr/lib/libgobject-2.0.so.0 #22 0xb795ac4b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #23 0xb7970d3d in ?? () from /usr/lib/libgobject-2.0.so.0 #24 0xb797262b in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #25 0xb7972c26 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #26 0xb7d7a33e in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #27 0xb7c5db4c in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0 #28 0xb7c5eef7 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 #29 0xb7af550a in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #30 0xb78c86f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #31 0xb78cbda3 in ?? () from /usr/lib/libglib-2.0.so.0 #32 0xb78cc2c2 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #33 0xb7c5f3a9 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #34 0x080521c0 in main (argc=20, argv=0x1) at main.c:557 This does not help me very much. I can see that it crashes when a new band is selected, that's all. I will get back to you in a private mail. Joop ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] cwdaemon and ptt
Op maandag 01-12-2008 om 19:19 uur [tijdzone -1000], schreef Alastair Couper: I was using xlog this last weekend in CQWW, and for the first time had tried to get ptt going, as I have always used a foot switch instead. I know that my serial port interface, as shown in the docs, is working OK. The keyer works fine, and the ptt function works fine in other applications. But with cwdaemon, I find that when a message is sent, the ptt turns on only for a brief instant and turns off again, even though the message is still being sent. If the ptt delay parameter is set to 50ms, then ptt will stay on for the first word of an Fn message (if it is at high speed). If I type in the keyer window, the ptt clicks on very briefly with each keypress, but does not stay on long enough to actually encompass a character such as 0. I tried using tlf, which allows the use of the ALT-P command to toggle the ptt. If I hit ALT-P during a message, the ptt stays on while the message is sent. Hitting ALT-P again turns it off. So this ptt behavior seems to be in cwdaemon, and it isn't useful as it stands. Does anyone else see this? I am not sure what the intended behavior is. Al nh7o Hoi Al, sorry for the late reply. It looks like PTT isn't working at all (* anyone on the list that can confirm this? *). When I programmed it, I did not have a setup available that uses PTT. With my kenwood TS-870S I don't need it. I looks like I need to have another look at the PTT code. Currently I am a little hooked up on other projects, so I can't make any short-term promises, sorry. Regards. Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Re: Xlog Printing - suggestion
Boris Sorochkin wrote: I agree, flexibilty is needed and that was in the old method. Okay, I will look into the old code and re-add it to xlog. I like Boris's idea, but I'm just an end user, not the programmer...hi Thanks for looking into this Joop. Most welcome! Ed W3NR Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Xlog Printing
Op donderdag 04-12-2008 om 12:56 uur [tijdzone -0500], schreef Ed: Boris Sorochkin wrote: Hi! There is some problem with printing the some page of the log. Last records of the page overflow the page and printed on first rows of the page instead shifting to the second page. Result depends of number of pages printed. Attached an example. Boris, 4Z5ST. Hello guys, the attachment by Boris was to large for the mailing list. There is a limit of 40 kB. Same as the results here. Thanks for taking the time to verify what I saw here. I would have attached a screenshot or a test file, but wasn't certain that was allowed. You could try the following things. - Make sure you have a suitable paper size. See Log - Page setup from the menu. You might want to try landscape. - When doing the actual printing, select a suitable scale (0-100%) on the second page of the print dialog, so the log fits on paper. I believe this is also descibed in the handbook. Make sure you read it. Thanks agn 73 Ed W3NR Let me know if this fixes things for you. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Xlog Printing
I set up paper size A4. In landscape mode it works better, but on several pages I get a log line below the foother of the page. Problems in portrait mode. also results differ between postscript and pdf mode. I would send example, but they are larger then 40k. seems like if some sequence in notes brakes lines or pages. Is it possible at all? Well, in previous versions you could show/hide columns so the log would fit on paper. Maybe I should start thinking about printing log entries over multiple lines. This way we will always have space enough. Any suggestions? I will try to fix this issue for the next release. Boris. Thanks Ed and Boris for the report. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] netkeyer.c character set fix
Op woensdag 26-11-2008 om 20:39 uur [tijdzone +0100], schreef Jon Kåre Hellan: Hi cwdaemon can send some latin-1 characters outside ascii, but expects to see latin-1. GTK applications these days, including xlog, use utf-8 internally. Making unixcw unicode aware sounds rather pointless, so I made the fix below to netkeyer.c. I had to convert to upper case before converting to latin-1 because cwdaemon fails to convert when character is non-ascii. Thanks Jon, patch has been added to CVS. Jon LA4RT Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Rotor Control from Xlog
Op woensdag 26-11-2008 om 09:18 uur [tijdzone -0800], schreef Rob Frohne: Hi Joop, et. al., Has anyone considered putting rotor control into Xlog. It would be nice to have the software have the ability to turn your antenna in the correct direction for the person you are talking with. Hamlib supports rotor control. Sounds like a good idea, but I will target it for the 2.0 release series. I guess we need some kind of dialog for this. Maybe this dialog should suggest what the beam heading should be (depending on what the callsign is) and we can either change it or click on the 'rotate' button right away. 73, Rob Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Keyer and Orion
Op zondag 21-09-2008 om 11:40 uur [tijdzone -0400], schreef John B. Egger: Does anyone on the list use the Xlog keyer with the Orion? If so, I could use some advice! Although the Orion manual refers to the Aux/IO jack as accepting CW from an external keyer or computer generated CW (like the CW keying output from popular contest logging software) using the computer sound card, it looks as if Xlog's keyer works through the parallel or serial ports, not the sound card. The Orion Programmer's Manual shows how its serial port is wired, and cwdaemon provides a schematic for the computer's serial port (see below), but I'm stuck here. The Orion's serial port shows this: 1, N.C.; 2, Serial Data Out; 3, Serial Data In; 4, N.C.; 5, GND; 6, N.C.; 7, RTS (in); 8, CTS (out); 9, N.C. Hi John, you must be confused. Your orion's serial port should be used to communicate with the PC's serial port through applications that use hamlib (see http://hamlib.sourceforge.net/app.html for a list of applications). cwdaemon uses a serial or parallel port to switch the keyer input of your transceiver, that's the jack where the straight key goes. In case your transceiver does not transmit automatically when the key goes down, a PTT switch is provided. Which of these corresponds to CW out to TRX and to PTT out toTRX on the cwdaemon schematic? And will wiring the serial connection using this circuit prevent hamlib from reading transceiver data? Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] How about a callsign server lookup button to open the page in your browser?
Op donderdag 11-09-2008 om 10:16 uur [tijdzone -0700], schreef Rob Frohne: Hi Joop, et. al., I'm wondering if there is a good reason why we can't have a button that will allow you to automate the process of copying and pasting the call sign of the station you are working into Firefox (or whatever your web browser is) so you can see the data on a call sign server like qrz.com or hamcall.net, or any of the other call sign servers. I realize having a URL that is hard coded into the program makes it very susceptible to changes webmasters make to things. To get around this, we could have a preference setting that would allow you to construct a URL, where CALL would be replaced with the call of the station you are looking up. For example the URL for qrz.com for my call (kl7na) is: http://www.qrz.com/kl7na What do you all think of this idea? Hello Rob, sorry for the late reply, been out of the country. Your idea sounds feasible, especially of we don't hardcode it. This way we can use any server. I was thinking of a small clickable button next to the callsign field, which will start your preferred web-browser. I can add it to the next release. 73, Rob, KL7NA Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Install help
Op maandag 01-09-2008 om 16:10 uur [tijdzone -0400], schreef Stewart Whitehouse: Hi, I tried to install xlog 1.8.1 from tar but can not find it. I still show 1.6.2 installed. synaptic shows that 1.6.2 is the latest version and the version installed. I did the tar install from Desktop. I am running UBUNTU and still a linux novice. Any help will be appreciated. Stew ke4yh Hi Stewart, Open a terminal window and become root using the 'su' command. First of all, you need to uninstall your ubuntu xlog package by typing 'apt-get remove xlog' in a terminal. You don't want conflicting xlog versions. Next, install the packages needed for building xlog: 'apt-get install build-essential libgtk2.0-dev libhamlib-dev'. As a normal user unpack the xlog source tree (the tarball) somwhere in your home directory: 'tar xvzf xlog-1.8.1.tar.gz' and follow the instructions in the INSTALL file, unpacked in xlog-1.8.1/INSTALL. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Hamlib in 1.8: No QSO-pane data
Op zaterdag 30-08-2008 om 19:35 uur [tijdzone -0400], schreef John B. Egger: I just updated Xlog 1.7 to 1.8. Hamlib provides a frequency readout in my statusbar, as I requested, but Ctrl-K adds no information from the transceiver to the QSO pane (only the date and time). I'm using the same parameters (selection of radio and device) as in 1.7 (which I still have installed on a laptop, so comparisons are easy). The ChangeLog didn't seem to show anything related to this. Anyone else experiencing this, or have I misconfigured 1.8 somehow? I compiled it from the .tar.gz file, since I use a Debian (Kubuntu-based) system. Everything looks fine, except that Ctrl-K doesn't pull in the data. Rob, KL7NA reported the same problem to me in a private mail. I will have a look at it later this week and when fixed, will make a 1.8.1 release. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] deleting a log
Op zaterdag 30-08-2008 om 09:03 uur [tijdzone -0500], schreef Dennis Ledford: I created a log name and want to remove it. How do I delete a log? Thanks, Den rm /path/to/log.xlog By default your logs are in $HOME/.xlog Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog-1.8 uploaded
Short changelog: xlog now uses native GTK+ printing. Searching capabilities have been improved. Locator scoring has been added, both with a list and a map. Log import has been improved. Portuguese and Italian translations have been added. There were several fixes and improvements Beware, the config file and format has changed, xlog needs to be reconfigured! See the ChangeLog for details. Download URL: http://pg4i.chronos.org.uk/download/xlog-1.8.tar.gz Debian packages will follow after Lenny is released, sorry. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Problem using the remote logging capabilities with KPSK
Op maandag 30-06-2008 om 13:24 uur [tijdzone -0500], schreef Joshua Wood: Hi Joop, Sorry to cause confusion. I found out that I was doing it wrong. xlog doesn't crash if you open a new log first... I used it to great effect this weekend, making several contacts. You're correct about kpsk being a dead project, although I very much hope to bring it back to life. As far as xlog, I'll be happy to submit a patch that will handle this situation gracefully (ie, pop up an error about not having a log open, or some such.) I'll get back to you once I've got it coded. Aha, now I understand what's going wrong... ;-) Should be easy to fix. I will have a look at it! Thanks so much for this wonderful little piece of software! Regards, Joshua Wood Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Problem using the remote logging capabilities with KPSK
Op donderdag 26-06-2008 om 18:36 uur [tijdzone -0500], schreef Joshua Wood: Hi, I've built xlog 1.7 on Slamd64 -current (call it 12.1 if you'd like.) I'm wanting to use it this weekend for Field Day. The problem I'm running into is, xlog segfaults when I send it a qso from KPSK. I've included a backtrace on the segfault below: (gdb) backtrace #0 0x0043f7d5 in addtolog_or_qsoframe () #1 0x00440ef9 in remote_entry () #2 0x2abe9fda802b in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x2abe9fda78d4 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #4 0x2abe9fdaabbd in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x2abe9fdaaeb7 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #6 0x2abe9e52b853 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0 #7 0x0040e159 in main () Any ideas on what could be causing this? Hi Joshua, I have downloaded kpsk-1.2rc2, but it won't compile on my system. I have checked the kpsk mailing lists to see if there is any activity, but they only seem to contain spam. I would like to suggest that you use gmfsk (works fine with xlog) or any of the other digital modem programs. Since my development time is limited I am ruluctant in supporting dead projects like kpsk. Also, backtraces don't help me much without line numbers. After compilation, start xlog from the xlog source tree when using gdb. 'gdb src/xlog'. It would be nice to seen that the content of the message buffer is in addtolog_or_qsoframe()... After the crash type: 'p entry'. Thanks, JK Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] hamlib freq display
Here is a minor issue, one that was momentarily confusing to me (v1.7): In Preferences - Hamlib, the last item says Round frequency to -N- characters For my rig (TT Orion), what really happens is that the frequency display is rounded to 10^N Hz. In fact, as N increases, the number of characters decreases. It might be clearer to say something like Round frequency at digit -N- (0 = 1 Hz, 1 = 10 Hz, ...) Your tip for the day! Great tip, thanks! 73 Martin AA6E -- Martin Ewing, AA6E [EMAIL PROTECTED] +1-203-315-5160 Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] disabling hamlib
On Sun, 6 Apr 2008 15:49:25 +0200 (CEST) Oh Thats bad news ( I've installed hamlib 1.2.7 and getting checking for GNOMEPRINT... yes checking for HAMLIB... configure: error: Package requirements (hamlib) were not met: No package 'hamlib' found /usr/local/lib/libhamlib++.so /usr/local/lib/libhamlib.so I'm not sure if I've got any of the older versions of xlog . Please read the INSTALL file in the source tree... -- Best Wishes Richard Bown ~ Registered Linux User 365161 OS Mandriva x86_64 2008.0 Kernel 2.6.22.9-1mdv HAM Callsign G8JVM : Locator IO82SP QRV all bands 80mtrs to 3 cms ,( non WARC ) http://www.software-radio.org.uk A computer is like a Native American Indian teepee, it has no gates, no windows and has an apache inside. Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] disabling hamlib
Op zondag 06-04-2008 om 19:22 uur [tijdzone +0100], schreef Richard: OK slapped wrists Joop. I've had to add a symlink on one of the libs, but what was more worrying was it completely hung gnome for the first time it was run. Did you have hamlib enabled? There is no particular reason why xlog should hang your desktop unless you load very large logs maybe... It seems to be behaving after a reboot Did you cheamge xlog's configuration after the reboot? thanks Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] v1.7 Bug
Op zaterdag 22-03-2008 om 15:14 uur [tijdzone +0200], schreef Harry Popov: Hi, Today I received update of XLog to my Debian Lenny. Alt-D, Alt-U, Alt-E fullfill corectly the date and time fields. But double click in these fields does nothing. It worked before. I think it is a bug. Some of us still use the mouse. :) Hello Harry, I can't remeber programming double-click in any of these fields. You need to click on the button next to it. I am using the case to ask. Can I suggest counting QRA squares on VHF bands. Usefull feature for all us VHF/UHF DXers. See settings-dialogs and windows-scoring, check the last checkbox. There is currently no way to display a list of locators worked. maybe in the next release. 73, Harry LZ1BB Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Log as diary
Op dinsdag 26-02-2008 om 18:21 uur [tijdzone -0500], schreef Martin Ewing AA6E: On the user level, I can imagine a button or menu item on the xlog panel that says Add Special Remark (or some such). It could bring up a simple text box for you to type an arbitrary note. Then a Save button enters the text (with date/time) into the database. (You choose the db technology!) The New Special Remark pane could be an alternative to the New QSO pane. Sorry for the late reply, recovering from a flue attack. Okay, but we already have a remarks field in the log which we could use for this. I am thinking of using a special callsign (e.g. NOTE or TAG) to tag a QSO for 'Special Remark'. This way we don't need to add an extra field to the QSO Frame or an extra menu item. Now, how does the log viewer panel look with this feature? It shows QSOs as usual, but a special remark needs to show between QSOs, if not in a separate pane for remarks. It could be a text line that crosses the usual QSO columns, and shows in a distinctive manner - italics, green color, whatever. It's probably enough to show the first text line of the note. If it is longer, you would select it for viewing bringing up the full text entry/edit dialog, which would let you read, edit, or delete the remark. The QSO list is divided into a number of columns which can not be altered once it is configured. You can add/delete columns (which the log-editor does), but when displaying the list they have a fixed number of columns. However, colorizing a QSO in the list is no problem. We could display it when double-clicking the QSO in a special window, but it would also be visible through the remarks field. The tagged QSO would be ignored when doing an export. The remark entry wants to be keyed by creation date, most likely, and should be sorted along with QSOs by date. Nice, but not essential: an ability to search on contents. Okay, no problem. As you suggest, you could use a pop-up like word processors do. You could annotate a QSO and indicate by a colored flag or asterisk. (Or possibly between QSOs.) Click on it and you can view, edit, or delete the note. The advantage is that it needs little screen space and it minimizes the violence to your current layout. However, I'm not so much interested in annotating a single QSO (although that could be useful) - I want to say that I installed a new antenna, or something like that that applies to many future QSOs. Yes, I can see the reason for adding this. It would be quite helpful. Even though it sounds fairly simple, I know this might be some work. I just wanted to put the idea out there for consideration. Thanks for the suggestion. Feel free to comment on my idea for implementing this into xlog. 73 Martin AA6E Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog-1.7 released
Version 1.7 has been released, this release has been sponsored by Stephane, F8FCE. We now have many more scoring possibilities added. here is the ChangeLog: * Scroll to the last QSO when the log is automatically loaded and there are more than 1000 QSO's. Thanks Jon LA4RT for reporting. * Display of the about dialog has been fixed. * TSV export for glabels has been fixed. The exported columns did not match the ones in the 'Settings-Dialogs and Windows-export' setting. Reported by John, K3GHH. * We no longer use tiny fonts for the remarks entry and when importing logs. It is easier in the eyes. Reported by Hein, PA0NQ. * The info page of the preferences dialog now updates QRA locator when latitude/longitude is changed and vice-versa. * Xlog now uses the functions provided by hamlib for calculating distance and bearing. * The old behaviour has been restored when a DXCC country has been confirmed, country worked count will be set to 0. * The same behaviour has been added for all the other awards, so if a country has been confirmed, the count is set to zero. Otherwise, the number of countries will be displayed. * A new key combination has been added, Control-Shift-A will add a QSO and fill in defaults for the next QSO. It is the same as using Control-A followed by Control-k. This is especially useful in contests. Requested by Dominique, HB9HLI. * The following changes by Stephane Fillod, F8FCE: * WAS, WAZ, IOTA and locator scoring have been added. * Xlog now knows how to import IOTA contest logs and fills in the AWARDS field. * It does work also with any ARRL contest where the state is exchanged. * EDI import is now capable of filling in BAND and POWER fields. * EDI import fixed when importing utf-8 dates. * EDI export: take into account the change of wwl() logic. * EDI export properly generates CRLF eol (according to official format). Download from http://pg4i.chronos.org.uk/download/xlog-1.7.tar.gz Please send bug reports to the list, as I will be away for the next 10 days... The Debian package will need to wait until I'm back, sorry. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] New log
Op vrijdag 25-01-2008 om 23:03 uur [tijdzone +], schreef John B. Egger: I'm trying to create a new log, Log2008, and insert into it the 30 or so QSOs I've made in calendar 2008 but entered in Log2007. What's the best way to do this? Is there a way to copy only selected QSOs from one log to another? Hi John, Copy log2007.xlog to log2008.xlog then grab a text editor and delete all of the QSO's you don't want. That's how I would do it. Just make sure the header stays intact. I merged Log2008 and Log2007, but can't figure out how to delete all of the QSOs that took place in 2007. I tried ADIF export (of only the 2008 QSOs) but the import into Log2008 didn't get all of my fields. Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] compiling problems.
Op zaterdag 12-01-2008 om 00:13 uur [tijdzone +0200], schreef Boris Sorochkin: I am trying to configure xlog 1.6.2 and I get error: checking for GTK... configure: error: Package requirements (gtk+-2.0 = 2.12.0) were not met: No package 'gtk+-2.0' found but it's installed. Any ideas? ___ Please install the GTK+ development package. Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Feature request
Op vrijdag 21-12-2007 om 08:07 uur [tijdzone +0200], schreef Hylton Conacher (ZR1HPC): Not having used the program but I would make Ctrl-D the key combination to use to insert default details. It's not that simple. Ctrl-k is uses for inserting defaults, clicking on all of the available buttons in the QSO frame and retrieving information from your rig. So it isn't used for defaults alone. My 2c and Merry Christmas to all Thanks and happy christmas, 73 de ZR1HPC Hylton Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Feature request
Op dinsdag 18-12-2007 om 22:45 uur [tijdzone +0200], schreef Boris Sorochkin: Hi Joop! In discussion on www.cqham.ru about xlog people figured out some nice features that might be very useful. I want ask if it's possible to implement some of them in future. enable sending call sign from xDx to xlog I want to do it the other way. xdx will ask xlog if a spotted callsign is in the log and then colorize the dx-spot accordingly. For example make new countries red. qrz.com lookup. probably integration with external program like callgit or use it's source. Yes, this is a good idea. Several people have asked about this. integration or use of dxcc program (it returns dxcc info for call sign) I don't see why this is helpful. xlog already uses cty.dat for DX information. language select for name, QTH and REMARKS fields - some Russian and Israeli hams was interested in writing QSO data in native language (it's might be useful when you have to change tree or four different layouts). That's not possible i'm afraid. You should start xlog in a certain language environment. There is no possibility for linux applications to change language while the program is running. On the other hand, I am not a language guru... ;-) feature to define custom scoring for different contests and awards. This is planned for a future versions. It's a lot of work, but basically I want to use some kind of template for defining awards or contests. Great regards, Boris, 4Z5ST Thanks, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] TSV export [solved, sort of]
Op zondag 09-12-2007 om 22:00 uur [tijdzone +], schreef John B.
Egger:
I don't know where the problem lies with my installation, but this
provides the practical solution that seems to work!
Here is the replacement src/logfile/labels.c that should fix your
reported issues...
Drop into the xlog source tree, recompile and reinstall.
--John K3GHH
Joop PG4I
/*
xlog - GTK+ logging program for amateur radio operators
Copyright (C) 2001 - 2007 Joop Stakenborg [EMAIL PROTECTED]
This file is part of xlog.
Xlog is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
Xlog is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with xlog. If not, see http://www.gnu.org/licenses/.
*/
/*
* labels.c - support for glabels, export some fields in a TAB separated way
*/
#include stdlib.h
#include stdio.h
#include string.h
#include glib.h
#include logfile.h
#include preferences.h
#include wwl.h
/*
* file fields
*/
static gint labels_open (LOGDB *);
static void labels_close (LOGDB *);
static gint labels_create (LOGDB *);
static gint labels_qso_append (LOGDB *, const qso_t *);
static gint labels_qso_foreach (LOGDB *,
gint (*fn) (LOGDB *, qso_t *, gpointer arg), gpointer arg);
extern preferencestype preferences;
const struct log_ops labels_ops = {
.open = labels_open,
.close = labels_close,
.create = labels_create,
.qso_append = labels_qso_append,
.qso_foreach = labels_qso_foreach,
.type = TYPE_LABELS,
.name = Labels,
.extension = .labels,
};
/*
* open for read
*/
gint
labels_open (LOGDB * handle)
{
FILE *fp;
fp = fopen (handle-path, r);
if (!fp)
return -1;
handle-priv = (gpointer) fp;
return 0;
}
/*
* open for write
*/
gint
labels_create (LOGDB * handle)
{
FILE *fp;
fp = fopen (handle-path, w);
if (!fp)
return -1;
handle-priv = (gpointer) fp;
return 0;
}
void
labels_close (LOGDB * handle)
{
FILE *fp = (FILE *) handle-priv;
fclose (fp);
}
gint
labels_qso_append (LOGDB * handle, const qso_t * q)
{
FILE *fp = (FILE *) handle-priv;
gint kms, miles, l, result;
if (preferences.saveastsv2[0] == '1')
{
if (q[DATE]) fprintf (fp, %s\t, q[DATE]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[2] == '1')
{
if (q[GMT]) fprintf (fp, %s\t, q[GMT]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[4] == '1')
{
if (q[GMTEND]) fprintf (fp, %s\t, q[GMTEND]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[6] == '1')
{
if (q[CALL]) fprintf (fp, %s\t, q[CALL]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[8] == '1')
{
if (q[BAND]) fprintf (fp, %s\t, q[BAND]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[10] == '1')
{
if (q[MODE]) fprintf (fp, %s\t, q[MODE]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[12] == '1')
{
if (q[RST]) fprintf (fp, %s\t, q[RST]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[14] == '1')
{
if (q[MYRST]) fprintf (fp, %s\t, q[MYRST]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[16] == '1')
{
if (q[AWARDS]) fprintf (fp, %s\t, q[AWARDS]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[18] == '1')
{
if (q[QSLOUT]) fprintf (fp, %s\t, q[QSLOUT]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[20] == '1')
{
if (q[QSLIN]) fprintf (fp, %s\t, q[QSLIN]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[22] == '1')
{
if (q[POWER]) fprintf (fp, %s\t, q[POWER]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[24] == '1')
{
if (q[NAME]) fprintf (fp, %s\t, q[NAME]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[26] == '1')
{
if (q[QTH]) fprintf (fp, %s\t, q[QTH]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[28] == '1')
{
if (q[LOCATOR])
{
if (preferences.tsvcalc == 0)
fprintf (fp, %s\t, q[LOCATOR]);
else
{
result = wwl (preferences.locator, q[LOCATOR], kms, l);
if (result == 0)
{
if (preferences.units == 1)
fprintf (fp, %s\t%d\t%d\t, q[LOCATOR], kms, l);
else
{
miles = (gint) (kms / 1.609);
fprintf (fp, %s\t%d\t%d\t, q[LOCATOR], miles, l);
}
}
else
fprintf (fp, %s\t%d\t%d\t, q[LOCATOR], 0, 0);
}
}
else
{
if (preferences.tsvcalc == 0)
fprintf (fp, \t);
else
fprintf (fp, \t\t\t);
}
}
if (preferences.saveastsv2[30] == '1')
{
if (q[U1]) fprintf (fp, %s\t, q[U1]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[32] == '1')
{
if (q[U2]) fprintf (fp, %s\t, q[U2]); else fprintf (fp, \t);
}
if (preferences.saveastsv2[34] == '1')
{
if (q[REMARKS]) fprintf (fp, %s\t
Re: [Xlog-discussion] TSV export [solved, sort of]
Op zondag 09-12-2007 om 22:00 uur [tijdzone +], schreef John B. Egger: PS: I just discovered that if I mark for export QSL IN and Locator, which are NOT in my log but are just before the two desired but missing fields, saveastsv2 takes the form I want (eight 1, three 0, 1, three 0, and three 1) and the export works perfectly! I get not QSLIN and Locator, but the fields that follow them, which I really want: Power and the first user-defined field. I don't know where the problem lies with my installation, but this provides the practical solution that seems to work! Thanks John for trying this. It is probably an error in xlog. I will give it another try later and keep you posted. --John K3GHH Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] UTC?
Op dinsdag 04-12-2007 om 01:11 uur [tijdzone -0500], schreef John L. Wilkerson Jr.: The log displays UTC for a QSO. How do you set UTC? From what I can tell, it just uses system time. In order to actually get UTC time, you need to set your system clock to UTC. Naturally, then this will mess up time stamps on files and such. What distro do you have? There should be a system administration tool to tell your OS whether you have set the system clock to UTC or local timezone. Next, you need to tell it in which timezone you are. Am I missing a setting somewhere, or is this a design flaw? Please read you distro's documentation, or ask at some support forum or mailing list if you can't find a solution. It is not a design flaw... --John Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xdx-2.4 released
* Added automatic country lookup by Emanuele IZ0ETE. In order for this to work you need to enable the country column in the preferences dialog. * With this release visible columns need to be reconfigured. * Portuguese translation added. Thanks to David, CT1DRB. Downloaf from http://pg4i.chronos.org.uk/download/xdx-2.4.tar.gz Regards, Joop ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] xlog-1.6.1 released
This is a bugfix release which fixes several scoring and hamlib issues. * Compilation fixes. * Fix appearance of the scoring window. Thanks to flavio, IK3OCD and Boris, 4Z5ST for reporting. * Fix power retrieval from the rig. Thanks Pat, KB8PYM and Martin, AA6E for the report. * Some fixes for EDI and EDITEST file format, patch by Stephane, F8FCE. * Some changes to the S-meter coding which will hopefully make it more accurate. * If there is no cummunication with the rig, hamlib will be stopped and a warning dialog will be shown. * The wac scoring is now updated correctly when a log is closed. * Country worked count would be set to 0 whenever you would have at least one confirmed QSO with that country. Patch by Stephane. * When using the bandoptionmenu the band would sometimes be truncated. * WAC scoring will now get updated when importing a log. * Include the old wwl code again because of license problems with the new code. * All of xlog is now GPL version 3. Download: http://pg4i.chronos.org.uk/download/xlog-1.6.1.tar.gz Thanks to all who have reported bugs! Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] v1.6 adventures comments
Op donderdag 15-11-2007 om 21:47 uur [tijdzone -0500], schreef Martin Ewing - AA6E: Alex was spot on about the logic needing to be in the transceiver backend. I had forgotten all about this, but the Orion backend (my backend!) seems to be set up correctly. I coded and tested the following snippet that retrieves the current output power in watts: status = rig_get_level(my_rig, RIG_VFO_CURR, RIG_LEVEL_RFPOWER, pwr); /* pwr (actually, pwr.f) is relative: 0.0 - 1.0 range */ status = rig_power2mW(my_rig, mwpwr, pwr.f, freq, mode); /* mwpwr (int) will be set to the actual demanded output power in milliwatts (0 - 10 for the Orion). Freq and mode are current valid rig vfo setting and operating mode. */ Yes, xlog was using both functions, but because of a wrong RFPOWER level function for the ts870, I multiplied it by 2.56... It is fixed in CVS now. There will be an updated xlog soon. I don't know what xlog is doing, but it is not this. So I think we have an actual bug report. 73 Martin AA6E Thanks, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Scoring window
Op maandag 19-11-2007 om 01:27 uur [tijdzone +0200], schreef Boris Sorochkin: Hi all! I have a small problem with scoring window. If i close Xlog while scoring window is opened and then reopen xlog the scoring window does not appear again, but the 'v' near it's position in options menu appears. there is no such problem with worked before window.. Hi Boris, that's right, appearance of the scoring window is buggy. I will fix it as soon as I can. thank you, Boris 4Z5ST Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Worked before window
Op maandag 19-11-2007 om 00:38 uur [tijdzone +0100], schreef Krister Eriksson: Sometimes the translation of a software gets som strange - and funny results. In my case the window worked before I assume it is meant in english, this is translated to swedish for a thing that is broken and it did worked before, or was in function before ... (in swedish: Fungerade förut) How can I change this? I am not using the very latest version. Hi Krister, the compiled language file is in /usr/local/share/locale/sv/LC_MESSAGES/xlog.mo, you need to replace it with your own version. In order to do so, use po/sv.po from the xlog source tree and read it with either kbabel (KDE based) or gtranslator (GNOME based). Modify the text inside kbabal/gtranslator and compile the sv.po file into a sv.gmo message catalog. Copy this file to usr/local/share/locale/sv/LC_MESSAGES/xlog.mo. 73 / SM5KRI Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] v1.6 adventures comments
Op woensdag 14-11-2007 om 23:07 uur [tijdzone -0500], schreef Martin Ewing - AA6E: Well, I upgraded to Fedora 8 mainly to try xlog 1.6. (Bad move, but that's a story for another day.) The good news. Xlog compiles and installs correctly. First run gave a horrible crash dump. After some head scratching, I turned on my rig (Orion) and tried again. All is well this time! This was a Hamlib/Orion problem. (I'm the HL Orion maintainer.) It does not seem to happen with other choices for rig type. Although the software turns to molasses if there's no response on the serial port. I am using Hamlib from CVS. I found and fixed one problem -- invalid return when get_info returns null. Now xlog does not crash when the rig is off, but xlog hangs up with a mostly uninitialized window until you turn the rig on. I'll look at it some more. Maybe Hamlib itself should have a better way to signal if there is no rig available. A non-blocking serial read might be a good idea. And/or threads. ;-) Glad you found it... In the past I had horrible crashes with hamlib when I first experimented with the TS-870 code. (I'm running Fedora 8 - Linux 2.6.23.1-49.fc8 #1 SMP i686 athlon i386; 1 GB RAM; Athlon XP 2000+.) Here are some other comments, besides the start-up issue: 1. Clicking Mode button produces mode setting correctly equal to Orion's state for USB, CW (if Orion LCW or UCW), and FM. However, Orion's LSB - xlog USB; AM - (unrecognized - leaves mode unchanged); FSK - (unrecognized - leaves mode unchanged) Looks like the hamlib modes are not correct. Can you please check with rigctl? Use 'rigctl --list' to find your model number, next call rigctl with the '-m' option and hit 'm' at the Rig command: prompt for every mode. I would suggest that LSB should map to LSB at least, and recognizing AM and FSK would be good as well. What do the ADIF files want? 2. Clicking Power button gives a result between 0 and 256. Hamlib returns a floating value between 0.0 and 1.0. For a 100 watt rig like mine, that should be 0 - 100 W of course. Ideally, there would be a preference setting for max. power that would be used to scale the result. In any case, 256 can't be right for most of us! Okay, I need to check this. I have had a similar report a while back, but I can't seem to find the bug. It works okay with my kenwood rig. 3. (no great importance) The S-meter scale does not correspond too well with Hamlib's numbers. Xlog's meter seems to have a long time constant, and I haven't tried to calibrate it seriously. But -6 dB (S8) from Hamlib seems to give S9 on xlog's meter. It seems to indicate 1 S-unit high over the range I've checked. Check the calbration table for your rig. It's inside the code for your rig somewhere... Hope this helps! 73 Martin AA6E Thanks very much for the report, it is appreciated! Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] 1.6
Op zaterdag 10-11-2007 om 20:18 uur [tijdzone -0500], schreef Martin Ewing - AA6E: No joy with Fedora 7. We have gtk+ v 2.10.14 only. Apparently, Fedora 8 has it - just released this week. core 8 should have the newest GTK+. In fact, I checked at http://www.gtk.org/download/, and there is no 2.12 release as yet! Is there a special reason to rely on 2.12? Yes, I want to avoid having to spend hours of work when a new GTK+ version is released. That's why I am trying to stay compatible with the latest version. For your own sake... it is best to keep your distribution updated. Newer is almost always better ;-) I will post a workaround shortly. 73 Martin AA6E Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Xdx Operation Question
Thanks Harry, et. al., I'm a bit new to the packet cluster commands, so I'm still figuring out how to automatically connect. The apropos seems to give commands I can do once I am connected. Unchecking the sound doesn't help me with the beeps (They still occur.), and turning off the system beep affects other programs that I would like to be able to beep me. So while I learned a lot, and I have some work arounds, I'm still not there yet. 'unset beep' works okay here as a cluster command, see 'apropos beep'. Thanks again 73, Rob Joop ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Xdx Operation Question
Strange... That was my first message on this list. When I got the list distributed copy I was surprised to see whole words missing from my message. Is there any filters on Joop? Your previous message was OK here, no words missing... Thanks, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Date format error with Cabrillo import?
Its one one the problems I had my backup logs Joop the spaces between report and contest serial number managed to get taken as an additional field and the qra field was lost. Xlog doesn't really care about spaces. As long as the header is intact, any information in the designated field is swallowed... Not a problem now as I've manually edited it, now the qra locator now produces distance and bearing, really great for VHF upwards what needs to be put in the locator field to allow a null entry ? leaving that field blank produces 6 digit numbers in the Azimuth and distance fields. Sorry about this, I will have a look next week. Not a major problem just noting it, but it really is a useful feature, just entering the callsign gives me a bearing , if worked before, so I can get the dishes pointing in the right direction before qsy'ing Will send you an updated source file to test. Thanks Richard g8jvm ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Power from Orion II
On Fri, 19 Jan 2007 22:51:41 + John B. Egger [EMAIL PROTECTED] wrote: Xlog's power figures are about double those indicated by my MFJ-993B antenna tuner. Here are a few data, from 80m CW: (Orion PWR control, MFJ LCD display, Xlog Power) = (100, 122, 256), (50, 58, 128), (25, 27, 64), (10, 10, 25), (5, 6.5, 12), and (1, 4.3, 2). This is a bug in the hamlib backend. Any easy fixes? Xlog 1.4, Xandros 4, Orion II. -- --John K3GHH Registered Linux User #291592 Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] export to adi
On Tue, 9 May 2006 18:22:45 +0200 (CEST) Daniel Schlieper [EMAIL PROTECTED] wrote: Dear xlog developers, first of all, many thanks for developing xlog, my favourite logging program! I use xlog in combination with gmfsk, but also on its own (for SSB contacts). When I export the xlog file to adif, I lose the information of the frequency or band. The adi file has BAND:1? instead of BAND:22M. It is easy to repair that with emacs, but I wonder if I have a broken xlog installation or if the problem is a bug? Yup, it's a bug. I just haven't though about adding 2 meters to ADIF export. I guess your 2 meter log in xlog shows something like: 144.320 for band information? You can do 2 things: Open the 'dialogs' window (ctrl+b). On the second page uncheck the ADIF option. Hopefully, xlog will now export to FREQ instead of BAND and your problems may be gone. The second option is to change the source code. Somewhere around line 420 of src/logfile/adif.c add a line with: case 144 ... 148: return 2M; just after: case 50 ... 54: return 6M; recompile and re-install :) Best regards, Daniel, M0ERA, Oxted, Surrey Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Xlog: Make Return in dialogs invoke OK.
On Mon, 01 May 2006 12:39:45 +0200 Jon K Hellan [EMAIL PROTECTED] wrote: Hi, I got tired of hunting for the OK button with the mouse, and added code to the dialogs to make Return invoke OK. It shouldn't take so much code :-) Thanks Jon and sorry for replying so late... Other things are keeping me from working on xlog... Will add your patch to the next release. I have been using shotcut keys myself in xlog. When a dialog pops up, take a good look at the buttons. I it says Ok, with and undelined 'O', you can type alt+O. Same for other strings... Anyway, using return makes sense... 73 de LA4RT Jon Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Installing on Fedora Core 5
Op za, 04-03-2006 te 12:06 -0500, schreef PASTOR/KC1DI: I got the hamlib versions reversed gmfsk .0.6 requires 1.2.0 and Xlog 1.2.4. That seems to be the conflict. Any way will pass along the tips to my friend. I guess recompilation of at least one of the two programs is needed. You can't install both hamlib 1.2.0 and 1.2.4 at the same time... Thanks 73 Dave 73 de Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] design of the score window
Op wo, 28-12-2005 te 17:54 +0100, schreef Alexandru Csete: To begin with I think it is fine with one row. In the long run, however, I would love to have both split by mode and mixed/total, also for WAZ and WAC - I'm crazy about statistics. Maybe one could use a notebook with one page per mode and the front page showing the mixed mode. That's a good idea. I was worried about space issues in the score window, but when we use a notebook there is no problem at all! What about the number of bands, should 50 Mhz be included or even more bands? I'm no VHF man yet but think people doing regular VHF/UHF are more interested in the number of grid squares rather than the number of DXCC countries worked. On the other hand, those doing EME and satellites may be interested in the number of countries as well. Okay, maybe it's okay to include 50 MHz, but who will want to work 100 countries in 2 meters anyway... :-) It would be better to add grid square statistics per band, so we should add a list dedicated to VHF/UHF qso's. What about modes, should we add RTTY and more modes? For the upper list I would prefer to have the same list of modes as I have in the option menu for mode selection. Then there could be some standard fallback list for those who do not use the option menu for mode selection. Have to think about this. There will be a configuration dialog for the score window, so we don't really have to use the option menu strings. I guess the rows to be displayed could be made configurable (I would myself only be interested in CW contacts), do we want this? Of course :) Configurable options with clever default settings are always good but a lot of work for the author. I might want to start out with a simple score window and go from there. We can always add features with future releases. By the way, some time ago I have found a little misbehaviour in xlog. When opening many logs so that the notebook page titles do not fit in the window anymore, the window width is increased even beyond the screen limits. There is an alternative, which makes the notebook tabs scrollable that is when the titles become too wide not all notebook pages are displayed, instead two small scrolling-arrows appear in the top corner of the notebook. It's done with gtk_notebook_set_scrollable. Thanks for the hint. I will take a look at it. Looking forward to test the new statistics code. Let us know when there is something testable in CVS :) Thanks for your comments! 73 Alex OZ9AEC Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] design of the score window
Attached is a screenshot of the score window which will hopefully be added to the next release. It keeps track of worked and confirmed DXCC countries and CQ zones in the logs that are opened. I have also moved the DXCC and locator frames to this window, so we have all information in one place. Do we need just one DXCC row in the bottom-right list, or do we need things like DXCC-CW, DXCC-SSB and DXCC-mixed? What about the number of bands, should 50 Mhz be included or even more bands? What about modes, should we add RTTY and more modes? I guess the rows to be displayed could be made configurable (I would myself only be interested in CW contacts), do we want this? Thanks, Joop PG4I attachment: mockup2.jpg ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: Awards tracking? (Re: [Xlog-discussion] xlog-1.3 released
In looking through the help file, I don't see any Award managment features in Xlog - are there other Free programs that will do that type of thing? Jlog does it. It is java based, so multi-platform, but without source code. I am currently working on 1.4, which should add DXCC and WAZ awards checking. Can't really say when it's ready though... -- Peter Laws | N5UWY/9 | plaws0 gmail | Travel by Train! They that can give up essential Liberty to obtain a little temporary safety deserve neither liberty nor safety. - Ben Franklin Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
[Xlog-discussion] Re: Xlog's configure script broken?
Hi Joop, Maybe a bug here, I'm not sure. Compiling with hamlib works perfectly, which is why I missed this as all my machines have hamlib installed and WITH_HAMLIB=yes in /etc/make.conf. However, deinstalling hamlib and attempting to compile xlog gives the following error (configure reports Disabling hamlib correctly and gcc uses -DWANT_HAMLIB=0 yet it's still looking for rig.h): if cc -DPACKAGE_NAME=\xlog\ -DPACKAGE_TARNAME=\xlog\ -DPACKAGE_VERSION=\1.3\ -DPACKAGE_STRING=\xlog\ 1.3\ -DPACKAGE_BUGREPORT=\[EMAIL PROTECTED] -DPACKAGE=\xlog\ -DVERSION=\1.3\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_IPC_H=1 -DHAVE_SYS_SHM_H=1 -DHAVE_STRPTIME=1 -DHAVE_STRPTIME_DECL= -DWANT_HAMLIB=0 -I. -I. -DXTHREADS -DXUSE_MTSAFE_API -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/libart-2.0 -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/X11R6/include/gtk-2.0 -I/usr/X11R6/lib/gtk-2.0/include -I/usr/X11R6/include/pango-1.0 -I/usr/X11R6/include -I/usr/local/include/freetype2 -I/usr/X11R6/include/libgnomeprint-2.2 -I.. -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DDATADIR=\/usr/X11R6/share\ -DXLOG_LOCALEDIR=\/usr/X11R6/share/locale\ -DXLOG_DATADIR=\/usr/X11R6/share/xlog\ -O2 -pipe -march=pentium3 -Wall -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.c; then mv -f .deps/main.Tpo .deps/main.Po; else rm -f .deps/main.Tpo; exit 1; fi main.c:41:24: hamlib/rig.h: No such file or directory *** Error code 1 [...] Any ideas? Thanks Matt, Yes, it's a bug. In src/main.c, line 40, replace: #if defined(WANT_HAMLIB) with: #if WANT_HAMLIB Sorry about this. I have cc'd to the mailing list in case people bump into this. If needed I can upload a new version -- Matt Dawson. [EMAIL PROTECTED] MTD15-RIPE OpenNIC M_D9 MD51-6BONE Regards, Joop PG4I ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Problems with Mandriva 2006
Op di, 15-11-2005 te 21:02 -0900, schreef John Pfeifer: I tried installing xlog under Mandriva 2006. I downloaded xlog-1.2.2.tar.gz, uncompressed it, the ran ./configure, make make install. I'm able to launch the program just fine, and--on first glance--everything appears to be fine. However, when I run xlog, the Log Editor function doesn't work and I am unable to save new log entries. Please be more specific. What do you mean with the log editor doesn't work. Please describe how you are trying to add new log entries and save them... Any ideas? thanks, John Pfeifer - WL7M Thanks, Joop PG4I -- Linux for your hamradio desktop ___ http://www.qsl.net/pg4i/linux ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Developers: AF_INET socket patch
Op za, 01-10-2005 te 12:07 -0700, schreef Mike: Description: Clients from any OS could send their log data to xlog. This is a patch to xlog that allows socket based connections from other computers to send their log data to xlog over the local network. You would only have to run one version of xlog. This works in a similar fashion to the message queues currently in xlog. Very nice Mike, I like the idea. Caveats: It is up to Joop to decide if he wants to use this code or not in future releases of xlog. People will have to write real clients to send the data over the network. Tell me what you think. I am sure it's not perfect. But it works. I would rather not use theading at the expense of using twice the amount of memory. I think there is a nice possibility in glib which doesn't depend on threading and uses g_io_add_watch to monitor the socket. I will send a patch to the list in a while, so you can try this. 73, Mike K6EEP Thanks for your contribution, Regards, Joop PG4I -- Linux for your hamradio desktop ___ http://www.qsl.net/pg4i/linux ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
Re: [Xlog-discussion] Xlog segmentation fault when a contact is logged from gMFSK (Bug Report)
Op do, 01-09-2005 te 17:13 -0700, schreef Ben Champion: Joop, Here is my ~/.xlog/preferences.xml file: I can reproduce the bugs in the odd case that there are no logs open. You must first create a log before adding data... Did you do this? 73, Ben Joop PG4I -- Linux for your hamradio desktop ___ http://www.qsl.net/pg4i/linux ___ Xlog-discussion mailing list Xlog-discussion@nongnu.org http://lists.nongnu.org/mailman/listinfo/xlog-discussion
