Propagation from View menu

[KD0ZV]

My propagation works when using the tab with F9 but if I select it from the view menu it does not work. I have tried it using Main for a source and also Winkeyer after entering a call.

Just says no Data Available.

2020-01-17_12-13-06.jpg (122.62 KiB) Viewed 4719 times

[KI5IO]

Rich,

Do not have any callsign in the UI field.

First open Propagation Window: View/Propagation
2nd Enter in a call sign in UI.

Page 51 of Users Guide.

[KD0ZV]

Yes, that works but is kinda messed up. I already had a callsign entered.

Least it works

[KI5IO]

Rich,

The same Propagation view is noted on the Main UI at the F9 Tab.

The detachable window works quite well when an OM has a huge monitor or even two or three monitors and can spread multiple windows all over the place.

I'm limited, at my station, to one monitor so have to crowd the various windows in when testing.

When the Propagation Window is placed elsewhere outside of the Main UI then entering the callsign later works well.

[KD0ZV]

It will work just fine

I just did not realize it would not read the callsign it it was entered before you opened the detached version.

I have two 27" monitors and a 49" so not short on digital real estate.

[KD0ZV]

One of the reasons I was extra confused was this.

I entered a call and checked the F9 propagation and then decided to use the window version. So I opened the Propagation window and entered the call of interest again. It did not work. You have to enter another call sign and then go back to the call-sign of interest.

[IW3HMH]

One of the reasons I was extra confused was this.

I entered a call and checked the F9 propagation and then decided to use the window version. So I opened the Propagation window and entered the call of interest again. It did not work. You have to enter another call sign and then go back to the call-sign of interest.

This is to avoid making complex calculations on data you already have loaded. Opening a new screen will read new "events" from the main UI, it's not collecting actual UI data because the callsign could be sent to calculation engine from main user interface, winkeyer or contest screen and the form doesn't know what is the one of interest, if more than one is open