Skip to content
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

Mission Editor-extras #1332

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

AndKe
Copy link
Contributor

@AndKe AndKe commented Mar 6, 2024

Adding these buttons:

"Add Yaw for each WP":
This add (optionally, starting from with selected waypoint) a YAW command for each waypoint.
This is useful for copters flying a grid/mission with a preset heading (in order for a sensor to face it's target )

"Deleye Yaw" :
Clean up mission, removing all Yaw commands.

"Change WP Altitude":
Allows to enter a offset for all WP altitudes in mission, useful when changing the mission slightly up/down

"Change Frame":
Let the user quickly change the whole missions altitude frame - for example from REL to ABS or AGL.

@peterbarker
Copy link
Contributor

image

tridge recently added some commands to change the Frame.

We'll probably add something to change a arbitrary field somehow.

One problem with this PR as-written is that it will affect all waypoints rather than a range. At least on Linux you can select a range of rows. I think it would be a far better interface to be able to select a range and only affect those cells.

image

tridge will need to be happy with the extra screen real-estate taken up by the new buttons.

@AndKe
Copy link
Contributor Author

AndKe commented Apr 6, 2024

Yes, the "from" behavior is by design, as one often want to keep flying nose-first to the data gathering area, and then fly sideways.
You mention selection is an option in Linux, - yes, but I have no clue is that has some reason to be different in win/mac .
Of course, I could have made it "for selected waypoints"

The real-estate has been vacant for years, and it is time to use it for something useful :)

@tridge
Copy link
Contributor

tridge commented Apr 10, 2024

@AndKe if it turns out to be tricky to use selected cells then I'd be fine with it always doing all rows

@AndKe
Copy link
Contributor Author

AndKe commented Apr 10, 2024

@tridge The current way it works is "all", or - "from selected" (if a row is selected) This is working fine for us (who are the only users of this that I am aware of) :)
Would you say changing the way it works to "selected cells" is required? Or is that just a slight preference you have?
Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants