怎么更改标签文字

就在我点击Enter时，我解决了我自己的问题，不正确地定义了指针对不起所有。



      以下为原文

    And just as I clicked enter I solved my own problem, improperly defined pointers sorry all.  

你能告诉我你是怎么解决这个问题的吗？我也有类似的问题。谢谢。



      以下为原文

    Hi
Could you show me what you did to resolve this please.
I am having similar issues.
thanks

您是否试图更新屏幕上没有被主动显示的文本？或者您想更新正在显示的屏幕上的文本吗？如果它是第一个我还没有想到的，如果它是第二个，那么每个小部件（标签，按钮等）都有它自己的GETTEX/SETTY函数内置，你只需要把它存储到一个拉链类型。在上面的示例中，当我声明LaSnk时，我声明了一个指向LaSnk类型的指针。只需从一个标签中取出文本，并在按下按钮时将其复制到另一个标签。我现在发布的问题是在按钮被按下时在另一个屏幕上更新文本，这些函数不起作用，我相信它是因为函数调用小部件重画而不是在屏幕上，这样就在某个地方产生了错误，但是甚至只是想复制一个拷贝。下面是不工作的：LaSTRIGIN副本（和LabelWigGET7- & GT；文本和NeXStand）；甚至更新屏幕，然后更新文本也不起作用。



      以下为原文

   


 
are you trying to update text on a screen that isnt being actively shown?  or did you want to update text on a screen being shown?  If its the first one I havent figured that out yet, if its the second then each widget (label, button, etc) has its own gettext/settext function built into it, you just have to store it into a laString type.  In my above example I declared a pointer to a laString type when I should just declared laString.  
    laString newString;
    laString_Initialize(newString);
    laLabelWidget_GetText(LabelWidget9, &newString);
   
   
  
    laLabelWidget_SetText(LabelWidget10, newString);
    
    laString_Destroy(&newString);
 
That should just take the text from one label and copy it to another label when a button is pressed.  Where i'm currently having issue is updating text on another screen when a button is pressed, these functions wont work, I believe its because the functions call for the widget to be redrawn and its not on the screen so that generates an error some where, but even trying to just do a copy like the following doesnt work:
 
laString_Copy(&LabelWidget7->text, &newString);
 
Even updating the screen and then updating the text doesnt work either.  

我想你的LILLASTIGIN初始化（NeXStand）；应该BalStaskIn初始化（和；NeXStand）；然后它对我起作用。



      以下为原文

    I think your line 
laString_Initialize(newString);
should be
laString_Initialize(&newString);
then it works for me.

在一个相似的主题中，你对拉斯特林格集（）函数有什么经验吗？这可以在小部件14到13×*********************NexStand；LaStRungIn初始化（ANP；NeXStand）；LalabelWistGueGETTeXT（LabelWistGe14，and NeXStand）；LalabelWistGoGETScript（LabelWigGET13，NeXStand）；LASTRIGNG销毁（ANP；NeXStand）；这不起作用。小部件14到hello ***********************NexStudio；LaSTRIGIN初始化（ANP；NeXStand）；LalabelWistGoGeGETTEXT（LabelWistGe14，and；NeXStand）；LalabelWistGoTyStTeXT（LabelWigGET13，NeXStand）；LaSTRIGHEGETSET（ANP；NeXStand，（const gfXuxChar *）”Hello）；LalabelWistGoGETScript（LabelWistGET1）4，新字符串）；拉斯特林破坏（和；新字符串）；有什么想法？



      以下为原文

    On a similar theme, have you had any experience with laString_Set() function ?
 
This works copying label on widget 14 to 13
***********************************
laString newString;
laString_Initialize(&newString);
laLabelWidget_GetText(LabelWidget14, &newString);
laLabelWidget_SetText(LabelWidget13, newString);
laString_Destroy(&newString);
 
This doesn't work - updating widget 14 to hello
***********************************
laString newString;
laString_Initialize(&newString);
laLabelWidget_GetText(LabelWidget14, &newString);
laLabelWidget_SetText(LabelWidget13, newString);
laString_Set(&newString, (const GFXU_CHAR*)"Hello");
laLabelWidget_SetText(LabelWidget14, newString);
laString_Destroy(&newString);
 
