Date   

Re: AGW (logs TX) vs. KISS over IP (TX not in log)

Lynn Deffenbaugh
 

Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


AGW (logs TX) vs. KISS over IP (TX not in log)

Rob Giuliano
 

Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Fix RF/TCP message gating (Dev: 2020/10/27 14:46)

Lynn Deffenbaugh
 

I recently discovered that I missed implementing one of the rules for gating messages from the APRS-IS to RF.  http://www.aprs-is.net/IGateDetails.aspx states:

Gate message packets and associated posits to RF if all of the following are true:

  1. the receiving station has been heard within range within a predefined time period (range defined as digi hops, distance, or both).
  2. the sending station has not been heard via RF within a predefined time period (packets gated from the Internet by other stations are excluded from this test).
  3. the sending station does not have TCPXX, NOGATE, or RFONLY in the header.
  4. the receiving station has not been heard via the Internet within a predefined time period.
    A station is said to be heard via the Internet if packets from the station contain TCPIP* or TCPXX* in the header or if gated (3rd-party) packets are seen on RF gated by the station and containing TCPIP or TCPXX in the 3rd-party header (in other words, the station is seen on RF as being an IGate).
I was missing the 4th condition from that list.  This development release fixes that issue.

Also, whatever software is using ToCall of >APEG03, likely UISS or the SGATE add-on, doesn't properly ack inbound messages that use a Reply-Ack format (which APRSIS32 does).  This causes lots of retries from the SATSRV, so I have (hopefully temporarily) disabled SATSRV responses if the message comes from >APEG*.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


Re: AGW vs. KISS over IP

Rob Giuliano
 

Just to be clear,  AGW is a sound card TNC application, but includes a specific 'AX.25 style' IP protocol.
I was not using AGW computer application, but running Direwolf and using its AGW protocol between Pi (Direwolf) and PC (APRSIS32).

In direwolf_left.conf the port settings were:
#############################################################
#               VIRTUAL TNC SERVER PROPERTIES               #
#############################################################
# Dire Wolf acts as a virtual TNC and can communicate with
#   client applications by different protocols:
#       - the "AGW TCPIP Socket Interface" - default port 8000
#       - KISS protocol over TCP socket - default port 8001
#       - KISS TNC via pseudo terminal   (-p command line option)
AGWPORT 8000
KISSPORT 8001


In direwolf-right.conf the port settings were:
#############################################################
#               VIRTUAL TNC SERVER PROPERTIES               #
#############################################################
# Dire Wolf acts as a virtual TNC and can communicate with
#   client applications by different protocols:
#       - the "AGW TCPIP Socket Interface" - default port 8000
#       - KISS protocol over TCP socket - default port 8001
#       - KISS TNC via pseudo terminal   (-p command line option)
AGWPORT 8010
KISSPORT 8011


To test the AGW protocol to/from APRSIS32 and more importantly, investigate my concern about the logging,
I created 2 AGW RF port with settings of:
   Type:            AGW     This is the communication protocol between device and APRSIS32.
   IP or DNS:    pi3         hostname for my Pi3 on the local network
   Port:              8000     First port's 'Port' setting to get data from the left side audio
    or  Port:        8010     Second port's 'Port' setting to get data from the right side audio

Then disable those 2 ports and created 2 new using straight KISS over IP
   Type:            IP                          This is the communication protocol between device and APRSIS32.
   IP or DNS:    pi3         hostname for my Pi3 on the local network
   Port:              8001     First port's 'Port' setting to get data from the left side audio
    or  Port:        8011     Second port's 'Port' setting to get data from the right side audio

Most of the sound card TNC emulators offer the option of communicating with the AGW protocol. 

Robert Giuliano
KB8RCO



On Friday, October 23, 2020, 12:20:10 AM EDT, Michael Wright <mfwright@...> wrote:


I played around a little with AGW, but DireWolf works for me.

I also want to say thanks for helping all the customers with this product!

Mike K6MFW






Re: Documented Ctrl shortcuts

Glenn O'Connor
 

Thanks Robert. I did have the Dev set at 1, previously.....Duh.

Glenn-KF0ED


Re: AGW vs. KISS over IP

Michael Wright
 

I played around a little with AGW, but DireWolf works for me.

I also want to say thanks for helping all the customers with this product!

Mike K6MFW


Re: AGW vs. KISS over IP

Rob Giuliano
 

Ignore me - messed up right side AGW port.  I Had it swapped with IP.
I knew the data looked strange.

Issue is only logging. KISS IP shows received data, but no TX data when a radio is connected.

Robert Giuliano
KB8RCO



On Thursday, October 22, 2020, 11:52:33 PM EDT, Rob Giuliano via groups.io <kb8rco@...> wrote:


I have mentioned issues with log windows and KISS ports over IP.  Now I was able to try a few things with 2 active channels on 1 sound card that actually interface with APRSIS32, but as 2 ports.  I am confused as to a few things:
1.  Why AGW does not TX on the Right channel, but KISS_IP does?
2.  Logging acts different in AGW than in KISS_IP.
3.  Logging acts differently for KISS_IP if radio is connected to the sound card channel?

Lots of info, but I hope it help find reasons.

Configuration:
I purchased the FePi sound card (stereo output and stereo input board that is a "hat" for the Pi), and the Nexus DR-X (digital radio cross patch).  The Nexus provides 2 "data jacks" that are designed to have access to the left LineIn/LineOut and connect them to different radios.  The Nexus Pi Distro provides drivers and many digital mode applications - including Direwolf. 

With this setup, I run 2 separate instances of Direwolf (separate terminals and configurations).
One uses the left audio channel, the other uses the right.

Observations:
As I was experimenting with this configuration, I noticed that if I connect to them using AGW, the right side does not go into TX.  If I switch to KISS over IP, everything works properly.

I think the TX issue is something in my setup (CONFIRMED!!!)
HOWEVER, in trying to troubleshoot the issue, I setup 4 ports and enable logging on each:
1.  DW_KISS_Lt             IP  8010
2.  DW_KISS_Rt            IP  8011
3.  DW_AGW_Lt        AGW  8000
4.  DW_AGW_Rt        AGW  8001

1.  DW_KISS_Lt             IP  8001
2.  DW_KISS_Rt            IP  8011
3.  DW_AGW_Lt        AGW  8000
4.  DW_AGW_Rt        AGW  8010

If I enable only 1 and 2, clear the log window, and hit <Transmit>
   everything looks normal, both TX as expected.  Neither post anything to the log.
   If I disconnect the radio from the left - Left logs.  (Same with only Left connect to radio - Rt logs)
   If I disconnect both from the radio, Both log.
If I enable only 3 and 4, clear the log window, and hit <Transmit>
   Operates as expected.

Robert Giuliano
KB8RCO


AGW vs. KISS over IP

Rob Giuliano
 

I have mentioned issues with log windows and KISS ports over IP.  Now I was able to try a few things with 2 active channels on 1 sound card that actually interface with APRSIS32, but as 2 ports.  I am confused as to a few things:
1.  Why AGW does not TX on the Right channel, but KISS_IP does?
2.  Logging acts different in AGW than in KISS_IP.
3.  Logging acts differently for KISS_IP if radio is connected to the sound card channel?

Lots of info, but I hope it help find reasons.

Configuration:
I purchased the FePi sound card (stereo output and stereo input board that is a "hat" for the Pi), and the Nexus DR-X (digital radio cross patch).  The Nexus provides 2 "data jacks" that are designed to have access to the left LineIn/LineOut and connect them to different radios.  The Nexus Pi Distro provides drivers and many digital mode applications - including Direwolf. 

With this setup, I run 2 separate instances of Direwolf (separate terminals and configurations).
One uses the left audio channel, the other uses the right.

Observations:
As I was experimenting with this configuration, I noticed that if I connect to them using AGW, the right side does not go into TX.  If I switch to KISS over IP, everything works properly.

I think the TX issue is something in my setup.  HOWEVER, in trying to troubleshoot the issue, I setup 4 ports and enable logging on each:
1.  DW_KISS_Lt             IP  8010
2.  DW_KISS_Rt            IP  8011
3.  DW_AGW_Lt        AGW  8000
4.  DW_AGW_Rt        AGW  8001

If I enable only 1 and 2, clear the log window, and hit <Transmit>
   everything looks normal, both TX as expected.  Neither post anything to the log.
   If I disconnect the radio from the left - Left logs.  (Same with only Left connect to radio - Rt logs)
   If I disconnect both from the radio, Both log.
