Date   

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


Re: Windoze position won't save.

Glenn O'Connor
 

C:\APRSIS32 isn't a protected directory, is it Lynn?

Glenn-KF0ED


Re: Windoze position won't save.

Lynn Deffenbaugh
 

One of 2 things.  Either you've got the APRSIS32 executable in a windows-protected directory.  Or you've got APRSIS32 maximized when you close it.  Maximized windows do not save their position.

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

On 10/22/2020 7:01 AM, Glenn O'Connor wrote:
Another I D 10 T question here.

What am I doing incorrectly to not be able to save a resized window position?
If I remember correctly, merely drag the pane to the desired position and upon restart, it
goes to the new default location.

Glenn-KF0ED


Windoze position won't save.

Glenn O'Connor
 

Another I D 10 T question here.

What am I doing incorrectly to not be able to save a resized window position?
If I remember correctly, merely drag the pane to the desired position and upon restart, it
goes to the new default location.

Glenn-KF0ED


Re: Status CONNECT

Rob Giuliano
 

Got it, but once I did the print screen, it seemed to connect.
Inline image
Now the timer is working
Inline image


I disabled the logging though, so no logs.  I may re-enable them and keep trying.

Robert Giuliano
KB8RCO



On Wednesday, October 21, 2020, 1:59:58 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


I'll try and enable logging across restart.  As is typical, it stops doing it when I try to duplicate.

Corollary to https://en.wikipedia.org/wiki/Murphy%27s_law

When you want something to go wrong, it won't.

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

On 10/21/2020 1:47 PM, Rob Giuliano via groups.io wrote:
Reply in BLUE

Robert Giuliano
KB8RCO



On Wednesday, October 21, 2020, 1:25:29 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Does the top line rotate through all of your various ports statuses?
Yes, rotates through all the connections and all 3 say OK.
It sounds like you may have Configure / Beacon / After Transmit checked.
Nope, Just double checked and that is not set.

This feature is there to allow a mobile station without a GPS to pan and zoom to a new location before any posits are sent.  If your station is fixed, you probably don't want this option checked.

That may not be the situation because I just tested my two instances that use this feature and the second line says "Suspended" as I thought it should.

Can you get a screen shot of the "CONNECT"?  It's not likely, but maybe it will reveal something different to me.
I'll try and enable logging across restart.  As is typical, it stops doing it when I try to duplicate.

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

On 10/21/2020 12:56 PM, Rob Giuliano via groups.io wrote:
I am running APRSIS32 under WINE 5.0 in Kubuntu 20.04.
I connect to RF ports either through USB COMM port, AGW, or KISS over IP.

