Label truncation - Bug?

I am using a label and my label text can have "-" in it (e.g. "TX-dallas_bigbig_whater" or "big-34333_hose_345" ) and so when the label truncates long names it will truncate the above two examples like this:
"TX-dallas_bigbig_whater"  gets truncated to "TX-..."   but should be   "TX-dallas_bigb..."
"big-34333_hose_345"         gets truncated to "big-..."   but should be   "big-34333_hos..."
Is this a bug or ?

I'd update your Flex 4 SDK to one of the newer nightly builds: http://opensource.adobe.com/wiki/display/flexsdk/Download+Flex+4
If I used 4.0.0.10485 (Beta 2 build) my s:Label text truncated to "TX-...".
After switching to 4.0.0.14288 my s:Label text truncated to "TX-dallas_bigbi...".
<?xml version='1.0' encoding='UTF-8'?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
               xmlns:s="library://ns.adobe.com/flex/spark"
               xmlns:s="library://ns.adobe.com/flex/mx">
    <s:layout>
        <s:VerticalLayout />
    </s:layout>
    <s:controlBarContent>
        <s:Label id="sdkVer" initialize="sdkVer.text = mx_internal::VERSION;" />
    </s:controlBarContent>
    <s:Label text="TX-dallas_bigbig_whater" width="100" maxDisplayedLines="1" />
</s:Application>
Peter
Message was edited by: Peter deHaan (Adobe)

