bugfix: hexes should accurately respond to pointer x, y #2253

[andretchen0]

This fixes #2253.

hitArea points were producing a polygon of the wrong size.

The code's a bit hacky, as the width/height dimensions in Hex are converted to polygon points using some "magic" numbers.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
ancientbeast	✅ Ready (Inspect)	Visit Preview	Jul 6, 2023 9:40pm

[ghost]

👇 Click on the image for a new way to code review

Legend

[DreadKnight]

@andretchen0 Unlike HoMM3, we squished the hexagons a bit so that they seem in perspective in order to enhance that.

[DreadKnight]

@andretchen0 Tested, while not pixel perfect, still a huge improvement and it also fixes a very weird issue apparently:

[andretchen0]

@andretchen0 Tested, while not pixel perfect, still a huge improvement and it also fixes a very weird issue apparently

Thanks for testing. Will have a look tomorrow.

[DreadKnight]

@andretchen0 Ok, will merge as it is right away; you fixed that stuff I made the gif for, so no worries about it 👍🏻
Anyway, if you manage to make it more pixel perfect, feel free to make another PR and even target the old issue.

[andretchen0]

@andretchen0 Tested, while not pixel perfect, still a huge improvement and it also fixes a very weird issue apparently:

Hold on. Is the issue in the gif you posted the "weird issue [that was fixed]" that you were talking about? Or is it still an issue with this PR?

I can't reproduce anyway.

Edit: nevermind. We're both posting. I just saw your response. ;)

[DreadKnight]

@andretchen0 Tested, while not pixel perfect, still a huge improvement and it also fixes a very weird issue apparently:

    [
      
    
        ![2023-07-07 01-00-48 (trimmed)](https://user-images.githubusercontent.com/587487/251585743-954b5279-de59-4007-88f2-be397b34d51a.gif)
      ](https://user-images.githubusercontent.com/587487/251585743-954b5279-de59-4007-88f2-be397b34d51a.gif)
    
    
      
        
          
        
        
          
          
        
      
      [
        
          
        
      ](https://user-images.githubusercontent.com/587487/251585743-954b5279-de59-4007-88f2-be397b34d51a.gif)

Hold on. Is the issue in the gif you posted the "weird issue [that was fixed]" that you were talking about? Or is it still an issue with this PR?

I can't reproduce anyway.

That was something I discovered in the beta before merging that I wasn't fully aware of; opened new issue just to close it with this PR as well, for the sake of issue history. All good.