If I enable only 3 and 4, clear the log window, and hit <Transmit>
   Left TX, but Right No.  Both log.  Entries: L:2 R:3.
   Extra Rt entry:
      Port(DW_AGW_Rt):2020-10-23T03:00:56.711 AGW:Need 892547120 Data, Have 180 / 892547156 Bytes

Only 3:
Port(DW_AGW_Lt):2020-10-23T03:27:51.457 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@032751h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Lt):2020-10-23T03:27:53.479 AGW:AX.25-rPort[0] KB8RCO>APWW11,WIDE2-2:@032751h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!

Only 4:  No TX!!
   Log:
Port(DW_AGW_Rt):2020-10-23T03:25:08.447 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@032508h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-23T03:25:22.451 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@032522h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!

If I enable only 2 and 3, clear the log window, and hit <Transmit>
   Left TX (pause) Right TX. Both log.  Entries: L:2 R:1
If I enable only 1 and 4, clear the log window, and hit <Transmit>
   Left TX, Right No. Both log.  Entries:  L:2 R:4

Example from the AGW log (bold is start of line):
Port(DW_AGW_Rt):2020-10-23T03:13:00.457 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@031300h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-23T03:13:01.872 Read 90 bytes after 144198 msec (up from 68187) vs 0 Quiet
Port(DW_AGW_Rt):2020-10-23T03:13:01.873 AGW:Need 858797872 Data, Have 630 / 858797908 Bytes
[630]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@030703h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@030750h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@030807h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@030820h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@030927h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@031036h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@031300h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>

Robert Giuliano
KB8RCO


Re: Documented Ctrl shortcuts

Rob Giuliano
 

I believe a previous post asked (by Lynn) whether you had enabled development mode?
  I am pretty sure this function is still only available in development mode.

Close APRSIS32 (can edit with it open), open the XML and search for
   <Update.Development>1</Update.Development>
Save the xml, start APRSIS32 and check about to see if there is an update.

Robert Giuliano
KB8RCO



On Thursday, October 22, 2020, 5:28:34 PM EDT, Glenn O'Connor <ka0lnr37@...> wrote:


Another thread. Yes, I'm not adding to the previous one I started.

Usually, I can adopt/manipulate the program for a custom use case. Quite, often, without documenting what worked in my instance, I'll fumble around until something "clicks".

I reverse Igate often in our rural locale NWS objects and others of local interest.
Ctrl-G to start and then Ctrl-I to xmit local RF. As I said, I fumble around. Ctrl-I isn't responding nor is the Igate showing in the view logs menu.

What have I NOT enabled in the port(s) settings?


Documented Ctrl shortcuts

Glenn O'Connor
 

Another thread. Yes, I'm not adding to the previous one I started.

Usually, I can adopt/manipulate the program for a custom use case. Quite, often, without documenting what worked in my instance, I'll fumble around until something "clicks".

I reverse Igate often in our rural locale NWS objects and others of local interest.
Ctrl-G to start and then Ctrl-I to xmit local RF. As I said, I fumble around. Ctrl-I isn't responding nor is the Igate showing in the view logs menu.

What have I NOT enabled in the port(s) settings?


Re: Windoze position won't save.

Lynn Deffenbaugh
 

Glad it's working.  Aero was probably setting window position flags rather than setting the actual window position.  That is actually why a maximized window doesn't save and restore properly, because the size and position of the window are not actually set.  Windows just "knows" that it's maximized and uses whatever the current definition of that is.

I suspect Aero has similar "snapped" flags somewhere that it is using rather than setting the size and position.

But congratulations on finally figuring it out.  Wow.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/22/2020 4:39 PM, Glenn O'Connor wrote:
I believe I've made peace with the app. Now, maybe I've had to do this in the past, maybe not.

NOT using the Aero Snap feature, I've a manually sized and saved under Screen/Preferred/Save.
Now exiting/launching the app, the desired main window(pane) size is restored.

I think I'll keep README notes entitled I D 10 T to keep around for my "custom" setup.

Thanks Lynn for all you do for our community!!

73,
Glenn-KF0ED

P.S. Yes, on the HF modem, I was only testing. I will run a separate instance if needed.


Re: Windoze position won't save.

Lynn Deffenbaugh
 

I suspect Aero is busting you.  Try manually sizing the window(s) where you want them, but make sure Aero doesn't "help" you.  Even if you have to leave a little border around the window, do it.  I suspect that will solve your issue.

