Jump to content

Joel Bodenmann

  • Content Count

  • Joined

  • Last visited

  • Days Won


About Joel Bodenmann

  • Rank
    µGFX Developer

Recent Profile Visitors

11,389 profile views
  1. It's a bit difficult to judge based on the image with the angle & blury-ness but it looks like there's an issue in the setup of the display controller scanlines. The ili9341 display controller families are known to have various issues such as mis-matching silicon revisions and suppliers simply shipping a slightly different chip. This usually results in incompatible initialization routines. Check out the GDISP driver file (inside something like /src/drivers/gdisp/ili9341/) and check the initialization routine. Usually the manufacturer and/or supplier of a display module will provide you with minimal sample code. Simply take the initialization routine you get from the sample code and plug it into the GDISP driver. I'd also recommend you to use the forum search - there's plenty of these issues regarding ILIxxxx display controllers around.
  2. Hello & welcome to the µGFX community. Please excuse the inconveniences you experienced. µGFX is very much alive and active. There has simply been an error in the automatic ordering system. All of your orders were received and by now you should have received a manual response to your purchase inquiry. Please do not hesitate to contact us again should you still not have received anything.
  3. I've never heard of anyone writing a µGFX GDISP driver for the NT35510 driver. However, writing a driver is very easy! You can find the corresponding documentation here: https://wiki.ugfx.io/index.php/Display_Driver_Model You can find examples in form of dozens of existing drivers in the µGFX library directory under /drivers/gdisp Furthermore, we're happy to help wherever we can! Just ask if you have any questions.
  4. The imagebox should automatically redraw when necessary. The only thing you have to make sure is that the image remains opened. The imagebox widget will simply clear the area if the assigned image is not opened (i.e. "nothing" will be rendered).
  5. We're happy to help where we can - don't hesitate to ask on the forum. I assume you're referring to the attachment of a few posts above yours? I had no issues downloading it. I've re-attached it to this post. Let me know if the issue persists.ArduinoIDE_ESP32_ILI9341.zip
  6. That should definitely go into a separate topic :)
  7. The µGFX library is actively maintained. There is currently no release date for µGFX v3 as we want to put our best efforts into it. The development repository of v3 is not public hence there's very little publicly visible efforts. µGFX v2.9 is known to be stable. While we do not currently add new features to it we are applying patches & hotfixes as they appear. We can only recommend using the µGFX library in your commercial product 😉 If it helps: There's an equally named company behind the µGFX library - This is not just a floating piece of software. Also professional support is being handled through this company.
  8. This was fixed in commit ff93884f71f783627f196330fd0c9f6a639bee56.
  9. Hello & welcome to the µGFX community! It would be definitely very appreciated if somebody could update the demo
  10. Hello & welcome to the µGFX community! This is certainly possible. The graph widget demo also plots multiple values in the same graph. However, in this case you'll most likely just end up having more than one graph widget/window on the same "display page".
  11. Hello & welcome to the µGFX community! Thank you for bringing this to our attention. We'll put it on the ToDo list for checking. Could you please leave a short description (and if necessary examples) as to why you think that this is the case? Some screenshots might also be helpful if possible
  12. Feel free to open a thread in the support section of this forum stating what you're trying to accomplish, what you already have (how far you got) and what problem(s) you're facing. "Doesn't even compile" is not enough information for us to help you in any way.
  13. If you're having issues compiling µGFX successfully, you can always open a thread in the support forum where you'll find people that are happy to help where they can. µGFX is being compiled a lot against / for the win32 platform as it is being used a lot as a development environment.
  14. Hello and welcome to the µGFX community. Providing pre-built libraries (either static or dynamic) for µGFX is not a very good idea. The library makes heavy use of compile time optimization based on the various configuration options given in the main configuration file and the driver configuration files. All those compile-time options influence the code that is being presented to the compiler during the pre-processor stage. Therfore, the binary code produced by the compiler (and eventually also the linker) depend on those options. This reason makes it very useless to publish binaries. For certain things such as the GDISP feature set we could just enable everything which would result in a larger binary and call it a day but for many of the other options that's simply not possible because the pre-processor makes changes based on the underlying system, the compiler being used and so on. Furthermore, some options are application specific (eg. GDISP_NEED_MULTITHREAD). TL;DR: Publishing pre-built binaries for uGFX is not a good idea because of lots of pre-processor modifications.
  15. Thank you for bringing this to our attention. We have fixed the problem.
  • Create New...