Not always, but often on first start (after reboot), the connections all say OK, but the beacon timer underneath does not start counting down.  It says "CONNECT" until I manually hit Transmit.  I have waited longer than the timer to see if it just a timing issue, but requires a manual TX to start the beaconing.
  The RF port tomeout is Zero (not much RF received the way this is setup. 

I think this may be an issue where the TX request is before the port is fully open, but it seems this should correct by itself.  Maybe not because of the Timeout setting.

Anyone else experience this with Windows or Linux and Wine?

Robert Giuliano
KB8RCO


Re: Status CONNECT

Greg D
 

For what it's worth, I run APRSIS32 on a Linux system under Wine, and I have not seen this behavior.  The only "odd" thing is that the first start-up after boot creates a small Wine window off to the side, with nothing in it.  No idea what it's for, and closing it has no apparent effect.

Greg  KO6TH


Lynn Deffenbaugh wrote:

I'll try and enable logging across restart.  As is typical, it stops doing it when I try to duplicate.

Corollary to https://en.wikipedia.org/wiki/Murphy%27s_law

When you want something to go wrong, it won't.

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

On 10/21/2020 1:47 PM, Rob Giuliano via groups.io wrote:
Reply in BLUE

Robert Giuliano
KB8RCO



On Wednesday, October 21, 2020, 1:25:29 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Does the top line rotate through all of your various ports statuses?
Yes, rotates through all the connections and all 3 say OK.
It sounds like you may have Configure / Beacon / After Transmit checked.
Nope, Just double checked and that is not set.

This feature is there to allow a mobile station without a GPS to pan and zoom to a new location before any posits are sent.  If your station is fixed, you probably don't want this option checked.

That may not be the situation because I just tested my two instances that use this feature and the second line says "Suspended" as I thought it should.

Can you get a screen shot of the "CONNECT"?  It's not likely, but maybe it will reveal something different to me.
I'll try and enable logging across restart.  As is typical, it stops doing it when I try to duplicate.

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

On 10/21/2020 12:56 PM, Rob Giuliano via groups.io wrote:
I am running APRSIS32 under WINE 5.0 in Kubuntu 20.04.
I connect to RF ports either through USB COMM port, AGW, or KISS over IP.

Not always, but often on first start (after reboot), the connections all say OK, but the beacon timer underneath does not start counting down.  It says "CONNECT" until I manually hit Transmit.  I have waited longer than the timer to see if it just a timing issue, but requires a manual TX to start the beaconing.
  The RF port tomeout is Zero (not much RF received the way this is setup. 

I think this may be an issue where the TX request is before the port is fully open, but it seems this should correct by itself.  Maybe not because of the Timeout setting.

Anyone else experience this with Windows or Linux and Wine?

Robert Giuliano
KB8RCO



Re: Status CONNECT

Lynn Deffenbaugh
 

I'll try and enable logging across restart.  As is typical, it stops doing it when I try to duplicate.

Corollary to https://en.wikipedia.org/wiki/Murphy%27s_law

When you want something to go wrong, it won't.

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

On 10/21/2020 1:47 PM, Rob Giuliano via groups.io wrote:
Reply in BLUE

Robert Giuliano
KB8RCO



On Wednesday, October 21, 2020, 1:25:29 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Does the top line rotate through all of your various ports statuses?
Yes, rotates through all the connections and all 3 say OK.
It sounds like you may have Configure / Beacon / After Transmit checked.
Nope, Just double checked and that is not set.

This feature is there to allow a mobile station without a GPS to pan and zoom to a new location before any posits are sent.  If your station is fixed, you probably don't want this option checked.

That may not be the situation because I just tested my two instances that use this feature and the second line says "Suspended" as I thought it should.

Can you get a screen shot of the "CONNECT"?  It's not likely, but maybe it will reveal something different to me.
I'll try and enable logging across restart.  As is typical, it stops doing it when I try to duplicate.

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

On 10/21/2020 12:56 PM, Rob Giuliano via groups.io wrote:
I am running APRSIS32 under WINE 5.0 in Kubuntu 20.04.
I connect to RF ports either through USB COMM port, AGW, or KISS over IP.

Not always, but often on first start (after reboot), the connections all say OK, but the beacon timer underneath does not start counting down.  It says "CONNECT" until I manually hit Transmit.  I have waited longer than the timer to see if it just a timing issue, but requires a manual TX to start the beaconing.
  The RF port tomeout is Zero (not much RF received the way this is setup. 

I think this may be an issue where the TX request is before the port is fully open, but it seems this should correct by itself.  Maybe not because of the Timeout setting.

Anyone else experience this with Windows or Linux and Wine?

Robert Giuliano
KB8RCO


Re: Status CONNECT

Rob Giuliano
 

Reply in BLUE

Robert Giuliano
KB8RCO



On Wednesday, October 21, 2020, 1:25:29 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Does the top line rotate through all of your various ports statuses?
Yes, rotates through all the connections and all 3 say OK.
It sounds like you may have Configure / Beacon / After Transmit checked.
Nope, Just double checked and that is not set.

This feature is there to allow a mobile station without a GPS to pan and zoom to a new location before any posits are sent.  If your station is fixed, you probably don't want this option checked.

That may not be the situation because I just tested my two instances that use this feature and the second line says "Suspended" as I thought it should.

Can you get a screen shot of the "CONNECT"?  It's not likely, but maybe it will reveal something different to me.
I'll try and enable logging across restart.  As is typical, it stops doing it when I try to duplicate.

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

On 10/21/2020 12:56 PM, Rob Giuliano via groups.io wrote:
I am running APRSIS32 under WINE 5.0 in Kubuntu 20.04.
I connect to RF ports either through USB COMM port, AGW, or KISS over IP.

Not always, but often on first start (after reboot), the connections all say OK, but the beacon timer underneath does not start counting down.  It says "CONNECT" until I manually hit Transmit.  I have waited longer than the timer to see if it just a timing issue, but requires a manual TX to start the beaconing.
  The RF port tomeout is Zero (not much RF received the way this is setup. 

I think this may be an issue where the TX request is before the port is fully open, but it seems this should correct by itself.  Maybe not because of the Timeout setting.

Anyone else experience this with Windows or Linux and Wine?

Robert Giuliano
KB8RCO


Re: Status CONNECT

Lynn Deffenbaugh
 

Does the top line rotate through all of your various ports statuses?

It sounds like you may have Configure / Beacon / After Transmit checked.

This feature is there to allow a mobile station without a GPS to pan and zoom to a new location before any posits are sent.  If your station is fixed, you probably don't want this option checked.

That may not be the situation because I just tested my two instances that use this feature and the second line says "Suspended" as I thought it should.

Can you get a screen shot of the "CONNECT"?  It's not likely, but maybe it will reveal something different to me.

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

On 10/21/2020 12:56 PM, Rob Giuliano via groups.io wrote:
I am running APRSIS32 under WINE 5.0 in Kubuntu 20.04.
I connect to RF ports either through USB COMM port, AGW, or KISS over IP.

Not always, but often on first start (after reboot), the connections all say OK, but the beacon timer underneath does not start counting down.  It says "CONNECT" until I manually hit Transmit.  I have waited longer than the timer to see if it just a timing issue, but requires a manual TX to start the beaconing.
  The RF port tomeout is Zero (not much RF received the way this is setup. 

I think this may be an issue where the TX request is before the port is fully open, but it seems this should correct by itself.  Maybe not because of the Timeout setting.

Anyone else experience this with Windows or Linux and Wine?

Robert Giuliano
KB8RCO

1521 - 1540 of 36433