Jump to content

Joel Bodenmann

Administrators
  • Posts

    2,656
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Joel Bodenmann

  1. Can you post a screenshot that shows the problem?

    Also, there are the high-level calls gwinHide() and gwinShow() which you should use. gwinSetVisible() is fine too though, but check the last parameter.
    You should definitely not manually touch the flags.

  2. The SSD1306 is a flush-based GDISP driver. The driver maintains a framebuffer itself which needs to be copied to the actual display controller's framebuffer. That operation is called flushing. Try to call gdispFlush() after rendering. You will find configuration options for flushing in the configuration file and more information in this forum.

  3. Yes, that's possible. With µGFX, almost anything is possible in these regards.

    • You can use a pixmap which is only the size of the button, render the button and then blit the finished one to the actual framebuffer
    • You can also implement full-screen double buffering
    • You can also implement driver level double buffering
    • You can also implement hardware supported double buffering
    • ...

    What works best (and what's possible) depends on the application, used platform, available resources and so on. There's no general guide to double buffering. In our daily work for customers we use all of the methods above. As always: The right tool for the right job. Each method has different advantages, disadvantages, requirements, complexities and so on.

    You might also want to keep in mind that flickering can occur from different sources.

  4. You might need to increase the values of GMOUSE_ADS7843_FINGER_CALIBRATE_ERROR and GMOUSE_ADS7843_PEN_CALIBRATE_ERROR in your board file. They are currently set to 20 and 2. Those are the distances in pixels which the fourth control crosshair is allowed to have as tolerance after the calibration has been applied. 2 and 20 are some very low values. Try higher ones.

  5. I guess you simply didn't click the Close button in the target editor dialog. I'll consider renaming that button to something like Apply or Save.

    I'm completely unable to reproduce the issue with the image.

  6. Release v0.23.3 is now available for download. Changelog:

    • Cleaning the project / regenerating the project no longer removes the output directory itself but only its content
    • Fixing issue with auto-sizing images on multi-state images for widgets that take multiple images for multiple states
    • Fixing issue with image resource editor dialog
    • Adding more userfriendly messages to the image resource editor dialog
    • Fixing issue with invalid container code generation
  7. Hi,

    This is basically simple math. The most commonly used interpolation algorithms are usually the extremely simple linear, quadratic or cubic ones. However, what algorithm you choose depends almost only on your application (on what kind of data you're plotting). Sometimes you might want to resort to splines instead.
    Regarding libraries: Usually this stuff is extremely simple (it's basic math). I am sure that there are tons of great libraries for generic data interpolation and so on, but on an µGFX application you're usually dealing with quite a static environment where your data is always very similar. Therefore, I'd recommend to just figure out what matches your data the best and then implement that function in your application.

    TL;DR: What algorithm to use really just depends on the data you're plotting.

  8. Thank you for your feedback :)

    I've added everything that wasn't already on the list to our todo list. Stuff like the post-generation scripts and the start-up color won't be done quickly, but we're getting there. I assume that we'll have an update by next week.

     

    Quote

    Can I add/change gfxconf.h defines? For example, I want to add GDISP_NEED_UTF8 and GDISP_NEED_PIXELREAD and some other defines.

    Those will eventually be added to the Target editor.

  9. Glad to hear that you managed to get it working.

     

    33 minutes ago, aymen said:

    But i still have a question : is it possible to launch the calibration process manually? For example only if i push a button at start up or if i have a jumper in a given position...

    I can't check right now but as far as I know there's no high-level API call for that at the moment.

×
×
  • Create New...