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

"fillGradientRect" not reacting on y-koordinate using "VLINEAR" #601

Closed
brutzler opened this issue Aug 6, 2024 · 5 comments
Closed

"fillGradientRect" not reacting on y-koordinate using "VLINEAR" #601

brutzler opened this issue Aug 6, 2024 · 5 comments
Labels
stale Inactive issues

Comments

@brutzler
Copy link

brutzler commented Aug 6, 2024

Carefully written Issues are more likely to be given priority.
丁寧に記述された報告は優先して対応される可能性が高くなります。

Environment ( 実行環境 )

  • MCU or Board name: [ESP-WROOM-32|]
  • Panel Driver IC: [RGB-Display]
  • Bus type:
  • LovyanGFX version: [v1.1.16]
  • FrameWork version: [ArduinoESP32]
  • Build Environment: [PlatformIO]
  • Operating System: [Windows]

Problem Description ( 問題の内容 )

using fillGradientRect the Y-coordinate looks always to be 0.

Thats my code.
tft.fillGradientRect( 300, 199, 150, 300, heatMapGradient, lgfx::VLINEAR );

instead of the "199" it is a "0" used. -> The grafic is always on top of the display.
Using lgfx::RADIAL instead of lgfx::VLINEAR the grafic is moving as expected

Expected Behavior ( 期待される動作 )

Actual Behavior ( 実際の動作 )

Steps to reproduce ( 再現のための前提条件 )

  1. step1
  2. ...

// If possible, attach a picture of your setup/wiring here.

Code to reproduce this issue ( 再現させるためのコード )

Please submit complete source code that can reproduce your problem.
あなたの問題を再現できる完全なソースコードを提示してください。

// the code should be wrapped in the ```cpp tag so that it will be displayed better.
#include "esp_log.h"

void app_main()
{

}

// If your code is longer than 30 lines, GIST is preferred.

@brutzler
Copy link
Author

brutzler commented Aug 7, 2024

I want to say: whatever y-coordinate I am using (199 in my example), the grafic is not on the expected place. It always stays on the top of the display. Looks like the function is ignoring the value and always using a "0".

tobozo added a commit that referenced this issue Aug 7, 2024
@tobozo
Copy link
Collaborator

tobozo commented Aug 7, 2024

hi, thanks for spotting that 👍

a fix has been pushed

@brutzler
Copy link
Author

brutzler commented Aug 7, 2024

TY for quick fixing this.
Working now as expected 👍

Copy link

github-actions bot commented Sep 6, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Inactive issues label Sep 6, 2024
Copy link

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Inactive issues
Projects
None yet
Development

No branches or pull requests

2 participants