Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Re: Feedback and comments
|
I support the suggestion to incorporate 1hr time segments into the schedule for all the reasons stated so far.
toggle quoted message
Show quoted text
I had no problems using the spreadsheet to assign and change operating time slots. Locking the top row and first column of the spreadsheet would be nice, and if we want to guild the lily, we could shade or color the rows. I also appreciated the messages shared by operators during the event. The reports on band conditions and your experiences with your contacts were interesting and letting us know when you needed to change your schedule was helpful. I also appreciated the N1MM tips. I did not know one can change CW speed with pgup and pgdn commands before this event. Nor do I know much about self-spotting via telnet commands. I didn't figure it out for this year's event but will investigate it for next year. Thanks to David for doing a great job organizing the team. My participation was easy and fun because of his diligence and enthusiastic encouragement throughout the event. 73, Leon NT8B -----Original Message-----
From: [email protected] <[email protected]> On Behalf Of David Wright via groups.io Sent: Friday, July 8, 2022 13:22 To: [email protected] Subject: [K2B-13Colonies2022] Feedback and comments Thanks, I wanted to start a separate thread for any comments or suggestions. So this one is fine! Here's what 13 Colonies web site says for exchange: The exchange for this event is: CALL SIGN RS / RST / RSQ STATE / PROVINCE or COUNTRY Sometimes I asked for name; usually, people volunteered it, so I did also. I think the one-hour time slot is a fantastic idea. I was going to recommend that myself. Not because of commitment(s), but because two hours can be physically grueling. On 20 meters, with jammers, guys plopping down 1 Khz away, weak signals fading in and out, DX calling off the back of the beam. Not to mention the pile-ups. Tnxs also on the spreadsheet idea. David, K2WPM K2B Coordinator ¨C 13 Colonies -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Mike Dodd via groups.io Sent: Friday, July 8, 2022 12:45 PM To: [email protected] Subject: [K2B-13Colonies2022] Feedback and comments This was my first time participating, and I came away with a few thoughts I'd like share with the group, and especially with David. ---------- TIME SLOTS: I was frustrated by the two-hour time slots on the sign-up sheet. Several times I couldn't commit to two hours due to time constraints. One-hour slots provide more flexibility and encourage signing up. Look at it this way: Suppose I can't commit to a two-hour session from 7pm-9pm, but I can and do commit to 7-8 and start operating then. Now, at 7:50, I discover I CAN operate until 9pm, so I open the sheet to see if 8-9 is still available. It is, so I sign up and keep on operating. Easy-peasy. ---------- SUGGESTION: Modify the sign-up sheet to lock the row and column headers so they're always visible. On the current sheet, they scroll off the screen as I move around the sheet. For example, if I want to sign up for 20CW at 7-9pm, the band/mode and time headers disappear as I tab from cell-to-cell and row-to-row, so I don't know which cell to look at. Hheaders should always be visible. This is a standard operation in most spreadsheets. Here's an article: <> ---------- SUGGESTION: I think 13 Colonies should eliminate the Name from the exchange. Only a few stations ever sent their name, and I didn't even know it was part of the exchange until well into the event (OK, I didn't RTFM). I didn't hear ANY K2(x) stations sending a name. Why have it if no one sends it? Comments, anyone? -- 73, Mike N4CF Louisa County, VA USA Elecraft K4d / KPA500 / KAT500 Carolina Windom up 45' |
to navigate to use esc to dismiss