Dan, yes, I can see the logic there. Although, I guess if I was going to manually forward a message to W0RMT, as an example, and type/select his address in the Station box, then it would be nice if the program automatically put the port that W0RMT was last heard on, rather than populate the port window with a port where W0RMT has never been heard. That would be helpful in situations where one's attention is being split among many people/things (e.g. an ARES/RACES event and you're sitting in a busy command post.) <br>
<br>I use W0RMT as an example because we are both local to one another and playing with D-RATS, so I hope Bud doesn't mind. We are both amazed at what you have accomplished with D-RATS, so thank you for all the hard work!<br>
<br>Gary<br>WB5PJB<br><br><br><div class="gmail_quote">On Sun, Nov 1, 2009 at 3:26 PM, Dan Smith <span dir="ltr"><<a href="mailto:dsmith@danplanet.com">dsmith@danplanet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">> I have also noticed that when I go to forward a message, because now<br>
> I have to manually forward a new message in the Outbox, the port that<br>
> automatically gets popped into the forwarding window is the ID-1,<br>
> which doesn't match the port I have set on the Chat tab at the time,<br>
> which is the IC-2820. I guess if you have just one port setup, then<br>
> it isn't an issue, but when I have two radios setup and have a radio<br>
> assigned in the Chat tab, then my own way of thinking is that the<br>
> radio assigned in the Chat tab is my current active radio for all<br>
> transmissions, so it can be a gotcha if the forwarding window throws<br>
> in a different radio as the port to use. Or, another way to look at<br>
> it might be for the program to keep track of which port it last heard<br>
> the station on to whom you are forwarding the message and pick that<br>
> port as the default. Not a big deal, but you have to be observant to<br>
> keep from forwarding an email to the wrong radio port.<br>
<br>
</div>The port selected on the chat tab does not impact anything other than<br>
chat-related activites (and QSTs). An outgoing message that is being<br>
routed automatically will use the port that the destination station was<br>
last heard on. If you're manually forwarding the message then the port<br>
and station you're choosing have nothing to do with where the message is<br>
addressed to, so choosing a port for you wouldn't make much sense.<br>
<br>
It sounds like if the send/receive was behaving properly it would be<br>
doing what you expect/want. If I can get some debug logs on that, I'll<br>
try to figure out what's going on.<br>
<div class="im"><br>
--<br>
Dan Smith<br>
dsmith#<a href="http://danplanet.com" target="_blank">danplanet.com</a>, s/#/@/<br>
<a href="http://www.danplanet.com" target="_blank">www.danplanet.com</a><br>
KK7DS<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">drats_users mailing list<br>
<a href="mailto:drats_users@lists.danplanet.com">drats_users@lists.danplanet.com</a><br>
<a href="http://lists.danplanet.com/mailman/listinfo/drats_users" target="_blank">http://lists.danplanet.com/mailman/listinfo/drats_users</a><br>
</div></div></blockquote></div><br>