FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  


Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support

New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Messages - scorpioprise

Pages: [1]
ThankYou, pauljiao ,
your way is a kind of hack method. 
I understand it, but as far as my final sistem will have something like 150+ values, maybe working on the code side (Eclipse) will be the better approach, building the interface before and hacking after.

Nontheless, I'll give this strategy a try  ;)

I DID IT  ;D ;D ;D ;D Hope You were stille following, but also for future readers.
So, that's easy, when you get it how it works!

Think in a "DataModel" way, that is "I store something somewhere, for who needs it"

Say you put something (the value) in a variable somewhere. Your variable will be updated somewhere in your code.
In my example, an event on UART0 toggles a boolean.

Then, here's the trick: find the label you want to change (will be named like you read in ESD), so you can search a  <PAGENAME>_<ESD_LABEL_NAME>_Text__Property

Pagename = FirstPage;

Now locate in <PAGENAME>__Generated.c file the

Code: [Select]
static const char * FirstPage_CELL_VAL_1_Text__Property(void *context);You will find it slightly different. Because you will find

Code: [Select]
static const char * FirstPage_CELL_VAL_1_Text__Property(void *context){return "ESD";}if "ESD" was the text you put via EveScreenDesigner.

Now implement it another way, like
Code: [Select]
int i=0;
static const char * FirstPage_CELL_VAL_1_Text__Property(void *context) {
   char * str;
   if (upcounting) {
      sprintf(str, "%d", ++i);
   } else {
      sprintf(str, "%d", --i);


   return str;

And "magically" you're done! Because the EVE engine works for you, automatically refreshing the value read from somewere else.
Obviously you have to let it do so, leaving to it the update and render slots on your widgets.

Hi Jimmy
Hi Christian

If you did solve your problem (which is essentially the same as mine) it would be great to get some pointers...


I'm stuck on it too... did you get some updates?
I'm building a console & canbus driven display, and I'm trying my best to understand the way to pass data to screen.

New Member Introductions / Re: Hello from Italy
« on: November 28, 2018, 10:25:54 AM »
Hi mosè, Filippo from Genova here ;-)

New Member Introductions / Hello From Italy
« on: November 28, 2018, 10:24:31 AM »
Hi everybody!

I'm building my first display, and I'm juggling with ESD, Eclipse, a Ft901 demo board and a couple of Ft812 - Ft813 demo display boards.
So I'm tryng the community approach, and I hope I can bring back experience from the fields!


Discussion - Software / From EVE Screen Designer to Eclipse... and back?
« on: November 27, 2018, 04:44:56 PM »
Hi, I'm new in using FTDI chips, but I'm building a custom display with FT901 and FT812/FT813.
As far as I've understood, once I export from ESD to Eclipse there is no way to get it back into ESD. Is that right?

The matter is that the GUI i'm working on will be very very complex, so I have to try and rebuild many times. And I have to add my layer of custom code in it.

Say it has a serial (UART0) interface working under the display interface, that can operate both indipendent speaking with the can-bus interface.
So both will call methods to write and read the can-bus.

First step is altering the code, ok, that's fine.
But if I have to add interface elements? How can I get it back into the ESD?

Otherwise I have to use the mighty power of git to catch the changed GUI things and keep the handcoded ones?

Hope you can help me understand.

Pages: [1]