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

Endianness Inconsistency #554

Closed
ghasto69 opened this issue Apr 12, 2024 · 2 comments
Closed

Endianness Inconsistency #554

ghasto69 opened this issue Apr 12, 2024 · 2 comments
Labels
stale Inactive issues

Comments

@ghasto69
Copy link

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

Environment ( 実行環境 )

  • MCU or Board name: esp32-s3
  • Panel Driver IC: ili9341
  • Bus type: spi
  • LovyanGFX version: latest
  • FrameWork version: ArduinoESP32 v2.0.3
  • Build Environment: [ArduinoIDE]
  • Operating System: [macOS]

Problem Description ( 問題の内容 )

Diffirent draw functions expect different endianness:
pushImage expects big endian for both image and transparency
pushSprite expects little endian for transparency
all simple drawing functions expect little endian

Expected Behavior ( 期待される動作 )

consistent endianness over all drawing functions

Actual Behavior ( 実際の動作 )

inconsistent endianness over all drawing functions

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.

Copy link

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 May 12, 2024
Copy link

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

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

1 participant