maallyn/modular-radar
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix max range, range cursor, and stc range control readouts

Browse Source
This commit is contained in:
Mark Allyn
2026-06-19 08:50:59 -07:00
parent 2f8a3706c5
commit 200778af26
9 changed files with 286 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
current_build_instructions
View File

@@ -1,4 +1,33 @@
1. build a stub for each radar that displays it's information in the left panel; then show the settngs of its controls on the status panel. In the main scope, just put the name in that panel. We do not have
any workings. This is only for testing the operation of the initialization and management.
As you know, you have enabled the controls on each radar enough to show that they are working, although
there are no uniform variables yet in the shaders.
2. Set the radar management structure to have all radars fully built and available to enable the operator to go through the radar selection and operating the controls.
This next step is to correct a mistake I made, especially with the maximum range settings for the radars
as well as the cursors.
First of all remove the control for the maximum range for the chain home radar. The only range option
for that is 200 nm. This means removing the control as well as setting the global variable for the
maximum range for chain home to 200nm. Later on when development starts with chain home, we need to
have a uniform variable for maximum range.
Here are the changes I need for the controls.
Impliment the step changes for the maximum range and indicate the maximum range in the text
status. I changed the maximum range setting to the step setting.
The control for the bearing shouid show the following:
1. Degrees from true north, going clockwise for advance or counterclockwise for keyboard for going
down. This is for chain home, ascope marine, and marine traffic control.
2. Degrees from front of boat for the police boat radar, going clockwise for advance or
counterclockwise for keyboard for going
3. Note that clockwise is the direction for bearing going positive.
4. If the operator goes beyond the meximum of 360 clockwise, we reset to 0
and if the operator goes below 0 counterclockwise, we reset to 360.
The control for the range cursor; keep normalized from 0 to 1. However, please take that
normalized value and convert to actual range using the current max range setting and display
the actual range in the text status window.