any thoughts ?

这可能是因为你没有为字符串设置字体，这对我来说是有效的。你需要知道你的字体是如何存储的，你可以在GFXyStasksAsvest.c中看到。



      以下为原文

   
It might be because you haven't set the font for the string, this worked for me.
 
    newString = laString_CreateFromCharBuffer("Hello", &Arial);
    laLabelWidget_SetText(LabelWidget2, newString);
 
 
You'll need to know how your fonts are stored, which you can see under gfx_assets.c

当你知道如何的时候，谢谢你。



      以下为原文

    Thanks
simple when you know how.

我注意到了LaSouthNexStudio；NexStask= ListRungReCudioFracBuffd（“AbdFdGujKnMnopqrStuvvxYxz”，和ArialNarrow）；LalabelWistGoTyStTrEnt（LabelWistGe13，NeXStand）；LaSTRIGGION Debug（＆NeXStand）；只显示已经在图形作曲家中使用的字母表字母。通过输入一个哑字符串作为一个字体资产在GC“abcDfgHukLnopoprrStuvvxyz”你看到这个了吗？你是怎么解决这个问题的？



      以下为原文

    I have noticed

laString newString;
newString = laString_CreateFromCharBuffer("abcdefghujklmnopqrstuvwxyz", &ArialNarrow);
laLabelWidget_SetText(LabelWidget13, newString);
laString_Destroy(&newString);
 
Only displays letters of the alphabet already used in graphics composer.
I can get around this by entering a dummy string as a font asset in GC of "abcdefghujklmnopqrstuvwxyz"
Have you seen this ? How did you get around this ?
 

我还没有这个问题，但我怀疑你可以修复它通过字体资源页和编辑字体下，它有一个字形选项卡，让你指定要添加的范围。如果你进入你的GFXyStasy.h文件并查找你的字体，它将显示当前导入的范围。我怀疑，但还没有验证，如果你到字形标签，并从范围480至90，它会导入所有的字符在该范围内。



      以下为原文

   


I haven't had that issue yet, but I would suspect you can fix it by going to the font resources page and under edit font it has a glyphs tab that lets you specify the range to add.  if you go to your gfx_assets.h file and look up your font it will display what ranges are currently imported.  I suspect but haven't verified that if you go to the glyph tab and import from range 48-90 that it will import all the characters in that range.  

为了解决我的问题，我不能把文本更新到一个当前不活跃的标签，我也不知道为什么。我创建了一个函数来更新标签，当它们变得活跃，但我有一个小的困难，使它足够通用的所有标签。为了工作，我必须直接引用每个标签，如果我试图创建一个指针，它每次都会崩溃，我宁愿这样，所以我可以对所有标签都有一个函数，但是它似乎不起作用。我试着创建一个双指针，指向原来的标签，但这也不起作用。我觉得我的做法是错误的，因为即使它工作了，它也必须先用旧文本绘制屏幕，然后重新绘制新的文本，这是我不希望看到的。是否有更好的方法将文本更新到当前没有显示的小部件？



      以下为原文

    Bumping this for help with my problem, I cant update text to a label that's not currently active and I don't know why.  I created a function to update labels when they become active however I'm having a small difficulty making it generic enough for all labels.  currently in order to work I have to reference each label directly, if i were to try to create a pointer to it, it crashes every time, I'd prefer that way so I can have one function for all labels, but it just doesn't seem to work.  I've tried creating a double pointer that points to the original label but that fails to work as well.  I feel like I'm going about it the wrong way because even when it does work it has to draw the screen first with the old text, then redraw with the new text which I feel is undesirable.  Is there a better way to update the text to a widget thats not currently being displayed?
 

所以我找到了一个解决方案，结果我所遇到的问题是由于标签的引用改变了，不知道为什么，但是我需要使用双指针来让这个工作。它仍然不是最佳的，因为旧文本在新文本被写入之前显示出来。如果Microchip能够记录一个更好的方法，那就好了。



      以下为原文

    So I was able to find a solution, turns out the problem I was having is due to the fact that the references to the labels change, Not sure why but I needed to use double pointers to get this to work.  Its still not optimal as the old text gets displayed before the new text is written it would be nice if Microchip could document  a way to do this better.  

