• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 513 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SIMPLELINK-MSP432-SDK_3.40.01.02 - Graphics Library String Bug

Derrick
Intellectual 395 points

Hi,

I'm not sure which forum this belongs in, but there appears to be a bug in the graphics library part of the SimpleLink MSP432 Software Development Kit (SDK). It looks like the string drawing functions do not work properly with clipping regions set within the drawing context if it does not start at the origin (x = 0, y = 0). If the clipping region is set elsewhere, nothing is drawn. The other drawing functions appear to work fine with any arbitrary clipping region. Has this been reported elsewhere? Is there a quick fix for this? I wanted to avoid having to rebuild the grlib.a myself if possible.

String functions in question: dev.ti.com/.../group__string__api.html

  • 0
    TI__Mastermind 40195 points

    It seems quit strange. I haven't meet this problem when playing with MSP432.

    Are you using CCS? To avoid build grlib.a automatically, you can put the .c file including String_api function in your workpace. If it doesn't work, put all grlib.a related files into workspace.

    Eason

  • 0 in reply to Eason Zhou
    Intellectual 395 points

    Eason Zhou said:

    It seems quit strange. I haven't meet this problem when playing with MSP432.

    Are you using CCS? To avoid build grlib.a automatically, you can put the .c file including String_api function in your workpace. If it doesn't work, put all grlib.a related files into workspace.

    Eason

    Eason,

    I took your advice and just made my own local copy with the fixes. I have it working and we can move forward with this.

    The fix was to add ySave in every scenario that checks the clipping region. For example:

    //
// See if the bottom of the clipping region has been exceeded.
//
if((ySave + y + y0) > sContext.clipRegion.yMax)
{
	//
	// Ignore the remainder of the on pixels.
	//
	break;
}

  • 0 in reply to Derrick
    TI__Mastermind 40195 points

    Thank you for help! I will convert this bug to our related team!

    Eason

**Attention** This is a public forum