At your convenience Phil.?
Happy Birthday to your grandaughter and Happy Easter to you and
your family.
Dave
On 3/30/24 17:43, Philip Rose, GM3ZZA
via groups.io wrote:
toggle quoted message
Show quoted text
Dave,
They were run-time warnings. I'll not be able to do it tomorrow,
as it's my granddaughter's 5th?birthday as well as
being Easter Sunday,?
Phil.
Phil,
Try substituting the attached for the original files.? Let
me know if there are still compile warnings.
Dave
On 3/30/24 14:36, Philip Rose,
GM3ZZA via groups.io wrote:
Hi Dave,
It's an old Dell Intel laptop repurposed with
Debian bookworm. I use the default window manager. I built
the latest FLTK git using default configuration so Wayland
and pango are enabled.
From what I understand from the FLTK forum
having had similar problems in my app, pango expects UTF8
characters. It's what draws characters on screen which are
not specified in the supplied font.
I will understand if you don't want to support
this yet.
73 Phil GM3ZZA
On 30 March 2024, at 17:28, "Dave, W1HKJ"
<w1hkj@...> wrote:
Phil,
I have a brand new Pi5 running PiOS Bookworm with one of
several desktop managers (preference is Mate Desktop).? I
am not seeing the errors you report.? What processor for
the target build.? Is the OS install a base Debian or a
derivative?
David
On 3/30/24 11:31, Philip Rose,
GM3ZZA via wrote:
I had a quick look. There are quite a lot of degree signs
coded in string literals and these will be the extended
ASCII 0xB0 rather than the UTF-8 U+00B0 ("\302\260"). One
of the files was "coordinates.cxx" (IIRC) in the <<
operator. The others were large menu_items as part of a
special character list.
Phil.
I compiled fldigi from
4.2.04.05 using the then latest fltk 1.4 on debian
bookworm and I keep getting the following warning:
(process:21094): Pango-WARNING **: 22:50:00.323:
Invalid UTF-8 string passed to
pango_layout_set_text()
>From my own experience this is when an extended
ASCII character is used rather than its UTF-8
equivalent. I noticed today as I hovered over a
callsign the tooltip window came up and displayed
latitude and longitude with the degree symbol
replaced by the black diamond used for an
unprintable character. At the same time the pango
warning came up.
If you want I can look at the fldigi code tomorrow.
73 Phil.
|
I do a git pull on fltk 1.4 every now and then. I got the latest tonight as there was a bug fix I needed to test. Printing QSL labels had gone wrong since I moved to Linux!
Phil.
toggle quoted message
Show quoted text
Are you building against fltk 1.3.9 or the 1.4 weekly snapshot (git repro clone) ?
Dave
On 3/30/24 15:32, Dave, W1HKJ wrote:
Phil,
Try substituting the attached for the original files.? Let me know if there are still compile warnings.
Dave
On 3/30/24 14:36, Philip Rose, GM3ZZA via groups.io wrote:
Hi Dave,
It's an old Dell Intel laptop repurposed with Debian bookworm. I use the default window manager. I built the latest FLTK git using default configuration so Wayland and pango are enabled.
From what I understand from the FLTK forum having had similar problems in my app, pango expects UTF8 characters. It's what draws characters on screen which are not specified in the supplied font.
I will understand if you don't want to support this yet.
73 Phil GM3ZZA
On 30 March 2024, at 17:28, "Dave, W1HKJ"
<w1hkj@...> wrote:
Phil,
I have a brand new Pi5 running PiOS Bookworm with one of several desktop managers (preference is Mate Desktop).? I am not seeing the errors you report.? What processor for the target build.? Is the OS install a base Debian or a derivative?
David
On 3/30/24 11:31, Philip Rose, GM3ZZA via wrote:
I had a quick look. There are quite a lot of degree signs coded in string literals and these will be the extended ASCII 0xB0 rather than the UTF-8 U+00B0 ("\302\260"). One of the files was "coordinates.cxx" (IIRC) in the << operator. The others were large menu_items
as part of a special character list.
Phil.
I compiled fldigi from 4.2.04.05 using the then latest fltk 1.4 on debian bookworm and I keep getting the following warning:
(process:21094): Pango-WARNING **: 22:50:00.323: Invalid UTF-8 string passed to pango_layout_set_text()
>From my own experience this is when an extended ASCII character is used rather than its UTF-8 equivalent. I noticed today as I hovered over a callsign the tooltip window came up and displayed latitude and longitude with the degree symbol replaced by the black
diamond used for an unprintable character. At the same time the pango warning came up.
If you want I can look at the fldigi code tomorrow.
73 Phil.
|
Dave,
They were run-time warnings. I'll not be able to do it tomorrow, as it's my granddaughter's 5th?birthday as well as being Easter Sunday,?
Phil.
toggle quoted message
Show quoted text
Phil,
Try substituting the attached for the original files.? Let me know if there are still compile warnings.
Dave
On 3/30/24 14:36, Philip Rose, GM3ZZA via groups.io wrote:
Hi Dave,
It's an old Dell Intel laptop repurposed with Debian bookworm. I use the default window manager. I built the latest FLTK git using default configuration so Wayland and pango are enabled.
From what I understand from the FLTK forum having had similar problems in my app, pango expects UTF8 characters. It's what draws characters on screen which are not specified in the supplied font.
I will understand if you don't want to support this yet.
73 Phil GM3ZZA
On 30 March 2024, at 17:28, "Dave, W1HKJ"
<w1hkj@...> wrote:
Phil,
I have a brand new Pi5 running PiOS Bookworm with one of several desktop managers (preference is Mate Desktop).? I am not seeing the errors you report.? What processor for the target build.? Is the OS install a base Debian or a derivative?
David
On 3/30/24 11:31, Philip Rose, GM3ZZA via wrote:
I had a quick look. There are quite a lot of degree signs coded in string literals and these will be the extended ASCII 0xB0 rather than the UTF-8 U+00B0 ("\302\260"). One of the files was "coordinates.cxx" (IIRC) in the << operator. The others were large menu_items
as part of a special character list.
Phil.
I compiled fldigi from 4.2.04.05 using the then latest fltk 1.4 on debian bookworm and I keep getting the following warning:
(process:21094): Pango-WARNING **: 22:50:00.323: Invalid UTF-8 string passed to pango_layout_set_text()
>From my own experience this is when an extended ASCII character is used rather than its UTF-8 equivalent. I noticed today as I hovered over a callsign the tooltip window came up and displayed latitude and longitude with the degree symbol replaced by the black
diamond used for an unprintable character. At the same time the pango warning came up.
If you want I can look at the fldigi code tomorrow.
73 Phil.
|
Keeping Raspberry Pi 5 cool on large compiles
I found a page that describes how to continually run the fan in the Raspberry Pi 5.? I made these changes and the Pi 5 never got above 72C while building fldigi with "make -j4".? Max temp for the Pi 5 is 80C-85C.
To summarize, place the following lines into /boot/firmware/config.txt and reboot.
dtparam=fan_temp0=40000
dtparam=fan_temp0_hyst=10000
dtparam=fan_temp0_speed=125
One of my Raspberry Pi 5's has been modified and is sitting right in front of me. I cannot hear any noise from the fan. So, I see no downside to this.
73,
Harry Bloomberg W3YJ
|
Are you building against fltk
1.3.9 or the 1.4 weekly snapshot (git repro clone) ?
Dave
On 3/30/24 15:32, Dave, W1HKJ wrote:
toggle quoted message
Show quoted text
Phil,
Try substituting the attached for the original files.? Let me
know if there are still compile warnings.
Dave
On 3/30/24 14:36, Philip Rose, GM3ZZA
via groups.io wrote:
Hi Dave,
It's an old Dell Intel laptop repurposed with
Debian bookworm. I use the default window manager. I built
the latest FLTK git using default configuration so Wayland
and pango are enabled.
From what I understand from the FLTK forum having
had similar problems in my app, pango expects UTF8
characters. It's what draws characters on screen which are
not specified in the supplied font.
I will understand if you don't want to support
this yet.
73 Phil GM3ZZA
On 30 March 2024, at 17:28, "Dave, W1HKJ" <w1hkj@...>
wrote:
Phil,
I have a brand new Pi5 running PiOS Bookworm with one of
several desktop managers (preference is Mate Desktop).? I am
not seeing the errors you report.? What processor for the
target build.? Is the OS install a base Debian or a
derivative?
David
On 3/30/24 11:31, Philip Rose,
GM3ZZA via
wrote:
I had a
quick look. There are quite a lot of degree signs coded in
string literals and these will be the extended ASCII 0xB0
rather than the UTF-8 U+00B0 ("\302\260"). One of the files
was "coordinates.cxx" (IIRC) in the << operator. The
others were large menu_items as part of a special character
list.
Phil.
I compiled fldigi from 4.2.04.05
using the then latest fltk 1.4 on debian bookworm and
I keep getting the following warning:
(process:21094): Pango-WARNING **: 22:50:00.323:
Invalid UTF-8 string passed to pango_layout_set_text()
>From my own experience this is when an extended
ASCII character is used rather than its UTF-8
equivalent. I noticed today as I hovered over a
callsign the tooltip window came up and displayed
latitude and longitude with the degree symbol replaced
by the black diamond used for an unprintable
character. At the same time the pango warning came up.
If you want I can look at the fldigi code tomorrow.
73 Phil.
|
Phil,
Try substituting the attached for the original files.? Let me
know if there are still compile warnings.
Dave
On 3/30/24 14:36, Philip Rose, GM3ZZA
via groups.io wrote:
toggle quoted message
Show quoted text
Hi Dave,
It's an old Dell Intel laptop repurposed with
Debian bookworm. I use the default window manager. I built the
latest FLTK git using default configuration so Wayland and
pango are enabled.
From what I understand from the FLTK forum having
had similar problems in my app, pango expects UTF8 characters.
It's what draws characters on screen which are not specified
in the supplied font.
I will understand if you don't want to support this
yet.
73 Phil GM3ZZA
On 30 March 2024, at 17:28, "Dave, W1HKJ"
<w1hkj@...> wrote:
Phil,
I have a brand new Pi5 running PiOS Bookworm with one of
several desktop managers (preference is Mate Desktop).? I am
not seeing the errors you report.? What processor for the
target build.? Is the OS install a base Debian or a
derivative?
David
On 3/30/24 11:31, Philip Rose, GM3ZZA
via
wrote:
I had a
quick look. There are quite a lot of degree signs coded in
string literals and these will be the extended ASCII 0xB0
rather than the UTF-8 U+00B0 ("\302\260"). One of the files
was "coordinates.cxx" (IIRC) in the << operator. The
others were large menu_items as part of a special character
list.
Phil.
I compiled fldigi from 4.2.04.05
using the then latest fltk 1.4 on debian bookworm and I
keep getting the following warning:
(process:21094): Pango-WARNING **: 22:50:00.323: Invalid
UTF-8 string passed to pango_layout_set_text()
>From my own experience this is when an extended
ASCII character is used rather than its UTF-8
equivalent. I noticed today as I hovered over a callsign
the tooltip window came up and displayed latitude and
longitude with the degree symbol replaced by the black
diamond used for an unprintable character. At the same
time the pango warning came up.
If you want I can look at the fldigi code tomorrow.
73 Phil.
|
Hi Dave,
It's an old Dell Intel laptop repurposed with Debian bookworm. I use the default window manager. I built the latest FLTK git using default configuration so Wayland and pango are enabled.
From what I understand from the FLTK forum having had similar problems in my app, pango expects UTF8 characters. It's what draws characters on screen which are not specified in the supplied font.
I will understand if you don't want to support this yet.
73 Phil GM3ZZA
On 30 March 2024, at 17:28, "Dave, W1HKJ" <w1hkj@...> wrote:
Phil,
I have a brand new Pi5 running PiOS Bookworm with one of several
desktop managers (preference is Mate Desktop).? I am not seeing
the errors you report.? What processor for the target build.? Is
the OS install a base Debian or a derivative?
David
On 3/30/24 11:31, Philip Rose, GM3ZZA
via wrote:
I had a quick look. There are quite a lot of degree signs coded
in string literals and these will be the extended ASCII 0xB0
rather than the UTF-8 U+00B0 ("\302\260"). One of the files was
"coordinates.cxx" (IIRC) in the << operator. The others
were large menu_items as part of a special character list.
Phil.
I compiled fldigi from 4.2.04.05
using the then latest fltk 1.4 on debian bookworm and I
keep getting the following warning:
(process:21094): Pango-WARNING **: 22:50:00.323: Invalid
UTF-8 string passed to pango_layout_set_text()
>From my own experience this is when an extended ASCII
character is used rather than its UTF-8 equivalent. I
noticed today as I hovered over a callsign the tooltip
window came up and displayed latitude and longitude with
the degree symbol replaced by the black diamond used for
an unprintable character. At the same time the pango
warning came up.
If you want I can look at the fldigi code tomorrow.
73 Phil.
|
flrig 2.0.05.31 development release
posted at
More work on the 7300 FM filter controls.
73, David, W1HKJ
|
Phil,
I have a brand new Pi5 running PiOS Bookworm with one of several
desktop managers (preference is Mate Desktop).? I am not seeing
the errors you report.? What processor for the target build.? Is
the OS install a base Debian or a derivative?
David
On 3/30/24 11:31, Philip Rose, GM3ZZA
via groups.io wrote:
toggle quoted message
Show quoted text
I had a quick look. There are quite a lot of degree signs coded
in string literals and these will be the extended ASCII 0xB0
rather than the UTF-8 U+00B0 ("\302\260"). One of the files was
"coordinates.cxx" (IIRC) in the << operator. The others
were large menu_items as part of a special character list.
Phil.
I compiled fldigi from 4.2.04.05
using the then latest fltk 1.4 on debian bookworm and I
keep getting the following warning:
(process:21094): Pango-WARNING **: 22:50:00.323: Invalid
UTF-8 string passed to pango_layout_set_text()
>From my own experience this is when an extended ASCII
character is used rather than its UTF-8 equivalent. I
noticed today as I hovered over a callsign the tooltip
window came up and displayed latitude and longitude with
the degree symbol replaced by the black diamond used for
an unprintable character. At the same time the pango
warning came up.
If you want I can look at the fldigi code tomorrow.
73 Phil.
|
I had a quick look. There are quite a lot of degree signs coded in string literals and these will be the extended ASCII 0xB0 rather than the UTF-8 U+00B0 ("\302\260"). One of the files was "coordinates.cxx" (IIRC) in the << operator. The others were large menu_items
as part of a special character list.
Phil.
toggle quoted message
Show quoted text
I compiled fldigi from 4.2.04.05 using the then latest fltk 1.4 on debian bookworm and I keep getting the following warning:
(process:21094): Pango-WARNING **: 22:50:00.323: Invalid UTF-8 string passed to pango_layout_set_text()
From my own experience this is when an extended ASCII character is used rather than its UTF-8 equivalent. I noticed today as I hovered over a callsign the tooltip window came up and displayed latitude and longitude with the degree symbol replaced by the black
diamond used for an unprintable character. At the same time the pango warning came up.
If you want I can look at the fldigi code tomorrow.
73 Phil.
|
flrig 2.0.05.30 development release
posted at
Author: Black Michael <mdblack98@...>
??? Win32 com port search
????? * improved search for active serial ports.
??? Win32 zusec overflow
????? * 32-bit Windows version is overflowing zusec()
??????? Causing timeouts when timeout is set to 50ms.
Author: dave-w1hkj <w1hkj@...>
??? FT991A
????? * test for valid return strings to queries
??? QMX
????? * add set time
??? Icom transceivers mode change
????? * change to FM bandwidth decode
????? * change to mode/bandwidth/freq display sequence
????? * use set_FILT when selecting FM/FM-D bandwidths
????? * change xmlrpc command rig.set_bandwidth to select
??????? the nearest available bandwidth.? previously selected
??????? the next largest bandwidth
????? * changes effect:
??????? . 7300
Full list of changes in the readme.txt file.
73, David, W1HKJ
|
I compiled fldigi from 4.2.04.05 using the then latest fltk 1.4 on debian bookworm and I keep getting the following warning:
(process:21094): Pango-WARNING **: 22:50:00.323: Invalid UTF-8 string passed to pango_layout_set_text()
From my own experience this is when an extended ASCII character is used rather than its UTF-8 equivalent. I noticed today as I hovered over a callsign the tooltip window came up and displayed latitude and longitude with the degree symbol replaced by the black diamond used for an unprintable character. At the same time the pango warning came up.
If you want I can look at the fldigi code tomorrow.
73 Phil.
|
IC756 (non pro) with fldigi 4.2.0.3
I am using fldigi with IC-756 (non pro) for receiving wefaxes. Currently I am modifying manually the frequency in fldigi (in order to get the .jpg file with wefax with a file name with the frequency value).
I have been trying to connect both via CAT so as to avoiding the entrance manually of frequency but I have not been success
I am using .XML for ic756 (from repository) and tested all the possible configurations with RigCAT. With hamlib the application get frozen, any advice on this issue? Thanks
73s Juan EA5XQ
|
CTY-3412 Country Files - 29 March 2024
The Country (CTY) Files were updated on 29 March 2024:
For installation instructions, start at:
Hover your mouse over the word Contest in the menu, then select the
software you are using.
To install the file, follow the link to your software at the top of the page.
If you are interested in a bigger CTY.DAT for everyday logging, you can get
it here:
Note that the release notes (and Version Entity) for this larger file are
different than what is shown below. There is a separate link to them.
As a reminder, there is an RSS feed of the latest country file announcements:
Here are the release notes:
29 March 2024 (CTY-3412)
VER20240329, Version entity is Kyrgyzstan, EX
Added/changed Entities/Prefixes/Callsigns:
* IT9ACJ/I/BO is Sicily, *IT9
* TO8AN is St. Martin, FS
* GB5ALV is Northern Ireland, GI
* GB2WSS is Scotland, GM
* KE0DXZ is Hawaii, KH6
* KB7YEJ and KJ7UFK are both Alaska, KL
* LU1DXC/L, LU7DZV/D, LW3EMP/L and LW6DLS/L are all Argentina, LU
* R165ASP, R165IP, R165NN, R8FF/1 and UE79SZ are all European Russia, UA
* R165RP and R95FSI are both Asiatic Russia, UA9
* R0FBA/9 is Asiatic Russia, UA9 in CQ zone 18, ITU zone 31
* RW6MD/0 is Asiatic Russia, UA9 in CQ zone 19, ITU zone 25
Removed Entities/Prefixes/Callsigns:
* 7O2WX in Yemen, 7O
* IT9AAK/7 in Italy, I
* AA3CM and KG7ART in Hawaii, KH6
* KD7RF and KD7UZB in Alaska, KL
* LU2CRV/D, LU2DT/D and LU4VS/V in Argentina, LU
* R101AE, R101ME, R137YWI, R81AWD, R9HAF/3, R9KC/6, RA0BM/6 and RA3X/1
in European Russia, UA
Though I am subscribed to this reflector so that I can make these
announcements, I do not see most messages posted to it. If you have
any comments or corrections to the country file, please contact me
directly.
73 - Jim AD1C
--
Jim Reisert AD1C, <jjreisert at alum.mit.edu>,
|
Hi Dave,
My evenings are pretty erratic, so can't commit to a time. I've my local club net at 19:30Z for maybe an hour. After that it depends on stuff I might have to do.
Phil GM3ZZA
On 27 March 2024, at 22:00, "Dave, W1HKJ" <w1hkj@...> wrote:
I will be on 30 M again
tomorrow Phil.? Let me know a good GMT for you.
Dave
On 3/27/24 16:16, Philip Rose, GM3ZZA
via wrote:
Just saw this and thought I was in the 30 minute window. Can't
count ?. Put out a few CQ's but nothing heard this side of teh
pond.
Phil GM3ZZA
I am QRV on 10130.0 +
1500 on waterfall, Thor-11, for the next 30 minutes.
73, David, W1HKJ
|
I will be on 30 M again
tomorrow Phil.? Let me know a good GMT for you.
Dave
On 3/27/24 16:16, Philip Rose, GM3ZZA
via groups.io wrote:
toggle quoted message
Show quoted text
Just saw this and thought I was in the 30 minute window. Can't
count ?. Put out a few CQ's but nothing heard this side of teh
pond.
Phil GM3ZZA
I am QRV on 10130.0 +
1500 on waterfall, Thor-11, for the next 30 minutes.
73, David, W1HKJ
|
Re: [winfldigi] 30 meters
I can just see a carrier at 10.128 + 1.5, but no modulation.
Phil GM3ZZA
toggle quoted message
Show quoted text
Now on 10128.0 + 1500.
On 3/27/24 15:29, Dave wrote:
I am QRV on 10130.0 + 1500 on waterfall, Thor-11, for the next 30 minutes.
73, David, W1HKJ
|
Just saw this and thought I was in the 30 minute window. Can't count ?. Put out a few CQ's but nothing heard this side of teh pond.
Phil GM3ZZA
toggle quoted message
Show quoted text
I am QRV on 10130.0 + 1500 on waterfall, Thor-11, for the next 30 minutes.
73, David, W1HKJ
|
Re: [winfldigi] 30 meters
Now on 10128.0 + 1500.
On 3/27/24 15:29, Dave wrote:
toggle quoted message
Show quoted text
I am QRV on 10130.0 + 1500
on waterfall, Thor-11, for the next 30 minutes.
73, David, W1HKJ
|
I am QRV on 10130.0 + 1500 on
waterfall, Thor-11, for the next 30 minutes.
73, David, W1HKJ
|
Dave, W1HKJ
Philip Rose, GM3ZZA