再来一次，对不起所有人，但我肯定会帮助别人的。Soooo基本上我所有这些问题的原因是因为图形堆栈没有为你创建的所有小部件保持一个持久值，它们被破坏和重新创建，并且图形堆栈不断调用init .c来重新绘制你可能拥有的所有屏幕，这意味着对标签的所有引用。文本字段，或者每次重画屏幕时发生的任何改变。因此，简单的方法是简单地创建一个拉链变量并把它放在重新创建屏幕的函数中，然后你可以简单地改变变量，当屏幕被绘制时，然后你得到新的文本。我没有意识到init。C不断调用，并认为一旦每个小部件被创建，它们将被再次引用，并从任何更新的值重新绘制它们。



      以下为原文

    Bumping this one more time, sorry everyone but I'm sure it'll help someone down the road.  SOOOOO basically the reason I had all these problems is because the graphics stack doesnt keep a persistant value for all the widgets you create, they get destroyed and recreated and the graphic stack constantly calls the init.c to redraw any screen you may have, that means all references to labels, textfields, or whatever change everytime the screen is redrawn.  So the easy way to do it is to simply create a laString variable and put that in the function that recreates the screen, then you can simply change the variable and when the screen goes to be drawn then viola you get the new text.  I didnt realize the init.c gets called continuously and thought that once each widget gets created and they would just be referenced again and redrawn from whatever updated value they were.  

我需要能够改变文本到文本已经进入屏幕上或通过输入从一个USB棒。我看到我通过图形作曲家资产管理器输入的文本在一个字符串表中，并为该文本固定长度。这是不能用的。新的文本将存储在诺瓦姆。我需要做什么才能改变文本，并使用存储在NOVRAM下一次系统上机的文本？



      以下为原文

    I'm needing to be able to change text to text that has been entered either on the screen or through input from a USB stick.  I see that the text I've entered through Graphic Composer Asset Manager is in a string table and a fixed length for that text.  So this can't be used. The new text will be stored in NOVRAM.
What do I need to be doing to be able to change text and use the text stored in NOVRAM the next time the system is powered up?

您好，有几个元素您正在尝试做。1）外部资产，像那些来自USB MSD的将被展示在和谐V2.04。这还包括使用SQI闪存的接口。在你的情况下，似乎你只是想从外部媒体输入这些数据，但也有可能把它放在那里，以便更长久地使用。请参阅新的演示ARIAXEXPLALALY资源（可用时）2）处理字符串，它们可以是可变大小和内容，尽管您必须设置字体过滤器来处理这个问题。为了显示，来自特定字体的所有字形必须是可用的。这不是默认的，以节省系统空间。您可以看到ARIAL计数器演示的快速变化字符串可变长度的例子。还有一些像阿里亚-韦瑟尔预言，不仅显示可变字符串，而且显示可变字体（和语言）本地化。3）第三元素将输入一个字符串（键盘大概，或外部媒体输入），并将其存储在Flash中。这是可能的，但是你必须自己去做。在内部闪存中存储此内容是可能的，但它在图形上下文之外。



      以下为原文

    Hello,
 
There are a few elements of what you are trying to do.
 
1) External assets, like those from a USB MSD will be demonstrated in Harmony v2.04.  This also includes interface for using an SQI Flash memory.  In your case it seems you want to just enter this data from the external media, but it is also possible to place it there for more permanent use.  See the new demo aria_external_resources (when available)
2) To deal with strings, they can be of variable size and content, although you will have to set up the font filter to deal with this.  In order to display, all of the glyphs from a specific font must be available.  This is not default in order to save system space.  You can see the aria_counter demo for an example of rapidly changing strings of variable length.  There are others like aria_weather_forecast that show not only variable strings, but also localization with variable font (and language).
3) The third element will be to enter a string (keypad presumably, or external media input) and store it in flash.  This is possible, but you will have to do it on your own.  Storing this content in internal Flash memory is possible, but it outside of the graphics context.

