Closed demvlad closed 6 months ago
Name | Link |
---|---|
Latest commit | 0c35172e6e7e088ded32d426122cc5a0419ed2a4 |
Latest deploy log | https://app.netlify.com/sites/origin-blackbox-logviewer/deploys/663b6d766af6290008bfe61e |
Deploy Preview | https://deploy-preview-726.dev.blackbox.betaflight.com |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
maybe not be properly rebased. & Conflicting files
maybe not be properly rebased.
Maybe! I do not understand. I've made rebase and resolved all conflicts. But there were too much conflicts after pushing branch. I've resolved their in the github online interface. Maybe this version will work:) If it will not, then i will repeate rebase.
Probably need to drop only these ones:
I've tried to load this version from github and run it. This is very wunderfull:), but it seems, the program is working! Will study, how to do rebase properly...
Probably need to drop only these ones:
Yes, i am seeing these. Will try next time :) @haslinghuis @nerdCopter would you write me please, how can i do rebase properly in this case, when both branches have too much commits.
git rebase -i HEAD~153
and drop the 3 commits. Save and force push.
Waiting for @nerdCopter for any alternatives.
i like git rebase -i
(interactive) as well. replaceing pick
with drop
for the suspect commits.
when i perform that exact command, my editor shows 4 to maybe drop.
edit: but then i still get some conflicts :frowning:
maybe squashing can help. complexity has increased with 1000 commits
Thank's. Can i do rebase like: rebase -i my_min_max_branch vite_veb_branch or rebase -i vite_veb_branch my_min_max_branch
What rebase direction is better?
Something like that described here: https://git-scm.com/docs/git-rebase
looks good :rocket:
looks good 🚀
I've done rebase more accuratly. The test master merge has not any conflicts. I am going to push this version after a small bit time.
i wonder now that it is PWA, are built-in browser based menus still bugged?
i wonder now that it is PWA, are built-in browser based menus still bugged?
The olde nw.js menu? I've checked nw.js menu in simple html page by using browser, while wrote issue in NW. They had the bugs. I think, it will has the bugs in PWA too.
looks good 🚀
I've done rebase more accuratly. The test master merge has not any conflicts. I am going to push this version after a small bit time.
Yes! The all rebase for wite web have not merge conflicts.
Improvements: The menu is simple now. There are no submenues by default.
If the stanard menu is not enough for you and you want more features, then click menu item while the Shift key is pressed. And you will see the submenu with extended actions.
The Save item is removed from the menu, because it duplicated the 'Save' checkboxes in Chart setup dialog box. You need to use the 'Save' checkboxes in one case only: if you want to change default min-max values for some curves by using workspace slots or by loading next logs. If 'Save' checkbox is not checked for curve then it will use default presets min-max values by loading next logs or workspace charts preset. I do not like the 'Save' checkboxes name, because the charts configuration will save in any case when you press the Apply button at dialog box or press Shift+num key after that. I want to find other short name for these checkboxes.
Improved: the right arrow markers are showed at menu items by pressing the Shift key to show the submenu activity. The default menu:
The menu with active submenu while Shift key is presed:
I think, the "Default" tables caption in Chart setup dialog box is better then 'Save'.
The workspace save strategy is changed #689.
I think, that are all till. I invite all participants for testing.
The 'This curves' actions replaced into submenu. Finaly we have next variants menu:
Improvements: The Apply and Cancel buttons are enabled while menu is open. You can use it to close the dialog box without pressing of Back and Return menu items. The Alt (optionKey on Mac) key is used instead of Shift to use hidden submenu. The 'Full range' item of 'This curve' menu has submenu while Alt key is pressed. The 'Default' item on main menu has hidden submenu too. The menu source code structure is improved.
The issue of this version what i know, and their resolving at moment:
The 'Full range' submenu on 'This curve' menu while Alt key is pressed.
Resolved issue of Esc and Alt keys actions. I've found that in Vite Web version the Alt-key activate the browsers menu in Windows. Therefore in the Vite Web version i am using Shift-key.
@ctzsnooze Please, check this update.
I notice, that in WEB version the menu modify key is 'Shift', in no WEB - 'Alt'
This is link to current NO WEB version. https://github.com/demvlad/blackbox-log-viewer/tree/min_max_chart_settings I will continue to support this version. The all new updates in future will be on this link.
@ctzsnooze I've reverted the all autocomplete preventions commits. Please check this version.
Improvements:
@ctzsnooze , the last issues are resolved. Updated:
Resolved error of data storage by using Expo, Grid, Smooth buttons
THE MANUAL The MinMax PR can control curves scale and placement quickly and full. The current MinMax curves settings are showed at 'Configure graphs' dialog box in the "Minimum" and "Maximum" columns.
The MinMax values can be changed:
To show context menu you must do right mouse click on Minimum or Maximum values field what you want to edit. The main context menu:
The main menu include following parts:
The actions for all curves:
The single curve submenu has same actions:
The main menu has extended mode. You need press the 'Shift' key to activate it and select the submenu, what you need.
The 'Like this one' extended submenu. You can change MinMax values and select curves what you need by using the checkboxes to apply these values. Click 'SET MIN-MAX VALUES' item for apply. Click 'Back' menu item to go back to main menu. Click 'Apply change' or 'Cancel' button on the main 'Configure graphs' dialog box to close the menu and dialog box immediately
The 'Zoom in', 'Zoom out' extended submenu. You can set the zoom procent value and select curves what you need by using the checkboxes to apply zoom. Click 'ZOOM IN', 'ZOOM OUT' items for apply zoom Click 'Back' menu item to go back to main menu. Click 'Apply change' or 'Cancel' button on the main 'Configure graphs' dialog box to close the menu and dialog box immediately
The 'Default' extended submenu. You can select curves what you need by using the checkboxes to apply default values. Click 'SET CURVES TO DEFAULT' item for apply Click 'Back' menu item to go back to main menu. Click 'Apply change' or 'Cancel' button on the main 'Configure graphs' dialog box to close the menu and dialog box immediately
The 'Full range' extended submenu. You can select curves what you need by using the checkboxes to apply values. Click 'At all global log time' menu item to set MinMax values from log data during all time. Click 'At local window time' menu item to set MinMax values from current time interval at the chart window. Click 'At markere time range' menu item to set MinMax values from markered time interval what you select by using "I", "O" keys. If it is not select then will apply all log time interval. Click 'Back' menu item to go back to main menu. Click 'Apply change' or 'Cancel' button on the main 'Configure graphs' dialog box to close the menu and dialog box immediately
The 'One scale' extended submenu. You can select curves what you need by using the checkboxes to set the same scale. Click 'SET SET CURVES TO SAME SCALE' item for apply Click 'Back' menu item to go back to main menu. Click 'Apply change' or 'Cancel' button on the main 'Configure graphs' dialog box to close the menu and dialog box immediately
The 'Centered' extended submenu. You can select curves what you need by using the checkboxes to centered. Click 'SET CURVES TO ZERO OFFSET' item for apply Click 'Back' menu item to go back to main menu. Click 'Apply change' or 'Cancel' button on the main 'Configure graphs' dialog box to close the menu and dialog box immediately
The single curve submenu has one 'Full range' extended item: It is like 'Full range' extended submenu, but for one selected curve only.
If you open context menu for one curves chart, then you see the short menu:
When you store the chart configuration in the workspace, the MinMax values stored for next using too.
This is non WEB version the PR: https://github.com/betaflight/blackbox-log-viewer/pull/689
Working REALLY WELL!! Absolutely love this PR. I can now quickly and easily set up the display exactly how I need it. Particularly helpful for debugs that don't have sensible scaling info. Ready to merge? I think so. Definitely ready for review.
May require a new workspaces file. Here's my current file. workspaces-ctzsnooze.json.zip
@haslinghuis Yes, we have two big improvements at moment: the VITE WEB and my MinMax. The all are need testing. Therefore i will continue to support my non Web PR version to different some bugs, what will possible.
@ctzsnooze workspace is used by default. His workspace uses curves min-max values, what this PR can control. Other improvements:
:thinking: we should add default workspace in separate PR as there is some discussion about having multiple presets
as default.
Anything that could reduce the size of this PR :stuck_out_tongue:
See also: #726
🤔 we should add default workspace in separate PR as there is some discussion about having multiple
presets
as default.
These are a small different workspaces. This workspace PR stored any min-max values what you can set to scale and place curves at the chart. If the full web version can not save local data and need some multy-presets, probably i will prefer developers local variant :)
The small improvement: The mouse click at curves on the legend works like toggle button (make the analyser chart as visible/unvisible)
@haslinghuis @nerdCopter @SupaflyFPV This PR is ready to merge now
i feel like Default
should be first in menu -- thoughts?
i feel like
Default
should be first in menu -- thoughts?
Yes, maybe.
Updated:
Failed conditions
C Reliability Rating on New Code (required ≥ A)
See analysis details on SonarCloud
Catch issues before they fail your Quality Gate with our IDE extension SonarLint
The Sonar Cloud
shows that many switch/case just return the same thing return value;
so it seems the switch/case are not even needed. please verify or reply otherwise.
The
Sonar Cloud
shows that many switch/case just return the same thingreturn value;
so it seems the switch/case are not even needed. please verify or reply otherwise.
switch/case ??? Yes, there are in default curves and units converters code. I've used the previouse source code as the ground. There are huge switch/case code really. And this code "return the same thing return value". Ok, I will check it.
@nerdCopter The example of code: case 'FFT_TIME': switch (fieldName) { case 'debug[0]': return value; case 'debug[1]': return value; // debug 2 = not used // debug 3 = not used default: return value; } The all cases return back the same input value today. But maybe someone will edit this or similar DEBUGs next time, i do not know that.
Will need to be refactored in another PR some time.
okay, i approved. if refactoring for a future date, no problem.
Main issue with this PR is that the user's workspaces have to be rebuilt.
@ctzsnooze
It is possible to use olde workspaces in this PR.
It has default curves MinMax values as start after loading.
I've checked this on supafly.json file for example.
Although useful, this file should not have been committed: src/workspaces-ctzsnooze.json
Although useful, this file should not have been committed: src/workspaces-ctzsnooze.json
This is workspace by default, it is used in main.js. This workspace showes using of MinMax.
@demvlad huge thank you for all improvements. Very much appreciated. Would love to see the documentation included in https://github.com/betaflight/betaflight.com
PR #689 for VITE Web.