Anyone else out there using Aero?  Has anyone else had issues with windows size/position being recalled?  Is anyone else even following this thread?  ;)

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/22/2020 4:09 PM, Glenn O'Connor wrote:

Do your multi-track windows come back where they were when you closed them?  Try the following sequence:

1) Open a multitrack on some station
2) Size and/or move the window around to where you'll remember
3) Close the multi-track window
4) Re-open a multitrack on the same station.

if that works, then try putting the multitrack window where you want your main window to be and close it there.  Then re-open the multitrack and see where it goes now.


The Multi-track reverts to the main window size after reopening.

One more question.  Is the main window completely on the screen on the right side of your monitor or is it's right edge actually off the screen?

It's on the very right side of the monitor, using the Aero feature.

And (ok, two questions) are you using one of those Windows features that maximizes the vertical coverage of a the window or are you actually sizing and moving it to exactly where you want it to be?

Yes, that Aero feature does maximize the vertical position. No to sizing it "manually". BUT, I just noticed something, a new wrinkle perhaps. Upon the Aero sizing of the main window, I've been able, in the past, to move that main window around the monitor's "real estate" and maintain that aspect ratio. However, now I moved that desired window aspect even just slightly away from monitor's side, it reverts to the original, undesired windows size! Wait, what?!?!


Re: Windoze position won't save.

Glenn O'Connor
 

I believe I've made peace with the app. Now, maybe I've had to do this in the past, maybe not.

NOT using the Aero Snap feature, I've a manually sized and saved under Screen/Preferred/Save.
Now exiting/launching the app, the desired main window(pane) size is restored.

I think I'll keep README notes entitled I D 10 T to keep around for my "custom" setup.

Thanks Lynn for all you do for our community!!

73,
Glenn-KF0ED

P.S. Yes, on the HF modem, I was only testing. I will run a separate instance if needed.


Re: Windoze position won't save.

Glenn O'Connor
 

Do your multi-track windows come back where they were when you closed them?  Try the following sequence:

1) Open a multitrack on some station
2) Size and/or move the window around to where you'll remember
3) Close the multi-track window
4) Re-open a multitrack on the same station.

if that works, then try putting the multitrack window where you want your main window to be and close it there.  Then re-open the multitrack and see where it goes now.


The Multi-track reverts to the main window size after reopening.

One more question.  Is the main window completely on the screen on the right side of your monitor or is it's right edge actually off the screen?

It's on the very right side of the monitor, using the Aero feature.

And (ok, two questions) are you using one of those Windows features that maximizes the vertical coverage of a the window or are you actually sizing and moving it to exactly where you want it to be?

Yes, that Aero feature does maximize the vertical position. No to sizing it "manually". BUT, I just noticed something, a new wrinkle perhaps. Upon the Aero sizing of the main window, I've been able, in the past, to move that main window around the monitor's "real estate" and maintain that aspect ratio. However, now I moved that desired window aspect even just slightly away from monitor's side, it reverts to the original, undesired windows size! Wait, what?!?!


Re: Windoze position won't save.

Lynn Deffenbaugh
 

After the re-install, did you edit the XML to switch to the current development version?  Not that the general version is very far behind, but what does your About box say?

This one has me stumped.

Do your multi-track windows come back where they were when you closed them?  Try the following sequence:

1) Open a multitrack on some station
2) Size and/or move the window around to where you'll remember
3) Close the multi-track window
4) Re-open a multitrack on the same station.

if that works, then try putting the multitrack window where you want your main window to be and close it there.  Then re-open the multitrack and see where it goes now.

One more question.  Is the main window completely on the screen on the right side of your monitor or is it's right edge actually off the screen?

And (ok, two questions) are you using one of those Windows features that maximizes the vertical coverage of a the window or are you actually sizing and moving it to exactly where you want it to be?

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/22/2020 3:31 PM, Glenn O'Connor wrote:
On Thu, Oct 22, 2020 at 01:40 PM, Lynn Deffenbaugh wrote:

1) If you make other configuration changes and close the client, do they show up in the XML?  The easiest one of those to try is change the Configure / General / Comment, close the client, and then see if your updated text is in the XML.  This will verify that APRSIS32 is able to write to the configuration XML file.

The XML file is being written to. Verified with the above suggested move.

2) Are you SURE you have the main window restored and not maximized when you close the client.  Window positions are NOT recorded if you close a maximized main window.

I don't run the program maximized.

3) What version of windows are you running?

W8.1

4) Is it a dual (or multi) monitor system?

Single, in the beloved Aero mode occupying the right side of a 16x9 monitor.

5) What is the callsign-SSID of the instance in question?

KF0ED

6) How are you closing the client?  The Exit menu option?  The X in the upper right corner?  Double-clicking the system menu in the upper left?  Closing from the task bar?  Force closing from Task Manager?

The upper X, usually.

This is a recent issue, Lynn. I've uninstalled the program for a reason or two, to get a clean reinstall.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


Re: Windoze position won't save.

Glenn O'Connor
 

On Thu, Oct 22, 2020 at 01:40 PM, Lynn Deffenbaugh wrote:

1) If you make other configuration changes and close the client, do they show up in the XML?  The easiest one of those to try is change the Configure / General / Comment, close the client, and then see if your updated text is in the XML.  This will verify that APRSIS32 is able to write to the configuration XML file.

The XML file is being written to. Verified with the above suggested move.

2) Are you SURE you have the main window restored and not maximized when you close the client.  Window positions are NOT recorded if you close a maximized main window.

I don't run the program maximized.

3) What version of windows are you running?

W8.1

4) Is it a dual (or multi) monitor system?

Single, in the beloved Aero mode occupying the right side of a 16x9 monitor.

5) What is the callsign-SSID of the instance in question?

KF0ED

6) How are you closing the client?  The Exit menu option?  The X in the upper right corner?  Double-clicking the system menu in the upper left?  Closing from the task bar?  Force closing from Task Manager?

The upper X, usually.

This is a recent issue, Lynn. I've uninstalled the program for a reason or two, to get a clean reinstall.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32


Re: Windoze position won't save.

Lynn Deffenbaugh
 

1) If you make other configuration changes and close the client, do they show up in the XML?  The easiest one of those to try is change the Configure / General / Comment, close the client, and then see if your updated text is in the XML.  This will verify that APRSIS32 is able to write to the configuration XML file.

2) Are you SURE you have the main window restored and not maximized when you close the client.  Window positions are NOT recorded if you close a maximized main window.

3) What version of windows are you running?

4) Is it a dual (or multi) monitor system?

5) What is the callsign-SSID of the instance in question?

6) How are you closing the client?  The Exit menu option?  The X in the upper right corner?  Double-clicking the system menu in the upper left?  Closing from the task bar?  Force closing from Task Manager?

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/22/2020 2:22 PM, Glenn O'Connor wrote:
Coming back to the my issue at hand, here's a clip of the APRSIS32 XML file points to Windows position: It doesn't vary, however, I can alter it to get the desired view.

<WindowPosition>*MainWindow*:10@130,130[1440,759]All</WindowPosition>
<!--SavedPosit-->


Re: Windoze position won't save.

Glenn O'Connor
 

Coming back to the my issue at hand, here's a clip of the APRSIS32 XML file points to Windows position: It doesn't vary, however, I can alter it to get the desired view.

<WindowPosition>*MainWindow*:10@130,130[1440,759]All</WindowPosition>
<!--SavedPosit-->


Re: Windoze position won't save.

Rob Giuliano
 

Actually, depending on the default restrictions, the root can be pritected from running applications writing to it.  Making sub folders seems to be okay,  but I have heard usrrs complain about being able to create it, but then had to change secutity settings to use it.

Something to keep in mind as MS continues to become stricter on these things, and adding other protection applica0tions make it more so.


On Thu, Oct 22, 2020 at 8:10 AM, Lynn Deffenbaugh
<kj4erj@...> wrote:

No, that should be fine.  Protected directories are the "Program Files" and such.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/22/2020 7:36 AM, Glenn O'Connor wrote:
C:\APRSIS32 isn't a protected directory, is it Lynn?

Glenn-KF0ED


Re: Windoze position won't save.

Lynn Deffenbaugh
 

No, that should be fine.  Protected directories are the "Program Files" and such.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/22/2020 7:36 AM, Glenn O'Connor wrote:
C:\APRSIS32 isn't a protected directory, is it Lynn?

Glenn-KF0ED

961 - 980 of 35881