Can Any help me with my F7

I need to run my test script to determine if the buttons are properly mapped then. I'll look into it.

Ok, I've fixed the trims. they should all work in the proper directions now.

I've added your changes for the new character mappings. I also fixed the battery and txpower displays so they can show on the top row.

While you are free to try, I probably would give up on the curve function. I assumed we'd just need to display the x/y values rather than trying to draw them.
I know that the F7 video doesn't work. I have spent no effort to enable it on the F7 as yet. MicroUAV never completed that work either. I'll get to it eventually.

Nice. I merged all this into the trunk. you don't need to continue working on the 'devof7' branch anymore.

The only thing I didn't merge is this:Thatdoesn't look right. If LCD_SCREEN_LINES is the wrong size, we should just increase it. Can you explain why this is needed?

You can work on the devof7 branch if you like. Just it is no longer needed.

There are 12 lines defined, and the count is zero based, so the lines are numbered 0 through 11. That is why we use i < LCD_SCREEN_LINES. So using i <= LCD_SCREEN_LINES would clear 13 lines which doesn't match. Soeither LCD_SCREEN_LINES should be '13' or something else is wrong.

I'm not sure I understand. the LCD_DrawLine function has 2 points (x1, y1) and (x2, y2). I don't understand how you would get 3 points from that. If what you want is increade resolution, you could look at the work I did for the F12E, or you could look at how double-size fonts work. On the F12E we create a virtual canvas (maximum size is 72x72) which is mapped into 24 custom font characters. You can only use lcd_gfx functions inside that window and it works by creating custom font characters. The latter part isn't possible on the F7, but you could potentially generate a higher resolution matrix (maybe 2 pixels per character) that would give you the info you need.
The font doubling works by doubling the line height (and width) . So for the F12E, we tell Deviation the screen is 66x26 even through in realitywe can only display 33x13 characters. this half-step is useful for alignment and maybe thatwould work for you as well.

Several users are using this (albeit on a F4), but there are lots of little screen issues that need work. there are several open tickets on the bugtracker, or you can ask in the F4 trhead for feedback. You definitely need to start with the current nightly builds though. There has been a huge amount of code reoganization since 5.0 was released, and porting changes from older code to the current trunk could be challenging depending on the scope. Also, we moved from bitbucket to github, so you'll need to refresh everything anyway.