Closed ny4i closed 3 years ago
Valery will need the link to the this build, ask the chaps with the 7600 and 7700 to try this version and ensure DEBUG level is set to TRACE.
Afterwards, we need the trace log back for analysis.
Thanks,
Tom NY4I
Principal Solutions Architect Better Software Solutions, Inc. 727-437-2771
On Feb 23, 2021, at 1:45 PM, Howie Hoyt notifications@github.com wrote:
Merged #487 https://github.com/n4af/TR4W/pull/487 into master.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/n4af/TR4W/pull/487#event-4366821745, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6TWSUGNWY53F4M3Q5FCJ3TAPZUHANCNFSM4YCVVSWQ.
i wonder if the compile error against utils_text is caused by a bad call from the added code ? https://github.com/n4af/TR4W/commit/a90167f19e5b9c4d79ac5d88c68f176a1025fc22
That seems logical. No changes to UTILS_TEXT that I recall though. Did you pull all the code from MASTER and the PULL REQUEST to compile it versus relying what was on your system?
Pulling MASTER without the pull request and trying to compile it would be a good test.
Tom Principal Solutions Architect Better Software Solutions, Inc. 727-437-2771
On Feb 23, 2021, at 2:31 PM, Howie Hoyt notifications@github.com wrote:
i wonder if the compile error against utils_text is caused by a bad call from the added code ? a90167f https://github.com/n4af/TR4W/commit/a90167f19e5b9c4d79ac5d88c68f176a1025fc22 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/n4af/TR4W/pull/487#issuecomment-784455338, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6TWSWHLJCAEHXJKPD6UQ3TAP7BPANCNFSM4YCVVSWQ.
yeah, did the pull and verified the code. always possible something was already clobbered. I will restore back to last good compile...
On Tue, Feb 23, 2021 at 2:34 PM Tom Schaefer notifications@github.com wrote:
That seems logical. No changes to UTILS_TEXT that I recall though. Did you pull all the code from MASTER and the PULL REQUEST to compile it versus relying what was on your system?
Pulling MASTER without the pull request and trying to compile it would be a good test.
Tom Principal Solutions Architect Better Software Solutions, Inc. 727-437-2771
On Feb 23, 2021, at 2:31 PM, Howie Hoyt notifications@github.com wrote:
i wonder if the compile error against utils_text is caused by a bad call from the added code ? a90167f < https://github.com/n4af/TR4W/commit/a90167f19e5b9c4d79ac5d88c68f176a1025fc22
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/n4af/TR4W/pull/487#issuecomment-784455338>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AC6TWSWHLJCAEHXJKPD6UQ3TAP7BPANCNFSM4YCVVSWQ .
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/n4af/TR4W/pull/487#issuecomment-784457164, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVLCUEQVANXGVJ2P4YYCHTTAP7M5ANCNFSM4YCVVSWQ .
it appears something is setup wrong with my compiler. i get the same issue restoring to the last and next to last releases.
Finally located the problem as an old copy of tr4w.dpr in the wrong directory. Interesting as I tried restoring the ENTIRE source directory with same problem, so the current project pointer must be in other than the dirve I maintains source code in.
Added more BandMap debug messages as well as a trace to see the data coming back from the radio. This way when the user clicks on a spot, we can see if the radio is responding properly to the command. This will show for example, if the radio command is not implemented as is the case if an IC7600 or IC7700 does not have the Version 2 and 2.1 firmware respectively.