我查看了LaString结构，以及定义的字符串是如何在GFXyReals.c.中的String Table数据中看到的。如果我将表索引设置为每一个字符串的1，那么将使用数据中指向的字符串。这似乎是实现更改文本的可能方式。我的问题是为什么GFXHUCHAR定义为UIT32？我看到，在图形作曲器中添加文本时，我唯一的选择是ASCII、UTF-8或UTF-16。那么，为什么我需要UIT32 32来定义一个字符，而不是R是0x052，我必须把它设置为0x000。这对每个字符都需要更多的RAM和NoLRAM。哪些国际字符需要32位字符？



      以下为原文

    I looked at the laString structure and how the defined strings were in the stringTable_data in gfx_assets.c. I see if I set the table index to -1 for each string then the string pointed to in data will be used instead.  That seems to be the possible way to implement changing text.  
 
The question I have is why is the GFXU_CHAR defined as uint32_t?  I see that the only choices I have when adding text in the Graphic Composer is ASCII, UTF-8 or UTF-16.  So why do I need uint32_t to define a character, i.e. instead of R being 0x0052, I have to set it as 0x00000052.  This requires more RAM and NOVRAM for each character.
 
What international characters require 32 bit characters?

你是对的。如果字符串具有有效的字符串表索引，则它将尝试引用数据表。如果将该引用设置为-1，则使用本地数据代替。有两个API允许您定义字符串本地数据。其中一个是UTIN 32×T（GFXIXCHAR）类型字符，另一个是UIT88T（CHAR）。请记住，当你制作自己的字符串时，还必须将字体资产附加到它上，并确保所需字体包含要在字符串中使用的字形。默认情况下，作曲家只生成您实际使用的字形。您可以在字体配置窗口下定义图形作曲器中的自定义字符范围。然后作曲家也将包括这些字形，它比其他任何东西更能证明未来。如果它消耗太多，那么您应该能够修改头中的GFXUCHAR CHAR定义值以满足您的需要。它不是生成代码，所以你不应该对它产生差异。



      以下为原文

    You are correct.  If a string has a valid string table index then it will attempt to reference the table for data.  If that reference is set to -1 then the local data is used instead.  There are two APIs which allow you to define string local data.  One takes in uint32_t (GFXU_CHAR) type characters, and the other uses uint8_t (char).  Keep in mind that when you craft your own string you also have to attach a font asset to it and ensure that the desired font contains the glyphs you're going to use in your string.
 
By default Composer will only generate the glyphs you're actually using.  You can define custom character ranges in Graphics Composer under the font configuration window.  Then Composer will include those glyphs as well.
 

 
It's more future proofing than anything else.  If it's consuming too much then you should be able to just modify the  GFXU_CHAR #define value in the header to suit your needs.  It's not generated code so you shouldn't get diff nags for it.

背景：MPLAB X IDE 4.01、XC32 V1.44、和声V2.04、PIC32 MZ2064 DAG176、NEWHAVEN 4.3“显示四线电阻触摸屏（ST722T2内部控制器）、内部DDR。我不喜欢再次碰撞，但我认为我误解了关于显示标签文本的一些事情。我有两个整数：一个是数字[09999 ]，另一个是[0，3]。第一个数是实际数（在我们的情况下是设定点），后者是小数点。所以，如果你有5000和2，TFT显示器应该显示50。我使用的逻辑如下：问题是，如果我有一个零的初始值，那么我可以改变我想要的小数点，它总是显示“0”。不是“0”，如果我有小数点1，或“0”为2，等等。这里是奇怪的部分：如果我把小数点设置为1，例如，值仍然在0，那么我可以将它设置为任何数目从[0，9]，它也不会改变。如果将值设置为10，它将正确显示“1”。现在，如果我把数字设置为5，它将正确地显示“0.5”。奇怪的是，如果小数点是2，它将需要一个大于100的数字来解开它，1000的小数点为3。一旦它“unclit'”，一切都显示完美，前提是我不改变小数点。这使我相信我的FrutATHOLL号函数工作正常，但是无论是LaSTRIGIN CREATEOVER CHARBASH还是LalabelWistGETScript都引起了问题。有什么想法吗？编辑1：我希望避免通过堆栈挖掘，但问题在于如何比较拉弦。在LabRiaWiGigLay.Label.C中有LalabelWistGoGETStEnt函数。这个函数调用LaString比较，如果字符串与以前相同，它就不会更新。这个比较函数最终归结为LabRiaSyStudio.c中的LaaStrucMP。这个函数，你可以想象，像STRCMP一样工作。这在正常操作中是好的，但是如果你在我的情况下“0”不同于“0”，那该怎么办？我明白，这避免了在没有必要时重绘的性能损失，但它不考虑像我这样的拐角情况，也不知道如何容易地绕过这一点，而不是修改堆栈。应负责确定两个字符串何时“相等”。在我的情况下，我会说如果长度不同，那么它们就不相等。因此，在LAYSTRCMP中检查字符串长度是一个很好的选择，如果取出它将不起作用。不过，我可以验证删除SETTATE中的LaSTRIGIN比较和后续返回值可以解决我的问题。



      以下为原文

    Background: MPLAB X IDE 4.01, XC32 v1.44, Harmony v2.04, PIC32MZ2064DAG176, Newhaven 4.3" display with 4-wire resistive touch panel (ST7282T2 internal controller), internal DDR.
 
