-
-
Notifications
You must be signed in to change notification settings - Fork 911
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
Fixed wrapping with Artificial Horizon #1324
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does completely solve the problem, see
I also think that trying to solve this problem by enforcing a specific origin point on the individual OSD elements with generated preview is not an ideal solution - this will require extra scrutiny to make sure that this constraint is not broken by any future changes.
I think in order to fix this in a robust way, what needs to be done is that the offset for the drag / drop attachement point that was introduced in #1165 and #1172 is taken into account when checking if the new position is clipping: Before #1165, OSD.searchLimitsElement()
would always return the total extent of the element against the fixed attachement point for drag / drop, but now this needs to be relative to the variable attachement point.
I think we should able to use one logic to apply to all osd elements:string, array of char and array of strings.
|
@dronejunkie: Yes, that sounds about right - what is neglected in the current code is proper calculation of the mouse cursor position relative to the element. |
Sorry Michael, hopefully I will get sometime next week to completed this. |
This issue / pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
AUTOMERGE: (FAIL)
|
Closing as inactive. Can be reopened when @dronejunkie decides to continue his work. |
I'll reopen this - this is still a bug and needs to be fixed, and if somebody wants to spend some time on fixing this up it will be appreciated. |
SonarCloud Quality Gate failed. 1 Bug No Coverage information |
@dronejunkie - Hi Jack - any chance you can review this again? It would be great to fix this for 4.3. |
Hi Chris,
Due to work and other commitments I do not have time anymore. Sorry about
that.
J.
…On Sat, 4 Dec 2021, 10:18 am ctzsnooze, ***@***.***> wrote:
@dronejunkie <https://github.com/dronejunkie> - Hi Jack - any chance you
can review this again? It would be great to fix this for 4.3.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1324 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGA2NXHAPV7A4XT5WN3O4ADUPFF23ANCNFSM4G7GXOVA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
is this still required, or is master working as expected now that HD was done? if still required, need rebase from master and continued testing. |
This PR is to fixing an existing issue with artificial horizon wrapping in some situation. I did some regression testing as well with other single char elements like sidebar and stick overlay. No issue.