Jump to content

MobileWill

Members
  • Posts

    103
  • Joined

  • Last visited

Posts posted by MobileWill

  1. Thanks. Looks like I was pretty close. But I am hitting GDISP_IMAGE_ERR_BADFORMAT. Which happened last night. It was unhanded exception and then finally got the GDISP_IMAGE_ERR_BADFORMAT. 

    I know the surface works because I can Blit it and it shows correctly. 

    I am PM you when my code in a bit.

  2. Do I have to make sure the pixmap is setup before creating the container? Any chance I can get a simple example of setting up the container?

     

    I am trying to leave the studio code untouched and then update the container after. I have tried both ways. 

  3. I am a bit confused. Once you set the image as the draw routine. How do you link it to the pixmap object?

    For the container I have

    wi.customDraw = gwinContainerDraw_Image;
    
    wi.customParam = gdispPixmapGetMemoryImage;
    

     

    If I want can I set the custom draw later instead of on creation of the widget using gwinSetCustomDraw?

  4. So strange. I copied the toolchain from Eclipse to Embitz and then had to tweak some compiler and assembler options for it to even compile. I added -mthumb and -Dthumb.

    Seems to work fine now, no display issues. This only happened with -O2 in case someone else runs across this. I hope Embitz gets another update soon. 

     

  5. I am using window in a container and the list box doesn't work right. I have it hidden and then visible when a button was pressed. The list box parent is the that page so not tied to any of the other containers that are on top. The issue is I can't interact with it once its displayed on top of the container that has a window in it. 

    Any ideas? It won't even scroll. Must be a conflict with the window or maybe the pixmap?

    If I use the pixmap image as the drawing routine for the container do I need the window at all? Maybe if I remove the window then the list box will work. 

  6. So I was able to try pixmaps in Eclipse and wow its fast. So much better. Took awhile to implement. I may have to rethink all my logic now that I have so much more flexibility. What I ended up doing is keeping the pixmap open and just update the graph in the pixmap and just write to the display once. Hope I don't run out of RAM later. 

    Should be fast enough that the user won't notice the draw after the splash page is closed.

    Only thing now that I am using Windows in an container is the list box doesn't work right. I have it hidden and then visible when a button was pressed. The list box parent is the that page so not tied to any of the other containers that are on top. The issue is I can't interact with it once its displayed on top of the container that has a window in it. 

    Any ideas? It won't even scroll. Must be a conflict with the window or maybe the pixmap?

    I just noticed you added option 2. That sounds like that could work very nicely. Hmm. Will it know to redraw if I update the pixmap or I just issue a redraw? The issue with the list box will probably still be there. 

  7. Just wanted to mention that now that Eclipse is working. uGfx is way faster and the code size is smaller. Because of the nature of my project I can see that it is also using way less power, 30mA less. So strange I would of never excepted that. I guess the speed is why power usage is less. Completing threads faster so more idle time. 

    I don't know if it was because I used Eclipse or just the Makefile vs Singlefile inclusion with Embitz.

    Once I get Embitz working with the Makefile I will have to compare. 

    So glad I spent the extra time to get the Makefile working. ;)

  8. So after trying Makefile with Embitz I ended up with the same errors as Eclipse. Go figure. But in the process I learned a lot about the Makefile system. I guess my inexperience was the source of the problem. I didn't realize every .c file has to be added to the Makefile. I guess I am used to auto discovery. So now in Embitz all the Makefile errors that were the same as Eclipse are fixed. I just have one left about osalDbgAssert but that is a ChibiOS problem. 

  9. When using the makefile I get tons of is not defined warnings for stuff that is commented out int he gfxconf.h

    For example

    GWIN_LABEL_ATTRIBUTE

    GWIN_NEED_LIST_IMAGES

    GFX_EMULATE_MALLOC

     

    I would like to get rid of the warnings. But in gfxconf.h it mentions to leave them commented out. 

     

  10. Oooo looks nice. Still cheaper than like Keil too. 

    Yeah Embitz has great potential just needs some polishing. Fix the debugger and OS Support and I would be set. 

    Hopefully tonight goes well. I would like to try out some of the larger demos too. I should be able to now. I think in Eclipse it would of worked now that I figured to add syscalls.c to the makefile. You should add it to the uGfx makefile examples. 

×
×
  • Create New...