Station Logbook and Station Location.

[R1BLH]

A station location can now be included in multiple station logbooks, which is inconvenient when linking the desired station locations to the log.

It would be nice if the list of possible station locations displayed in the drop-down list of those available for linking to a given station logbook would only show station locations that are not yet bound to any station logbook.

[phl0]

Which version are you using? This has been implemented with #1570 in August 2022.

[R1BLH]

Version 2.5.2 (latest dev branch).

All other locations are already linked to another station logbook.

[phl0]

Hmm. That should do. The dropdown contains only station locations which are not yet linked to the Station logbook you are editing.

[R1BLH]

Yes, these station locations (which are in the drop-down list) are not linked to the current station logbook under edit. But they are already linked to another station logbook. This is the point.

It would be good to have the possibility to show in the drop-down list only those station locations that are not linked to any station logbook.

[phl0]

But that would not allow linking a location to another logbook...

[R1BLH]

Yes.
It is strange for me to link one station location with several station logbooks.
In any case, now i have 76 station locations (thanks to eQSL,cc) and it is very difficult to find necessary station location when creating new station logbook.
So this could be an option.

[HB9HIL]

Yes. It is strange for me to link one station location with several station logbooks. In any case, now i have 76 station locations (thanks to eQSL,cc) and it is very difficult to find necessary station location when creating new station logbook. So this could be an option.

I don't really understand why so many station locations .. because of eQSL??

[HB9HIL]

I have only one Logbook and various Station Locations depending from where I'm operating.

[R1BLH]

Yes, because of eQSL. Every time I move to my contryside QTH (typically every weekend in the warm season) I have to create a new profile in eQSL because the gridsquare has changed (in this case the RDA has changed as well).
This is a really annoying situation with eQSL. :(

[R1BLH]

I made a second logbook for QSO from another area and DXCC in this case (/0 in the callsign).

[dg9vh]

Yes, because of eQSL. Every time I move to my contryside QTH (typically every weekend in the warm season) I have to create a new profile in eQSL because the gridsquare has changed (in this case the RDA has changed as well). This is a really annoying situation with eQSL. :(

Why not create just one station profile in eQSL that begins at your first QSO and lasts 20 years? You can have parallel valid QTHs in eQSL to one profile... you do not need to create one just for 10 days holiday.

[R1BLH]

This is because eQSL requires that valid date periods for each QTH of the same callsign must not overlap.
It would be nice for me have only one profile for one gridsquare (one QTH). :)

[dg9vh]

Ah, I had this different in mind but you are right. I tested it on my account... what a crap :-) Am Sa., 2. Dez. 2023 um 20:57 Uhr schrieb Michael [R1BLH] < ***@***.***>:

…

Why not create just one station profile in eQSL that begins at your first QSO and lasts 20 years? You can have parallel valid QTHs in eQSL to one profile... you do not need to create one just for 10 days holiday. This is because eQSL requires that valid date periods for each QTH of the same callsign must not overlap. — Reply to this email directly, view it on GitHub <#2762 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADKN5OV73GWGQOZYLFQQUFLYHOB35AVCNFSM6AAAAABAC3N7D2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TOMZZGYZTI> . You are receiving this because you commented.Message ID: ***@***.***>

-- Amateurfunk ist das, was uns verbindet! Bleiben wir in Kontakt! DARC e.V., Ortsverband Q03, Neunkirchen