Re: #flrig Compiling on Raspberry Pi
#flrig
Thanks Dave, ? Sent from for Windows ?
toggle quoted message
Show quoted text
From: DaveSent: 12 February 2023 16:33 To: [email protected]Subject: Re: [winfldigi] #flrig Compiling on Raspberry Pi ? Phil,
That bug has been fixed in the alpha series of commits (post 1.4.7).
static Fl_Image* msg_icon;
void set_message_icon(const char** pixmap)
{
??????? if (msg_icon && msg_icon->data() == pixmap)
??????????????? return;
??????? delete msg_icon;
??????? Fl_Widget* msg = fl_message_icon();
??????? msg->label("");
??????? msg->align(FL_ALIGN_TOP_LEFT | FL_ALIGN_INSIDE);
??????? if (msg->parent() != NULL)
??????????????? msg->color(msg->parent()->color());
??????? msg->box(FL_NO_BOX);
??????? msg->image(msg_icon = new Fl_Pixmap(pixmap));
}
Your analysis of the bug is correct.? Your membership in linuxham has been approved.
73, David, W1HKJ On 2/12/23 10:09, Philip Rose via groups.io wrote: Yes I know I should post on linuxham, but my application to join is still waiting to be approved after several days. ? I am trying to compile flrig on raspberry Pi4 using a recent snapshot of fltk 1.4. It compiles OK but I get a run error. ? It's failing in this code in graphics/icons.cxx li247+ ? void set_message_icon(const char** pixmap) {? if (msg_icon && msg_icon->data() == pixmap) ???????? return; ? delete msg_icon; ? ? Fl_Widget* msg = fl_message_icon(); ? msg->label("");? msg->align(FL_ALIGN_TOP_LEFT | FL_ALIGN_INSIDE); ? msg->color(msg->parent()->color());???? <<<<<<<<< ? msg->box(FL_NO_BOX); ? msg->image(msg_icon = new Fl_Pixmap(pixmap)); } ? As if the widget is being created without a parent. I don't know if this is a feature of FLTK 1.4 v. the version of FLTK tested with. ? Regards Phil GM3ZZA ? ? ? ? ?
?
|
Re: #flrig Compiling on Raspberry Pi
#flrig
Phil,
That bug has been fixed in the alpha series of commits (post
1.4.7).
static Fl_Image* msg_icon;
void set_message_icon(const char** pixmap)
{
??????? if (msg_icon && msg_icon->data() == pixmap)
??????????????? return;
??????? delete msg_icon;
??????? Fl_Widget* msg = fl_message_icon();
??????? msg->label("");
??????? msg->align(FL_ALIGN_TOP_LEFT | FL_ALIGN_INSIDE);
??????? if (msg->parent() != NULL)
??????????????? msg->color(msg->parent()->color());
??????? msg->box(FL_NO_BOX);
??????? msg->image(msg_icon = new Fl_Pixmap(pixmap));
}
Your analysis of the bug is correct.? Your
membership in linuxham has been approved.
73, David, W1HKJ
On 2/12/23 10:09, Philip Rose via
groups.io wrote:
toggle quoted message
Show quoted text
Yes I know I should post on linuxham, but my application to join is still waiting to be approved after several days.
I am trying to compile flrig on raspberry Pi4 using a recent snapshot of fltk 1.4. It compiles OK but I get a run error.
It's failing in this code in graphics/icons.cxx li247+
void set_message_icon(const char** pixmap)
{
if (msg_icon && msg_icon->data() == pixmap)
return;
delete msg_icon;
Fl_Widget* msg = fl_message_icon();
msg->label("");
msg->align(FL_ALIGN_TOP_LEFT | FL_ALIGN_INSIDE);
msg->color(msg->parent()->color()); <<<<<<<<<
msg->box(FL_NO_BOX);
msg->image(msg_icon = new Fl_Pixmap(pixmap));
}
As if the widget is being created without a parent. I don't know if this is a feature of FLTK 1.4 v. the version of FLTK tested with.
Regards Phil GM3ZZA
|
#flrig Compiling on Raspberry Pi
#flrig
Yes I know I should post on linuxham, but my application to join is still waiting to be approved after several days.
I am trying to compile flrig on raspberry Pi4 using a recent snapshot of fltk 1.4. It compiles OK but I get a run error.
It's failing in this code in graphics/icons.cxx li247+
void set_message_icon(const char** pixmap)
{
if (msg_icon && msg_icon->data() == pixmap)
return;
delete msg_icon;
Fl_Widget* msg = fl_message_icon();
msg->label("");
msg->align(FL_ALIGN_TOP_LEFT | FL_ALIGN_INSIDE);
msg->color(msg->parent()->color()); <<<<<<<<<
msg->box(FL_NO_BOX);
msg->image(msg_icon = new Fl_Pixmap(pixmap));
}
As if the widget is being created without a parent. I don't know if this is a feature of FLTK 1.4 v. the version of FLTK tested with.
Regards Phil GM3ZZA
|
view/download macro info from function keys
is there a way that I can access the detail of the? macros that i have assigned to my function keys
they need a bit of tidying up, and it's cumbersome to have to right click and make a note of what is assigned there
I know I have duplicates and probably need to reload the defaults (assuming I can do that) and start over, but I'd like to see what s in there, because
several of those come in handy and I want to make sure I get them back in.
A
|
Thanks for the info Ed. I
will try both Flrig and CAT control. 73's
On 2/11/2023 8:40 PM, Ed W3NR wrote:
Ed W3NR
--
73'S DE NU4N DAVE
-- 73's de NU4N
|
Thanks Ed I will try both
FLRIG and Cat control. 73's
On 2/11/2023 8:40 PM, Ed W3NR wrote:
Ed W3NR
--
73'S DE NU4N DAVE
-- 73's de NU4N
|
Re: Incrementing Serial Number
This is working:?
Message Macro: <TX> <CALL> 599? <CNTR> <CNTR> <MYCALL> <RX>
Log Macro: <LOG> <INCR>
Thanks Cliff
K5XOM
|
|
|
I am having the power out issue with FLDIGI. I have FLRIG controlling FLDIGI. Using COM3 at 115000 baud. Reads the freq just fine. But some where I don't have a PTT setting correct. Anyone using the ICOM 7300 with FLDIGI.
Would appreciate the help. Thanks in advance.
--
73'S DAVE NU4N
|
Re: Incrementing Serial Number
My macro:
<TX> 599 <CNTR> <CNTR> <RX>
next macro:
<LOG><INCR>
Rules say RST & Serial number, so why is everyone over-thinking a simple macro ?
Ed W3NR
|
Re: Incrementing Serial Number
Ken,
I guess I confused things by my email.
Quoting your previous email - below is what you are sending to the other station:
<TX> <CALL> 599? <CNTR>? <CNTR>? <INCR>? <MYCALL> <RX>
I am suggesting remove the <INCR> from your macro quoted above. The <INCR> in that position causes the serial number to increment before you log it.?
After you log then increment it after the logging macro, such as <LOG><INCR> ?No need for <RX> to start out the macro. This way the serial number will be incremented before your next contact, ASSUMING that you log each contact.
If you don't do it this way then if you use the <DECR>, as you seem to be trying now, your next contact will have the wrong serial number.?
You could also put it all in one macro if you want, however I would not do it that way because you may not want to log every one for some reason:
<TX> <CALL> 599? <CNTR>? <CNTR> ?<MYCALL> <RX> <LOG> <INCR>
On Feb 11, 2023, at 13:23, Ken Smith via < kls235@...> wrote:
[Edited Message Follows]
No, it is only <LOG> I tried this <RX><INCR><LOG> and the number doubled, Like should be 95, but doubled to 97. Next? I used <RX><DECR><LOG> and that made it come out correctly, but when I respond to another station it won't transmit. So, not good yet.
|
Re: Incrementing Serial Number
Ken,
this is what you reported as your sending macro:
This is what I have to get serial to increment each time I send report.
<TX> <CALL> 599? <CNTR>? <CNTR>? <INCR>? <MYCALL> <RX>
Take the <INCR> out of that macro and put it after the <LOG> macro.
toggle quoted message
Show quoted text
On Feb 10, 2023, at 16:08, Ken Smith via < kls235@...> wrote:
This is what I have to get serial to increment each time I send report.
<TX> <CALL> 599? <CNTR>? <CNTR>? <INCR>? <MYCALL> <RX>
|
Re: Incrementing Serial Number
Ken,
Your first example of the macro that sends the data to the OP increments the counter. Take that out and put it after <LOG> and you should be good.
toggle quoted message
Show quoted text
On Feb 11, 2023, at 13:23, Ken Smith via < kls235@...> wrote:
[Edited Message Follows]
No, it is only <LOG> I tried this <RX><INCR><LOG> and the number doubled, Like should be 95, but doubled to 97.
|
Re: Incrementing Serial Number
No, it is only <LOG>
I tried this <RX><INCR><LOG> and the number doubled, Like should be 95, but doubled to 97.
Next? I used <RX><DECR><LOG> and that made it come out correctly, but when I respond to another station it won't transmit.
So, not good yet.
|
ACLog rig keying broken as of version 4.1.20
#fldigi
Hi All,
It appears that the ability to key your rig through the ACLog API connection broke between 4.1.18 and 4.1.20.? Nothing I do in 4.1.20 or later will key up the rig, and I do not see any <RIGTX> or <RIGRX> messages in the data stream (window or log file).? It works perfectly in 4.1.18, and then upgrading to 4.1.20 - making no other changes - breaks it.
Did something change about how this needs to be setup?
73,
Matt - N3NWV
|
Re: Incrementing Serial Number
Thanks Dave. I am not a programmer, but maybe someone who is will come along and make it happen.
73, Fred
K2DFC
|
Re: Incrementing Serial Number
flrig etal is "open source and
free (not as in free beer)" software.? The source code is
available at the same place at which you downloaded the binary
executable.? You are "free" to modify, build, test and submit
any changes you make so that others may enjoy the benefits of
your work.
73, David, W1HKJ
On 2/11/23 09:59, Fred K2DFC via
groups.io wrote:
toggle quoted message
Show quoted text
Last time I did a RTTY contest like this I had nothing but problems with the serial numbers. I have avoided contests like this ever since. I would think a CONFIG feature could make this easier by advancing the serial number when a QSO is logged instead of having to make it a macro item, since so many appear to have problems. As an example, the N3FJP Nov SS contest log. The serial number starts at 001 and advances automatically after each QSO is entered (logged). The OP doesn't have to do anything but concentrate on the contest. The last time I did the WPX RTTY test I had to watch and correct the serial number being sent and set up two additional macros to do it.
Fred
K2DFC
|
Re: Incrementing Serial Number
Last time I did a RTTY contest like this I had nothing but problems with the serial numbers. I have avoided contests like this ever since. I would think a CONFIG feature could make this easier by advancing the serial number when a QSO is logged instead of having to make it a macro item, since so many appear to have problems. As an example, the N3FJP Nov SS contest log. The serial number starts at 001 and advances automatically after each QSO is entered (logged). The OP doesn't have to do anything but concentrate on the contest. The last time I did the WPX RTTY test I had to watch and correct the serial number being sent and set up two additional macros to do it.
Fred
K2DFC
|
Re: Incrementing Serial Number
> shows up in the log "Ser In" box is one number higher than what was sent.
Does your macro look like
...<RX><INCR><LOG>
or
...<RX><LOG><INCR>
That is, do you log before you increment the number, or after?? Even better, you can use the <XBEG> and <XEND> to actually save/log what you sent.? (see )
|
Re: Incrementing Serial Number
When I send a report, the serial No, that is in the? "S #" box? which is right under the Call sign,?
that number prints on the screen to the other operator.
But the number that shows up in the log "Ser In" box is one number higher than what was sent.
Then I have to go to the log and manually change the number to which was actually sent.
|
Philip Rose
Dave
David Tucker
Ken Smith