Similar Messages

  • [svn:fx-trunk] 12943: Dealt with my FIXMEs, except for one involving Label truncation which I reassigned to Carol to assess .

    Revision: 12943
    Revision: 12943
    Author:   [email protected]
    Date:     2009-12-14 20:57:18 -0800 (Mon, 14 Dec 2009)
    Log Message:
    Dealt with my FIXMEs, except for one involving Label truncation which I reassigned to Carol to assess.
    QE notes: None
    Doc notes: None
    Bugs: None
    Reviewer: None
    Tests run: checkintests
    Is noteworthy for integration: No
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/StyleProtoChain.as
        flex/sdk/trunk/frameworks/projects/spark/src/mx/core/FTETextField.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/Label.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/TextBase.as

  • Mouse-Over Labels sometimes truncated (bug fix requested)

    Hello,
    In both Xcelsius 2008 and all subsequent fixes, the Mouse-Over labels are sometimes truncated.  It happens when I have a text category that could be translated as a number.  For example, if I name a category "1E" ("1E" is a type of problem that our department is tracking) then when I hover the mouse over the pie chart it will just say "1" as the category name.  "1A", "1F", etc work which would lead me to believe that it perceives "1E" to be the same as the exponential 1*10^1, which is why it is showing "1".  It happens even if the categories are specified as text.  I think this is a bug that should be addressed in the upcoming SP2.

    Hi,
       What version of Xcelsius and LiveOffice do you have in place?
       Also, did you actually raise an SAP ticket and recieve an confirmation from Support Engineer (via ADAPT) that a developer will look into it last year? Please note, nothing will get fix unless it is logged under the proper channel.
       From what I can see, this is the only relevant ADAPT similar to yours (KBArticle 1403226 - See below). Although this doesn't mention anything about Mouse-Over Labels. Hope it helps.
    Symptom
    Character 'e' which behind the numbers (like 1e) will be lost after refreshing Live Office objects
    Reproducing the Issue
    Create a table in SQL server, add some columns with nchar(10) type
    In this table, add some records with value like '1e', '1389e'
    Create a Universe based on this table
    Create a Webi report based on this Universe
    Create a Live Office object based on this Webi report
    Create an Xcelsius dashboard, and use Spreadsheet Table to show this Live Office object
    Choose 'refresh on load' or add a refresh button to refresh this connection
    You wiil find the character 'e' which behind the numbers (like 1e) will be lost
    (For detail information about the reproduce steps, please refer to attached doc with some screenshots)
    Cause
    The issue has been identified and logged under Problem Report ID ADAPT01296829 (Xcelsius side) and ADAPT01290988 (Live Office side)
    Resolution
    Apply fix packages at both Xcelsius and Live Office sides to fix this issue:
    Live Office FP2.3 or SP3
    XCelsius X5 LAFix2.0.3 or Xcelsius SP3
    Regards,
    Ken

  • Tab labels truncating....why?

    Hi,
    I have many swf files that were built with SP1 Fix Pack 1 using the tab set component. I recently upgraded to SP1 Fix Pack 3. Now, when I make changes to the .xlf file and export the swf, several of the tab labels are now truncating. No changes were made to the tab sets. Has anyone else had issues like this, or know why this is happening.
    Thanks.

    Why do I have to install an extension to get back to the style I want to use? This is ridiculous.

  • Preferences Label Colors bug?  (Mac CS5.5)

    The fields in this pref are editable.  I can change the words, "Blue, Cyan, Green" etc. in the Pref Pane.  But, I'm still stuck with the default names when I right-click a clip in the timeline and choose "Label."
    The only place where I see those field name changes reflected is in the Preferences > Label Defaults Pane.
    This is a bug, right?
    What if I wanted to change those color names to be Good, Bad, MOS, GFX, etc.?  That would be much more useful than the default color names, because I like to color code my clips in the Timeline.  It makes effects editing (and clip classification) much simpler.
    Or, am I doing something wrong?

    I don't even see how it's useful to color code items in the Project Tab.  They already have their unique icons.  What more do you need? 
    Actually, there is one very useful feature, IMO: the ability to select clips in a bin or in a sequence based on their label color. Right-click a clip, go to to Labels, and select Select Label Group; all footage items with that label will be selected. This can be really helpful for cleaning up a project, or mass replacing stuff in a sequence. One of my requests was that we have many more (12-20) labels that we can define ourselves, so that their is a finer degree of granularity with how you label footage items. Right now, labels are (automatically) based on the footage item type, or (manually) if you assign a label. Being able to create labels like you suggest, e.g. Good, Bad, MOS, etc., would be much more user-friendly in that regard.
    On that subject, I'd love to see the Project fields "hide-able" like they are in AE.  I never saw the use for Labels there (or in AE for that matter).  I need to make another Feature Request.
    They are. Click the flyout menu in the Project panel  (kind of like Avid's hamburger menu) and go to Metadata Display. You can check and uncheck the fields you want to see there. You can also rearrange columns/field names in the Project panel by dragging them around.

  • Constant label location bug?

    As I was answering the question posted in this thread, I stumbled upon this little "feature" (tested in LV 2011).
    The Options panel allows you to specify the location of diagram object labels:
    By default, it is set to the first value, which is "Top-Left":
    However, for constants created from a control, it looks like this:
    If you try to change that option, say to "Top-Middle", and create a constant, it will still give you the result shown above. For any other object (Loop, Function, etc) it seems that the location preference is used properly:
    Even if you create a constant from a control whose label is at the "Top-Middle", a constant created from it will look as above. No biggie, but that appears to be an undocumented feature.
    Note that if you create a very small For Loop and show its label (when the default location is "Top-Middle"):
    and resize the loop, the label will stick to the Top-Left corner:
    no matter whether or not you check the "Labels locked by default". Puzzling to me...
    I am sure there are other oddities. Won't prevent me from sleeping though.

    Hey there,
    That does seem odd. I will reproduce this on my machine and file a bug report.
    Thanks for pointing that out.
    Happy Thanksgiving!
    Jacob R. | Applications Engineer | National Instruments

  • Safari .svg text truncation bug

    I hope that this picture will make the problem clear. I'm using exactly the same .svg image in both cases - it's created by Archi.
    As you can see, the text in the boxes is truncated in the case of Safari - but not with Firefox.
    Any suggestions as to how to fix this?

    This appears to be fixed in the latest nightly build. You can check those out here.
    http://nightly.webkit.org/
    Find out more info regarding Safari's development on the blog.
    http://webkit.org/blog/

  • Problem with label on barseries ?

    Hi,
       I have faced a problem with label truncation for the clustered and stacked bar chart.
    if the size of the bar is too small and labelposition is inside label truncates , similarly when bar is too long and occupy the graph width the label outside truncates.
    Is there any way to resolve this problem.
    Thanks in advance

    for b)
    JButton nextButton = new JButton(String.valueOf(i));
         nextButton.setForeground(Color.red);//
         nextButton.addActionListener(this);
         days.add(nextButton);
    OR
    Font titlefont = new Font("SansSerif",Font.BOLD,20); //Globle
    JPanel middle = new JPanel();
    monthlabel = new JLabel();
    monthlabel.setFont(titlefont);
    middle.add(monthlabel);
    I'm new it java but i think this should help

  • Notes getting truncated while importing excel to MS project

    Hi All
    I am importing an excel sheet to MS project 2010 through import map. There are some notes related to tasks that are longer than 255 words in length. When the project map is completed, all the fields are fine other than the notes field. The data in notes
    field gets truncated to 126 characters. Can someone help me out on this.
    Udyan

    To those who may be interested in this thread.
    The jury is still out on whether this truncation bug is also present in Project 2013/Excel 2013. Meanwhile I've developed a macro that will export a formatted Excel Workbook into Project. The macro is structured to run from Excel. The main purpose of the
    macro is to export the full notes text data, (i.e. no truncation even at 255 characters), from a specified column on the Excel Worksheet into the Notes field of Project. Other basic Project data including Task Name, Outline level, Duration, Start,  &
    Resource Names are also exported. An example of the formatted Excel Worksheet is shown below.
    If you are interested in this macro, let me know.
    John
    Example of formatted data for export. Note that multiple resource assignments per task are handled (not easily done with an import map alone). The macro detects the units used in the worksheet duration column (i.e. number only,  or number with "h",
    "d", or "w") such that the proper data is exported to Project (i.e. minutes). For reference the note text shown for Task b is the text string that is truncated at 126 characters when using a simple import map. That bug is resolved by the macro. The notes text
    for Task c is is 406 characters and all of them are exported by the macro (i.e. no truncation at 255 characters). The notes text for Task d has a line feed in the text string and that is exported by the macro.

  • Statistics Express Kurtosis inconistency Labview 2011 (Bug 215683)

    Hi All,
    I am currently working with a data collection program from which I need to output the skew and kurtosis values for an array of 30 data points. As I was already using the Statistics Express VI to calculate mean, s.d. etc. I just added the skew and kurtosis outputs to that VI. I then set up a basic VI to generate a 1D array of random numbers to let me compare the Express VI to the skew and kurtosis VI on the mathematics > probability and stats. palette.
    The skew and kurtosis values are inconsistent between the two VIs. If I calculate the skew and kurtosis by hand I can see that the non-express VI appears to be giving the correct answer. I did some digging and found that this has been labelled as bug no. 215683 and is described as having been fixed as part of Labview 2011. I am running Labview 2011 with SP1 so I'm not quite sure why the two VIs are still inconsistent. 
    I realise that I can simply use the VI which is giving the correct answer but I am curious as to why a bug which should be fixed still appears to be active in my version of Labview.
    Any thoughts/ input would be greatly appreciated.
    Many thanks in advance

    Hi cat,
    why don't you get rid of that buggy (as it seems) ExpressVI?
    The remaining data (StDev, variance) are provided by just another function from math->statistics palette…
    You can also opne the ExpressVI to see, how it calculates those data and why it does produce different results!
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Chart label length limitation?

    Is there a limitation on the length of x- or y-axis label for a SVG chart? The chart on my page has x-axis
    label truncated to 15 characters long.

    Me too, in my SVG pie chart, the last row legend text was truncated. just like:
    deal size > 70k - 92.5%
    deal size
    I actually expected in the second row, deal size <= 70k ...
    What happened? and how can I control this, moreover the legend was displayed in the left upper of the region and cost a lot width in my screen. Can I change to display the legend in other place, eg. the bottom of the region or the chart?
    Anyone can help us about this?

  • Label misplaceme​nt after conversion or copying

    Besides disappearing "cloned" property nodes, which seems solved in Labview 2012 (SP1), I also have a problem with misplacement of labels after conversions or copying.
    The problem occurs at least in the following situation:
    1. There is a property node of a control.
    2. The control is defined in a "Type Def".
    3. A label is attached Right-Centered of the property node.
    4. The location of the Label in the "Type Def" is different (Top-Left, for instance).
    5. To create the bug either the source is converted (e.g. Labview 2011 to Labview 2012) or the property node is copied between sources.
    6. The label of the converted/copied property node now has moved upwards, above the property node.
    In Labview 2012 the solution for disappearing "cloned" property nodes also fixes the label misplacement bug for those property nodes.
    The misplacement of labels can be quite annoying when you have relatively compact code in many multiple stacked sequences and event handlers.
    I also had a seperate, global problem with label placement after the label font is changed / converted, but have not yet verified if this still happens in Labview 2012.
    Solved!
    Go to Solution.

    billko wrote:
    Ettepet wrote:
    I started this topic to get this bug (these bugs) acknowledged and (hopefuly) fixed in the (near) future, but sofar nothing.  I emailed someone who entered the two bugreports I mentioned:
    CAR #318066 -- Implicitly typed property node Value does not retain the typedefness of the original control
    CAR #318065 -- "Find" popup problems on implicitly linked property/invoke nodes when original control is a typedef
    ...but have heard nothing back after an initial reply asking me for the CARs (and my reply to that) several days ago.
    It amazes me that none here seem to have problems with labels being misplaced by Labview, as it has been doing so for several years (at least) and it effectively wrecks the layout of your code.
    ...Or maybe we just gave up... 
    Well, I got hope after seeing many instances [where the bug used to occur] fixed in LV2012 because of the CARs I mentioned in my previous post.  The bug mentioned in the OP should be readily fixable for ALL instances in a very similar manner.
    I would be very happy if a CAR was created for this.

  • Polar plot scale numbers "truncated"

    I have a strange problem when using the polar plot VI.
    Labview 2012 latest SP, running on a cRIO9074. I'm running a servo motor for one revolution while measuring the runout on an armature using a linear position sensor.
    The data looks good, but for some reason, the scale labels truncate after two decimals, no matter what I set the precision to. I'm sending it a cluster of two double precision arrays.
    When I run the Labview example, it works fine I can change the number of decimals viewed to 10 if I need to. I've tried keeping everything the same as the example.
    Any ideas?
    See picture.
    The sample VI works fine, (I can set the precision to 6 and I will see 6 decimal positions. )

    Thanks for the response, Kurt. With the help of a colleague, we were able to determine that this behavior is only when the VI is running on the cRIO.
    (I think it was called "Polar Plot Demo.vi", but yes the VI is "Polar Plot with Points Option.vi"
    We verified this by running the example vi first from windows (works fine), then ran it on the cRIO. On the cRIO it truncates decimals depending upon what font size you use. If you use a REAL TINY font, it will include more decimals. When running in Windows, the graph appears to move left to accomodate for more decimal place. When running on the cRIO, it appears to cut the picture off on the right side.
    Following is our setup, but as stated above, we sent the demo program to the cRIO (didn't use any I/O) and the problem occured.
    We're using Labview 2012, latest updates applied.
    Modules are:
    NI-9411 to read an Ono Sokki position sensor (quadature output from two channels, resolution is .0001 mm.
    Ethercat set up using the "getting started" manual for the NI supplied AKD servo drive and motor.
    All hardware works fine and data collected looks good. Test is to turn motor and collect servo position and linear encoder position.
    Data has 4 decimal places coming in.

  • Label misplacement after font change

    Below label misplacement bug was mentioned earlier (here).
    Bug description:
    There is a label misplacement bug when you change font (type / size) or change your default font, which can also happen during conversion to a different LV version on a different pc (with different environment settings). This bug misplaces the labels horizontally, especially when the label is positioned halfway horizontally or even halfway vertically on any side of a property node or control / icon.
    It could be reasoned that proper placement of text after its font is changed can be very hard to get right in any programming environment.  At least one of the combinations: label stuck to the right side of an item (property node, etc.), placed half-way vertically should be easy to position properly though.  (horizontally at least)  Since this is where I (intuitively) put many of my labels for property nodes I would like to have this fixed.  This bug has been present in LV for at least several years.
    Solved!
    Go to Solution.

    Hello Ettepet,
    Sorry for the delay.
    I didn't fully follow the procedure of steps you were explaining before and therefor I couldn't reproduce it.
    I see similar behavior (but to a lesser extinct than 2 full chars) when I play around with the font size of the default font.
    During the next week I'll search through the existing CARs and file a new one if it doesn't exist yes.
    If it does exist, then I'll provide you with the CAR number and add you as a person experiencing similar issues.
    PS: Sorry for the delay, I was teaching 2 courses during this week.
    Next week i'll be back on normal support shift.
    Kind Regards,
    Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
    CLD, CTA
    If someone helped you, let them know. Mark as solved and/or give a kudo.

  • Slow performance Designer 10g (on 10gR2 database)

    We are busy testing Designer 10g version 10.1.2.5 (windows XP) on 10gR2 64 bit database (Sun solaris) . The repository was migrated from Designer 6.0.
    But the performance/response is rather slow. Example: At first, opening a server model diagram took 2 minutes or more. By searching the forum we found the tip for the "alter system set OPTIMIZER_SECURE_VIEW_MERGING = false;". That made a big difference.
    But now we still have response problems: Expanding the treeview for the list of tables, views or snapshots takes much longer then in Designer 6.0.
    Also opening for example Design Editor takes longer then one normally expects, allthough some delay can be expected because we have a lot of applications (100) in the repository.
    Is it because it is now written in Java, or are more database optimizations possible?
    Paul.

    Have you computed statistics using the Repository Administration Utility (RAU)? The default percentage of 20% is usually good enough, but you could go higher.
    Do a View Objects in RAU and check for missing, disabled or invalid objects. If you find any, there are ways to correct the situation, mostly under the Recreate button.
    Make sure that no-one else is using the repository, then press the Recreate button in RAU and use the selection labeled: Truncate Temporary Tables. Sometimes these tables get too full and can impact performance.
    Under the Options menu in RAU, there is an item labeled: Enable Performance Enhancements. To be honest with you, I've never noticed this item before, and I don't know for sure what it does. Then again, I've never had any serious performance problems in Designer. It might be worth your while to back up your repository, then turn this on.

Maybe you are looking for