Same issue here this afternoon. All test apps up to 4.1.23.29 worked perfectly.

73

Dave - K1DJE


On 2/13/2023 7:37 PM, Bob AF9W wrote:

I installed 4.1.24 this morning.? 4.1.23 has been running fine. When I start 4.1.24, it starts flrig and then exits.? I found events in the Windows Application Event Log.? All of the failures are identical.? It happens every time I start the app.? I tried uninstalling and reinstalling and no change.

I installed 4.1.24 this morning.? 4.1.23 has been running fine. When I start 4.1.24, it starts flrig and then exits.? I found events in the Windows Application Event Log.? All of the failures are identical.? It happens every time I start the app.? I tried uninstalling and reinstalling and no change.

Hi Dave,

Thanks for the quick work on this!? Alpha version works fine.? I noticed two things that differ slightly from the way I read the current docs:

1.? Setting the "Mode determined by" to "Don't use" really hampers ACLog, and I can't see where it makes any difference to Fldigi.? Set to "Don't use", ACLog won't automatically track the mode when logging QSOs.? You have to set it manually, which is a giant pain.? The mode in Fldigi and the mode on the radio don't seem to be connected in any way, in either direction, regardless of what settings I use here, so I'd really rather leave it set to "Rig" in AClog.? What am I breaking by ignoring the directions to set this to "Do not use"?

2.? I have to select to use RIGTX and RIGRX to have keying work.? I see the old CWCOM... commands being sent by Fldigi if I don't select this option, but those commands do not actually key the radio.? I expected to have no keying with this option deselcted, but this is not why I expected it.? I thought that this option was the "Yes/No" you want Fldigi to use AClog for keying.? How would you configure things if you wanted ACLog polling the radio, and FLdigi connected to ACLog for logging but not able to key the radio.

Thanks again Dave.? On the whole this is all great work and I really appreciate the time you put into it.

73,
Matt

On Feb 13, 2023, at 02:13, Ken Smith via <kls235@...> wrote:

As you? know I am new to all this. Having recently participated in a contest I've learned some things.
I use <LOG><INCR>? On it's own Macro
and I don't hit it until the exchange is over and there are no questions.
Because if the other op has a question and they ask you to resend your serial number
but? you already updated it by hitting log. Now it;s a new number. Then you have to start manually typing a number back to him.
So I don't log it until it's over.
The first day was hectic with the logging.
Last day was much better.
Thank you everyone.
K5XOM

On Feb 12, 2023, at 09:23, Anne KC9YL <KC9YL.anne@...> wrote:

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

[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.

?

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

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

?

?

?

?

?

?

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