OpenGD77

The reason there is a function called RenderRows is because the radios with black+white screens have the screen divided into sections of 8 rows becuase of the way the 1 bit data is organised. And because the UI code is almost completely unified across black+white and colour screen radios, then the ...

Actually I noticed some hender rendering issues on the sweep scan, but I'm not sure why that is happening Probably because of this in uiVFOMode.c: #elif defined(PLATFORM_MD380) || defined(PLATFORM_MDUV380) || defined(PLATFORM_MD2017) #define VFO_SWEEP_GRAPH_START_Y 10 #define VFO_SWEEP_GRAPH_HEIGHT...

Well, you are doing your own special version which just suits you I would argue if it just suits me or every DM-1701 user, but all right. :) I'm not sure that its going to be practical to do a version which also reduces the screen width by 8 or 16 pixles because the bezel obscures that as well. I'm...

Compiled and packaged firmware binary https://www.opengd77.com/downloads/MDUV380_DM1701/Firmware/Experimental/OpenDM1701_SCREEN_HEIGHT_HACK.zip That still crops the left part of the mode text, the right part of the % sign (it looks much worse in life than in the photo), and the left part of the fra...

Becasue you don't need to modify all that stuff Just move the whole display down 8 lines No, that's completely wrong. I don't want the bottom 2 pixels of the zone display cropped. Also moving down the menu 8 pixels is not necessary, leaving everything as-is is better. You don't see the top title of...

Can you send me the firmware so I can test it on mine? My e-mail is ok on qrz.com Unfortunately, since the author of the firmware feels that the way I modified the code is completely wrong, I cannot send you my modified version in good conscience. :( You will need to wait for an official fix for th...

You are doing things completely the wrong way. Tell me, if modify the code so the text positions will be more suitable for the DM-1701: #elif defined(PLATFORM_MD380) || defined(PLATFORM_MDUV380) || defined(PLATFORM_MD2017) #define DISPLAY_Y_POS_HEADER 2 #define DISPLAY_Y_POS_BAR 10 [...] #elif defi...

I never wrote that is not possible, I told you multiple time you have to take care about the rendering, and the way you moved the vertical offset of the header is WRONG. It's not WRONG... Why do you refuse to understand, that it's not the only thing I did? Also take care how many rows we need to re...

Because you RSSI bar is below the 16th pixel line, hence the 200ms update for that part won't be correctly rendered when the RSSI bar moves up and down quickly, and in some occasion some stuff will overlap on screen (in a pretty ugly way ;) ).. I would send you a video of my radio which shows that ...

Re-reading the code, yes, 16 pixels. Hence the RSSI bar is not updated each 200ms, which is bad. Why wouldn't the RSSI bar update? You assume I did not modify the display rendering parts of the code according to the changed position of the header. But I did that (and no, not for every platfrom, ONL...