I hate to bump this again, but I think I am misunderstanding something regarding displaying label text. I have two integers: one is a number [0,9999] and another [0,3]. The first number is the actual number (setpoint in our case) and the latter is the decimal point. So, if you have 5000 and 2, the TFT display should display 50.00. The logic that I use is the following:
 
 static void format_number(char *num, uint8_t dp, double val)
{
    const char *formatters[] = {"%1.0f","%2.1f","%3.2f","%4.3f"};
    const uint16_t divisor[] = {1,10,100,1000};
    
    if (dp > 3)
        return;
    val /= divisor[dp];
    sprintf(num, formatters[dp], val);
}

    uint16_t dp;
    uint16_t sp;
    char buff[20];
    laString val;

    //Setpoint
    format_number(buff, dp, sp);
    val = laString_CreateFromCharBuffer(buff, &DINBd____MainValues);
    laLabelWidget_SetText(LabelSetpoint, val);
    laString_Destroy(&val);
 
The problem is that if I have an initial value of zero, then I can change the decimal point all I want and it will always display "0". Not "0.0" if I have a decimal point of 1, or "0.00" for 2, etc. Here is the strange part: if I set the decimal point to 1, for example, and the value is still at 0 then I can set it to any number from [0,9] and it won't change either. If I set the value to 10 it will correctly display "1.0". Now if I set the number to 5, it will correctly display "0.5".
 
Oddly enough, if the decimal point is 2, it will take a number larger than 100 to unstick it and 1000 for a decimal point of 3. As soon as it's "unstuck", everything displays perfectly provided that I don't change the decimal point.
 
This leads me to believe that my format_number function works fine, but either laString_CreateFromCharBuffer or laLabelWidget_SetText is causing problems.
 
Any thoughts?
 
Edit 1: I was hoping to avoid digging through the stack, but the problem is with how laString is compared. In libaria_widget_label.c there is the laLabelWidget_SetText function. This function calls laString_Compare and, if the string is the same as before, it won't update. This comparison function ultimately boils down to la_strcmp in libaria_string.c. This function, as you can imagine, works like strcmp.
 
This is fine in normal operation, but what if you're in my situation where "0" is different than "0.00"? I understand that this avoids the performance penalty from a redraw when none is needed, but it doesn't account for corner cases like mine, nor can I see a way to get around this easily, short of modifying the stack.
 
I would propose that this string compare business be taken out and that the application should be responsible for determining when two strings are "equal". In my case, I would say if the lengths are different then they're not equal. Therefore, checking string lengths in la_strcmp is a good alternative if taking it out won't work. I can verify, though, that removing the laString_Compare and subsequent return value in SetText solves my problem.

如果LaaStrucMP返回“0”和“0”相等，那么这听起来像是一个bug，而最初的长度检查可能是缺少的。我会打开一个bug报告并查看它。谢谢。



      以下为原文

    If la_strcmp returns equal for "0" and "0.00" then it sounds like that's a bug and the initial length check is probably what is missing.  I'll open a bug report on this and look into it.
 
Thanks