-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some UI and UX enhancements #211
Comments
May make sense, noted.
Yeah, it does not make much sense to have 4 defaults that are the same thing.
Recall that there may be more than one peak at a time. Which one do I choose? The first one? The last one? The one with the strongest significance? The one at the highest level? What if we have two peaks that are constantly swapping in significance?
This should be a separate feature request, and could be big. I need to specify commands to enumerate inspectors and so on.
This one may make sense and should not be difficult to implement. Thanks! |
Add a textbox into Doppler tool to put the target name. To receive this variable from the infotextbox in top right corner.
In the External tool forwarding add -tsession #1 to -tsession #4 in the 4 instances. Then baudline will use different profiles and every one can store different settings, Also the #N appears in the title then can identify every baudline when have multiple instances running.
The Peak detect show the Frequency and level at right if the icon. This frequency can be get from the infotextbox as frequency_peak? Mabue the Peak icon can be better an inverted triangle than a circle?
In the RemoteApi that be able to change the frequency and BW of the inspectors.
Hide the inspector tags in the spectrum screen. For example F6 is the ON/OFF to hide and visible.
Thanks!
The text was updated successfully, but these errors were encountered: