Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
VuhDo VuhDo
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 279
    • Issues 279
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • VuhDo
  • VuhDoVuhDo
  • Issues
  • #376

Closed
Open
Created Jun 18, 2021 by Kris@krijos

[Question] Code design

When looking at how the bars are updated it seems that every button (as I have understood that is the corresponding mouse click?) is looped through to update the bar state for every button. Is there any reason why it is written like this instead of updating the bars against a single button? The way I am thinking is that since it is just a visual hook is there a reason I am missing as to why it is important to update the bar state for every button? Example function to this would be "VUHDO_updateIncHeal" where tAllButtons is looped through to update the value ranges for the incoming heals, which to me seems like a visual thing that could be done by only looking at a single button?

Edited Jun 18, 2021 by Kris
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking