-
Notifications
You must be signed in to change notification settings - Fork 520
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
Fix #2581: Marquee auto restart issue #4392
Fix #2581: Marquee auto restart issue #4392
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.
@KevinGitonga Suggested changes.
...oppia/android/app/devoptions/markchapterscompleted/MarkChaptersCompletedFragmentPresenter.kt
Outdated
Show resolved
Hide resolved
...g/oppia/android/app/devoptions/markstoriescompleted/MarkStoriesCompletedFragmentPresenter.kt
Outdated
Show resolved
Hide resolved
...org/oppia/android/app/devoptions/marktopicscompleted/MarkTopicsCompletedFragmentPresenter.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/org/oppia/android/app/topic/TopicFragmentPresenter.kt
Outdated
Show resolved
Hide resolved
Thanks @KevinGitonga. Left one comment--please also add tests once we land on a final solution. Note that in the future I suggest only sending a PR for review once it's completed from your perspective (which includes adding tests). If you'd like first thoughts on a PR as you're finishing (e.g. before tests are written), I suggest marking the PR as a 'draft' and explicitly mentioning when assigning reviewers that you'd like their initial thoughts. This helps better communicate expectations and ensure that reviewers are giving you the type of feedback that you're looking for. |
Hi @KevinGitonga, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue. |
…ely to make it clear.
… ExplorationActivityTest.kt.
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.
Thanks @KevinGitonga. Just had a few follow-up comments--PTAL.
app/src/sharedTest/java/org/oppia/android/app/player/exploration/ExplorationActivityTest.kt
Show resolved
Hide resolved
app/src/main/java/org/oppia/android/app/topic/TopicFragmentPresenter.kt
Outdated
Show resolved
Hide resolved
@BenHenning have added tests and shallow_since config PTAL. |
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.
Thanks @KevinGitonga! I think this has turned into quite a nice solution. LGTM.
@rt4914 since you requested changes, could you please take another look? |
Dismissing since Rajat is out, and original concerns seem addressed.
Actually, dismissing @rt4914's review since his original concerns seem addressed and he's on holiday at the moment. Rajat: if you have any follow-up concerns, please be sure to let @KevinGitonga know. Going ahead and merging this. |
) ## Explanation Fixes #4709 This reverts commit 846657e from PR #4392. See #4709 (comment) for a detailed explanation for why this reversion is the correct approach. Note that this PR will be cherry-picked into the 0.10 release branch for the upcoming MR2 beta release. ## Essential Checklist - [x] The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".) - [x] Any changes to [scripts/assets](https://github.com/oppia/oppia-android/tree/develop/scripts/assets) files have their rationale included in the PR explanation. - [x] The PR follows the [style guide](https://github.com/oppia/oppia-android/wiki/Coding-style-guide). - [x] The PR does not contain any unnecessary code changes from Android Studio ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#undo-unnecessary-changes)). - [x] The PR is made from a branch that's **not** called "develop" and is up-to-date with "develop". - [x] The PR is **assigned** to the appropriate reviewers ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section)). ## For UI-specific PRs only This is a mostly clean reversion of #4392, so see that PR for an idea on how marquees behaved prior to that PR (as this PR returns the app to that behavior).
) ## Explanation Fixes #4709 This reverts commit 846657e from PR #4392. See #4709 (comment) for a detailed explanation for why this reversion is the correct approach. Note that this PR will be cherry-picked into the 0.10 release branch for the upcoming MR2 beta release. ## Essential Checklist - [x] The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".) - [x] Any changes to [scripts/assets](https://github.com/oppia/oppia-android/tree/develop/scripts/assets) files have their rationale included in the PR explanation. - [x] The PR follows the [style guide](https://github.com/oppia/oppia-android/wiki/Coding-style-guide). - [x] The PR does not contain any unnecessary code changes from Android Studio ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#undo-unnecessary-changes)). - [x] The PR is made from a branch that's **not** called "develop" and is up-to-date with "develop". - [x] The PR is **assigned** to the appropriate reviewers ([reference](https://github.com/oppia/oppia-android/wiki/Guidance-on-submitting-a-PR#clarification-regarding-assignees-and-reviewers-section)). ## For UI-specific PRs only This is a mostly clean reversion of #4392, so see that PR for an idea on how marquees behaved prior to that PR (as this PR returns the app to that behavior).
Explanation
Fix #2581
This fix introduces a custom View "MarqueeView" which acts as parent view for the textview in the toolbar this allows the MarqueeView to manipulate the child TextView and allow's it to marquee through translation animation if the text is long enough. It also solves the issue which we had which of text animating over the back navigation icon by attaching the textview inside a scrollview which allows it disappear cleanly without overlapping.
Essential Checklist
For UI-specific PRs only
If your PR includes UI-related changes, then:
Before changes demonstration
marquue_restart_issue_bf.mp4
After changes demonstration
after_demo.mp4
After changes RTL demonstration
marquee_rtl_demo.mp4