BRT Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to the Bridgetek Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ Bridgetek Support

Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Simon

Pages: [1]
1
Hello Bridgetek Community,

with the EAB 1.4.0 I converted fonts some months ago. In some screens I used the tabulator to save commands in the display list. This worked fine with the fonts I created at that time.
With an update of the EAB to version 2.1.0, the tabulator can no longer be displayed. Instead, a white box appears on the display.
After some research, I noticed that the tabulator is not even present in the font used, but until the update, it was still generated with in the EVE font. Since I would like to supplement the font, I would like to ask whether a checkbox can be inserted in the EAB, with which one can generate the tabulator again with into the font.
Possibly someone has a suggestion to circumvent the problem in another way?
I am looking forward to your feedback.

Greetings Simon

2
Discussion - EVE / UTF-8 Encoding Error
« on: March 06, 2020, 10:22:54 AM »
Hi there,

I have an issue on the UTF-8 encoding used with the BT816-Chip. For the use of some special symbols i need font-elements that are adressed by UTF-8 encoding with four bytes. So I converted this font https://fontlibrary.org/de/font/symbola#Symbola-Regular that contains the symbols I want to use with EVE Asset Builder v1.2.0.
After progammming the font on my flash, I tried to adress i.e. the UTF-8 code F09FA183 to type a special arrow. The display didn't show anything.
Then I tried to use a symbol with a three byte UTF-8 encoding i.e. E2AF86 (a different arrow symbol) and everything worked fine.

I also tried different ways to use the symbol:
One try was about putting each byte into a text array by hand like shown below, what worked as describes up to 3-byte encoding.

Code: [Select]
switch (direction)

         {
            case 0://arrow up
            {

               arrow_x = x1+((x2-x1)/2)-20;
               arrow_y = y1+((y2-y1)/2)-12;

               EVE_cmd_setfont2(13, SPECIAL_FONT2_RAM_ADR,0); //special font

         //this arrow is displayed correctly
               LCD_FuncData.text_buffer[0] =0xE2;
               LCD_FuncData.text_buffer[1] =0xAF;
               LCD_FuncData.text_buffer[2] = 0x85;
               LCD_FuncData.text_buffer[3] = 0;
               break;
            }
            case 1://arrow down
            {
               arrow_x = x1+((x2-x1)/2)-20;
               arrow_y = y1+((y2-y1)/2)-12;

               EVE_cmd_setfont2(13, SPECIAL_FONT2_RAM_ADR,0); //special font

         //this arrow is not shown on display
               LCD_FuncData.text_buffer[0] =0xF0;
               LCD_FuncData.text_buffer[1] =0x9F;
               LCD_FuncData.text_buffer[2] = 0xA1;
               LCD_FuncData.text_buffer[3] = 0x83;
               LCD_FuncData.text_buffer[4] = 0;
               break;
            }
  }

  if (button_down)
        {
               EVE_cmd_button(x1,y1,x2-x1,y2-y1,13,EVE_OPT_FLAT); //in here the button and its label is generated by sending the text array content to the BT-Chip
        }
        else
        {
               EVE_cmd_button(x1,y1,x2-x1,y2-y1,13,0);
        }

Another try I started in the EVE Screen Editor with only a few lines:

Code: [Select]
CLEAR(1, 1, 1)
CMD_SETFONT2(13, 0,0)
CMD_TEXT(123, 117, 13, 0, "🡃?")

I opened the font data in the emulator and loaded my font. This time the display showed two questionmarks instead of the arrow. In the Inspector view i could see that the generated code actually adresses the same section as for the questionmark character.

So my question is if there is an availability to use the Symbols with four byte UTF-8 encoding or if the BT-Chip restricts the usage of them.

Hopefully somebody can answer me that question.

Regards,
Simon

Pages: [1]