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

[scroll-view] call _processDeltaMove() in update() #16541

Merged
merged 1 commit into from
Nov 29, 2023
Merged

Commits on Nov 27, 2023

  1. [scroll-view] call _processDeltaMove() in update()

    call `_processDeltaMove()` in `update()`
    
    it should not call  run _processDeltaMove()  in every touchmove event ,  it will take bad performance.
    
    
    Re: #
    
    ### Changelog
    
    *
    
    -------
    
    ### Continuous Integration
    
    This pull request:
    
    * [ ] needs automatic test cases check.
      > Manual trigger with `@cocos-robot run test cases` afterward.
    * [ ] does not change any runtime related code or build configuration
      > If any reviewer thinks the CI checks are needed, please uncheck this option, then close and reopen the issue.
    
    -------
    
    ### Compatibility Check
    
    This pull request:
    
    * [ ] changes public API, and have ensured backward compatibility with [deprecated features](https://github.com/cocos/cocos-engine/blob/v3.5.0/docs/contribution/deprecated-features.md).
    * [ ] affects platform compatibility, e.g. system version, browser version, platform sdk version, platform toolchain, language version, hardware compatibility etc.
    * [ ] affects file structure of the build package or build configuration which requires user project upgrade.
    * [ ] **introduces breaking changes**, please list all changes, affected features and the scope of violation.
    
    <!-- Note: Makes sure these boxes are checked before submitting your PR - thank you!
    - [ ] Your pull request title is using English, it's precise and appropriate.
    - [ ] If your pull request has gone "stale", you should **rebase** your work on top of the latest version of the upstream branch.
    - [ ] If your commit history is full of small, unimportant commits (such as "fix pep8" or "update tests"), **squash** your commits down to a few, or one, discreet changesets before submitting a pull request.
    - [ ] Document new code with comments in source code based on API docs
    - [ ] Make sure any runtime log information in `log` , `error` or `new Error('')` has been moved into `EngineErrorMap.md` with an ID, and use `logID(id)` or `new Error(getError(id))` instead.
    - To official teams:
      - [ ] Check that your PR is following our [guides](https://github.com/cocos/3d-tasks/blob/master/workflows/readme.md)
    -->
    finscn authored Nov 27, 2023
    Configuration menu
    Copy the full SHA
    7e2bb1e View commit details
    Browse the repository at this point in the history