Search Results

Search results 1-18 of 18.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Memory device seem not working

    andrea_cp - - emWin related

    Post

    Source Code (59 lines)Hello everybody, we've a user interface developed with the emWin library and now we'd like to "optimize" its appearance and its behaviour displayed data are refreshed. In particular, we've a window with a textbox showing a value, which can be managed through an encoder: rotating this latter allows to increment (cw) or decrement (ccw) the value. When encoder is rotated relatively fast, application has to refresh value faster and this is reflected appearance, which is "degrad…

  • Display emulation with IAR

    andrea_cp - - emWin related

    Post

    Hi everybody, We need a way to make screenshots of the user interface we've developed with emWin. Looking for that on the Internet and on the forum, I've found functions GUI_BMP_Serialize() and GUI_BMP_SerializeExBpp(), but they cannot help us since we're working in an embedded system based on a M4 ST microcontroller. So we switched to the on pc simulation, but these requires the Microsoft Visual Studio IDE. Is there a way to simulate the user interface on the host pc using IAR IDE? Thanks Andre…

  • Drag touch on buttons

    andrea_cp - - emWin related

    Post

    Hi, We've a touch screen application, in which we use different widgets, in particulare BUTTONs. We've noticed that, if we've more than one button in a window, touching on one button triggers a WM_NOTIFICATION_CLICKED message: this is ok. Touching on a button and moving the finger while keeping touched, trigger WM_NOTIFICATION_CLICKED and a WM_NOTIFICATION_MOVED_OUT if the finger is moved out of button area: that still ok. But why, if I press a button and, keeping touched, I move the finger on a…

  • Hi, I'm developing a user interface on a 320x240 display, with 4-wire analog touch interface. Everything is working well, just touch seems to be to much rough. Our problem is that, even if we calibrate the touchscreen with a 9 points method, still persist a lot of wrong revealed touch: i.e., with reference to the image attacched, finger is pressed on the button '+' (45x45 pixels), but the library detect a touch on the slider, at least 20 pixels over the button itself. Calibration is done run-tim…

  • Dialog background

    andrea_cp - - emWin related

    Post

    Hi, simple than I was trying. WINDOW_SetBkColor() solved the problem. Thanks, Andrea

  • Hi Sven, that the point I came out me too. We've a resistive 320x240 touch screen display, with buttons 80 pixels wide and 45 pixels height: not so big, but quite usable. Unfortunately, display is not a the same level of the case in which it is placed, but there is a little thickness that does not make so friendly to use buttons on the borders. We've noticed that pressing the finger and, while keeping pressed, moving across the screen, a WM_NOTIFICATION_CLICKED message is emitted every time the …

  • Dialog background

    andrea_cp - - emWin related

    Post

    Hi, is there a way to change dialog background color? I've tried with function calls to GUI_SetBkColor( GUI_BLACK ) and GUI_Clear() in message WM_PRE_PAINT, but with no luck: background still remain white. Any idea? Many thanks Andrea

  • Hello Sven, many thanks for your reply: now behaviour of the Pressed variable looks as expected. Just one more question: why sometimes, and not so rarely, WM_NOTIFICATION_RELEASED message is not sent when a button released? Thanks for your support Andrea

  • Hi everybody, I'm working on a user interface base on emWin functionalities and everything is working in the right way. Now, I'm looking to optimize touch, but while debugging I've faced a strange behaviour to me. I've Window Manager enabled, a simple window with 4 buttons and a custom callback assigned to this window and I would like to better understand the "flow of messages", such as WM_TOUCH and WM_TOUCH_CHILD. Putting one breakpoint on the WM_TOUCH_CHILD case and on on the WM_NOTIFICATION_C…

  • Dropdown scrollbar color

    andrea_cp - - emWin related

    Post

    Hi guys, I'm facing some problems with the automatic scrollbar of a dropdown widget. I would like to change the color of the arrows, thumb area and shaft using function DROPDOWN_SetScrollbarColor() but I still get a skinned scrollbar, even if I've removed skinning from the "father" dropdown widget. How to remove skinning from automatic scrollbar of dropdown? I've thought about calling routine WIDGET_SetEffect() on scrollbar, but how to get scrollbar handler to pass to this function? Here my code…

  • Remove skinning

    andrea_cp - - emWin related

    Post

    Hi guys, I'm facing a problem with the skinning functionalty of the widget: I would like to remove it, but unable to get this goal. I've tried by writing this define in GUIConf.h: Source Code (1 line) Looking at where this symbol is called, I've found it's used in header Widget.h at this point Source Code (3 lines) So I've directly chagned the symbol here and recompiled my project: nothing has changed.Hope anyone could help me. Many thanks for your support Andrea[i] [/i]

  • WM_HideWindow not hiding

    andrea_cp - - emWin related

    Post

    Hi @golf2109 the way you has written is the one I've followed, as you can see in the example code of my question, but after an hide-show "cycle", I'm not able to hide the widget one more time.

  • WM_HideWindow not hiding

    andrea_cp - - emWin related

    Post

    Hi guys, I'm working with IAR and STemWin to create an ui for an application of us, builded for an ST32F429-Discovery board. I've noticed a strange behaviour hiding/showing a widget, more specifically a button. Below my code: Source Code (39 lines) This function is called every time the very first or very last widget of a "list" is reached, hiding the previous and next button respectively. The strange thing is that after this "sequence" of actions, shown->hidden->shown, I'm not able to hide the …

  • Hi Sven, many thanks for your answer, it solved the problem Previously, in my PID_Exec() function, I called GUI_TOUCH_StoreStateEx() only if new touch state was different form previous one, therefore only on press/release event: this implies taht on "pressure and move", like when using LISTWHEEL, only the first touch was detected, but nothing else. Changed my code according to yours and everything works right. Thanks a lot

  • Hi everybody, I'm working with an ST STM32F4-DISCOVERY board and I would like to use the listwheel widget in my ui application, but it seems it does not working well with a resistive touch screen, as the one of the demo board. In fact, I'm unable to make the listwheel scrolling, it just moves in a strange manner sometimes, when I double touch a point. I aslo tried the example WIDGET_Listwheel.c, but it does not work (I know it's not optimized for an embedded application, but I just tried if it's…

  • Hi everybody, I'm facing some strange behaviours in my UI application, base on the STemWin. Foundamentally, the structure of the panel displayed is divided into 4 child windows, as shown in the image attached. The "bars" are just used for navigation purproses, while it's the Central Window that contains relevant widgets/data. Problems begin when a change from a panel to another is requested: Central Window is cleared and re-created with new widgets, while toolbars remain without beeing deleting,…

  • Widget reposition not working

    andrea_cp - - emWin related

    Post

    My fault, re-reading the user manual at the decription of WM_SetWindowPos(), I've found the trick: "xPos New position in X in desktop coordinates. yPosNew position in Y in desktop coordinates." Sorry

  • Widget reposition not working

    andrea_cp - - emWin related

    Post

    Hi everybody, I'm trying to create a User Interface application with the STemWin library and I'm facing a problem with the reposition of existing widgets, in particular of BUTTONs. The "standard" structure of a window of my application is as shown: ------------------------------------- | Top toolbar | ------------------------------------- | E | | N | | m | | a | | p | | v | | t | CENTRAL | i | | y | | g | | | | a | | | | t | | | | e | ------------------------------------- Where there are 4 windo…