Skip to content

Dynamic Variables in "Tx Macros #6

@vargatamasop

Description

@vargatamasop

Hi Lorenzo,

Thank you so much for the detailed and positive reply! I am thrilled to hear that you understand the 11m specific issue and that the AutoSeq logic update will be a priority for version 1.2.

While thinking about this limitation regarding the 9 and 10-character non-standard formats (like my own 109HA2247 or 999ZZ9999), another idea came to my mind. It could be a very powerful, complementary feature that would help operators immediately, even before the core AutoSeq logic is fully expanded.

The Proposal: Dynamic Variables in "Tx Macros" (Free Text)

Currently, the Tx Macros list only supports static text (e.g., "TNX 73 GL"). Would it be possible to introduce standard dynamic variables into the Tx Macros feature?

For example, allowing placeholders like:

<DXCALL> (Target station's callsign)

<MYCALL> (Operator's callsign)

<SNR> (Signal report from the DX Call box)

<GRID> (Locator)

How this solves the problem: If these variables were accepted, operators with long callsigns could manually create their own "fallback" macros. I could simply add a new macro: During a pile-up, instead of typing manually, I could select this macro, and the software would dynamically generate the shortened 13-character text (e.g., 109HA1641 -14) directly into the Tx5 box.

This would give us the power to execute the workaround with a single click, completely bypassing the AutoSeq hashing limitations, using our custom templates.

Do you think implementing dynamic variables for the Tx Macros field is technically feasible in the future?

Thanks again for your amazing dedication to the software!

Best regards, Tamas / 109HA2247

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions