Legend width

Hello,
I want to set the width of a legend using script. I can set its position, but cannot influence its size, which appears to be adjusted automatically. Usually, it is too small to be legible. How can I do this? So far I have being using (unsuccessfully) these varaiables:-
D2LegPosX
D2LegPosY
D2LegTxtSizeAut
D2LegSizeGlX
D2LegTxtType
D2CCurveLegTxt
D2LegDraw = true
Can anyone guide me please? Obviously, I am missing something....
Thanks in advance

Sounds like you legend size is still set to "Automatic legend size". Please change this parameter to "Fixed legend size" in the dialog and you should be able to adjust the legend width using variables in a Script.
Otmar D. Foehner
Business Development Manager
DIAdem and Test Data Management
National Instruments
Austin, TX - USA
"For an optimist the glass is half full, for a pessimist it's half empty, and for an engineer is twice bigger than necessary."

Similar Messages

Chart Legend width

I have a problem with a chart legend.
Is it possible to enlarge the width of a chart legend ?
If yes where I can do it.
Thank you very much

I know it is over a year since you posted the reply. But, I just wanted to know if the new version (2.2) has anything to change the size of legend width. The width is much too small. I am using a 3-D pie chart if that helps.

Chart legend width in Firefox

This may already be common knowledge, but we just bumped into what may be the cause of truncated chart legends in Firefox.
I have been trying to figure out how to expand the width of the legend box that accompanies charts. Firefox sometimes renders the legend box too short to display the full value character strings. But sometimes Firefox renders the legend box with a wider width, so the value strings have plenty of room to fully be displayed.
IE, on the other hand, reduces the font of the text in the legend box and so can display the full values.
And then a co-worker noticed a pattern in the way Firefox renders the legend box.
If the "data point limit" set for a pie chart, for instance, is at least as great as the greatest number of values that can be displayed, Firefox renders the legend box with enough room for the full value character strings. It does not truncate the legend box.
For example, if the largest number of values that can be displayed in a pie chart is 10, if the "data point limit" for the chart is set to 11 or more, Firefox will render a legend box with sufficient width to display the full value strings.
On the other hand, if the "data point limit" is set to 10 or less when there can be 10 or more values for the column driving the pie chart, then Firefox will render a legend box that may not be wide enough to display the full value strings. The strings will thus be truncated to the render width of the legend box.
So far this behavior appears consistent. I

Actually, it is necessary only to set the "data point limit" equal to, not greater than, the maximum number of column values for a chart. So if the maximum number of column values is 10, if the "datda point limit" is set to 10, the legend box will be wide enough to display the full value strings. It can be set to a number greater than 10 as well, but that is not necessary for the legend box to be wide enough.

Crystal Chart Legend Width

Is there a way to set the width of a chart legend? I want to make it wider so the text doesn't wrap but when I grab the handles and stretch the box, it snaps back to the original width. I have XI R2.
Thanks,
Rob

Please re-post if this is still an issue or purchase a case and have a dedicated support engineer work with you directly:
http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryID=11522300?resid=-Z5tUwoHAiwAAA8@NLgAAAAS&rests=1254701640551

Graph legend width change - Left aligned or right aligned

Hello all,
when I place an XY-Graph with Plot-Legend shown in LV2012, the text of the plot name is left aligned, wich is, what I want. With this behaviour the little pictures, representing the plot attributes, are fixed. After migrating to LV2014 I realized, that the text is now right aligned, which means, that the little pictures are moving to left & right, depending on the plot name length.
I found no property controlling this behaviour.
As a workaround I could set the plot legend position depending on its width, when the plot name is changed, but there is no event, firing when the plot name is changed by the user. So I would have to poll the plot names in the timeout case of my event structure. Btw. I have to show six XY- graphs on my FP, so polling can cause a remarkable CPU load (when I do it 1000 times / s ).
Any suggestions?
Greets, Dave

Hello Dominik,
thank you for your reply.
I'd like to show you the problem with some pictures:
The left picture shows the original situation, the right picture demonstrates the behaviour with LV2012, the legend is right aligned.
The same situation in LV2014, the legend is right aligned.
Greets, Dave

Chart legend too wide when using horizontal layout

I am using a flex chart with about 15 series on it. I've set
the legend direction variable to "horizontal". However since the
panel width which contains the chart is fixed, the legend sprawls
out to the right instead of going "wrapping around" nicely to stay
within the panel. As a result, you can't read the whole legend when
looking at the chart. The chart itself stays the proper width, but
the legend is too wide and can only be seen via using the scrollbar
to move horizontally. How can that be fixed?

Solerous, you must create a custom legend. Here's an example
that uses a grid to lay out the individual grid items. If you have
a variable number of series, then you can probably come up with
better logic for laying out the legend, but this should help get
you going.
hth,
matt horn
flex docs
<?xml version="1.0"?>

<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
backgroundColor="white" creationComplete="init()">
<mx:Script><![CDATA[
import mx.containers.GridItem;
import mx.containers.GridRow;
import mx.graphics.SolidColor;
import mx.graphics.IFill;
import mx.charts.LegendItem;
import mx.charts.Legend;
import mx.collections.ArrayCollection;
[Bindable]
public var expenses:ArrayCollection = new ArrayCollection([
{Expense:"Taxes", April:2000, May:321, June:131, July:1100,
August:200, September:1400, October:42},
{Expense:"Rent", April:1000, May:95, June:313, July:600,
August:400, September:200, October:52},
{Expense:"Taxes", April:2000, May:321, June:131, July:90,
August:500, September:900, October:300},
{Expense:"Bills", April:100, May:478, June:841, July:400,
August:600, September:1100, October:150}
private function init():void {
for (var i:int = 0; i < myChart.series.length; i++) {
var li:LegendItem = new LegendItem();
li.label = myChart.series
.displayName;
var sc:SolidColor = myChart.series.getStyle("fill");
li.setStyle("fill", sc);
var gi:GridItem = new GridItem();
if (i < 3) {
// First row
gi.addChild(li);
gr1.addChild(gi);
} else if (i >= 3 && i < 6) {
// Second row
gi.addChild(li);
gr2.addChild(gi);
} else if (i >= 6) {
// Third row
gi.addChild(li);
gr3.addChild(gi);
]]></mx:Script>
<mx:Panel title="Bar Chart with Legend" width="500"
height="600">
<mx:BarChart id="myChart" dataProvider="{expenses}"
height="400" showDataTips="true">
<mx:verticalAxis>
<mx:CategoryAxis
dataProvider="{expenses}"
categoryField="Expense"
/>
</mx:verticalAxis>
<mx:series>
<mx:BarSeries xField="April" displayName="April (in
$USD)"/>
<mx:BarSeries
xField="May"
displayName="May (in $USD)"
/>
<mx:BarSeries
xField="June"
displayName="June (in $USD)"
/>
<mx:BarSeries
xField="July"
displayName="July (in $USD)"
/>
<mx:BarSeries
xField="August"
displayName="August (in $USD)"
/>
<mx:BarSeries
xField="September"
displayName="September (in $USD)"
/>
<mx:BarSeries
xField="October"
displayName="October (in $USD)"
/>
</mx:series>
</mx:BarChart>
<mx:Grid id="myGrid">
<mx:GridRow id="gr1">
</mx:GridRow>
<mx:GridRow id="gr2">
</mx:GridRow>
<mx:GridRow id="gr3">
</mx:GridRow>
</mx:Grid>
</mx:Panel>
</mx:Application>

Pie Chart with Legend

Hey Experts,
I have a small issue but cannot seem to find the solution. I have a pie chart with legends which I want to show side by side (horizontally). First pie chart and then legends. My requirement is that when the window is resized, the pie chart should also resize. I am able to show the chart and legends horizontally but when the legends list is long, the pie chart is always aligned in the center vertically. I tried setting all properties such as verticalAlign = "top", verticalCenter = "false", tried putting pie chart and legends in a separate VBox but nothing seems to work. Below is the code snippet.
I believe others would have faced this problem. Can someone help?
<mx:HBox width="100%" height="100%" verticalAlign="top" verticalCenter="false">
 <mx:VBox width="100%" verticalAlign="top" verticalCenter="false">
 <mx:PieChart id="pieChart" width="100%" height="100%" showDataTips="true" minWidth="200" minHeight="200" verticalCenter="false"/>
 </mx:VBox>
 <mx:VBox width="100%" verticalAlign="top" verticalCenter="false">
 <mx:Legend width="100%" height="100%" dataProvider="{pieChart}"/>
 </mx:VBox>
</mx:HBox>

Hi Dajji,
Here is the code which resolves the problem...
Note: In the code below I have removed the percentage width and height for PieChart.....that resolves the problem.....but the thing here is as you resize
your browser window the piechart width and height will not change accordingly...? Do you need PieChart to change its dimensions as your browser window
resizes...???
However if you specify width="100%" and height="100%" for PieChart you never gonna acheive the PieChart to be vertically alined to top.....why because
as you specified width="100%" and height="100%" for PieChart it occupies the total dimensions of the VBox but the actual visible portion dimensions are
less... because within the VBox you also have the legends so Flex will assign the sizes proportionately....for PieChart and Legends..
Hope you got my point...So you should remove the width="100%" and height="100%" for PieChart then you can acheive what you needed...
<?xml version="1.0"?>

<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" height="100%" width="100%">
 <mx:Script>
 <![CDATA[
 import mx.collections.ArrayCollection;
 [Bindable]
 private var medalsAC:ArrayCollection = new ArrayCollection( [
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 },
 { Country: "USA", Gold: 35, Silver:39, Bronze: 29 },
 { Country: "China", Gold: 32, Silver:17, Bronze: 14 },
 { Country: "Russia", Gold: 27, Silver:27, Bronze: 38 } ]);
 private function displayGold(data:Object, field:String, index:Number, percentValue:Number):String {
 var temp:String= (" " + percentValue).substr(0,6);
 return data.Country + ": " + '\n' + "Total Gold: " + data.Gold + '\n' + temp + "%";
 ]]>
 </mx:Script>
 <mx:Panel title="Olympics 2004 Medals Tally Panel" height="100%" width="100%" layout="horizontal" verticalAlign="top">
 <mx:VBox verticalAlign="top" height="100%" width="100%">
 <mx:PieChart id="chart"
 showDataTips="true"
 dataProvider="{medalsAC}">
 <mx:series>
 <mx:PieSeries
 nameField="Country"
 field="Gold"
 labelFunction="displayGold">
 </mx:PieSeries>
 </mx:series>
 </mx:PieChart>
 </mx:VBox>
 <mx:Legend dataProvider="{chart}"/>
 </mx:Panel>
</mx:Application>
Thanks,
Bhasker Chari

Display x-channel in VIEW legend?

Hello,
Does anyone know how to display the x-axis channel name you are graphing against in the VIEW legend (the y-axis channel is displayed as the "Name").
Thanks!
Julia

Thanks Brad! This also works with DIAdem 2012.
I made a script which does the next adjustments in the VIEW.
- Align the Y-axises
- Remove the Yaxis name
- Selection of the legend items
- Legend width adjustment
- Legend items width adjustment
I used an User dialog box to control the labels in the legend, the Y axis distance to the left, the legend width & the legend items width.
Now I use a pull down selection list for the Y-axis distance & the legend width.
- Is it possible to read the highest digits form the Y-axis channels and adjust the Y-axis distance automatically?
- Is it possible to read the longest length from the channel names displayed in the VIEW and adjust the legend width automatically?
I prefer it to use the VIEW instead of the REPORT, because it is easy to zoom in the VIEW. I use long data sets (vehicle data from weeks) so it consumes a lot of time to look at this data in the REPORT.
Another question, how can I pre-select checkboxes in the User dialog box?
With kind regards,
Stijn
Attachments:
DIAdem VIEW adjusted.jpg ‏316 KB
User dialog box - DIAdem VIEW legend.jpg ‏30 KB

Axis titles don't display on cartesian chart

I use Adobe Flex Builder 3 to create charts for use in a
larger web application. Since moving from Flex Builder 2 to Flex
Builder 3, the axis titles are no longer being displayed.
In my mx:Application, I declare an mx:CartesianChart. I
dynamically add ColumnSeries to a ColumnSet based on the contents
of an XML file loaded using a URLRequest. I then add the ColumnSet
as the only element of the chart.series Array. The rest of the
chart (including the legend) displays correctly.
The axes are explicitly defined as part of the
mx:CartesianChart:
<mx:CartesianChart left="{legend.width}" top="30"
right="0" bottom="0" id="chart" dataProvider="{xmlDoc.elements()}"
showDataTips="true" dataTipFunction="formatDataTips">
<mx:verticalAxis>
<mx:LinearAxis id="vAx" autoAdjust="true" title="Dollars"
labelFunction="formatVerticalLabel"/>
</mx:verticalAxis>
<mx:horizontalAxis>
<mx:CategoryAxis id="hAx" categoryField="Year"
title="Year"/>
</mx:horizontalAxis>
<mx:horizontalAxisRenderers>
<mx:AxisRenderer axis="{hAx}" labelRotation="-60"/>
</mx:horizontalAxisRenderers>
</mx:CartesianChart>
Thanks in advance for your help.

I've isolated the issue, but I'm not sure if it's a bug or if
something I'm doing wrong. The following simplified version of my
chart application doesn't display the axis titles:
[code]
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
<mx:Legend dataProvider="{chart}" left="0" top="25"
id="legend"/>
<mx:CartesianChart left="{legend.width}" top="30"
right="0" bottom="0" id="chart">
<mx:verticalAxis>
<mx:LinearAxis title="Dollars"/>
</mx:verticalAxis>
<mx:horizontalAxis>
<mx:CategoryAxis title="Year"/>
</mx:horizontalAxis>
</mx:CartesianChart>
</mx:Application>
[/code]
The following version does:
[code]
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
<mx:Legend dataProvider="{chart}" left="0" top="25"
id="legend"/>
<mx:CartesianChart left="{0}" top="30" right="0"
bottom="0" id="chart">
<mx:verticalAxis>
<mx:LinearAxis title="Dollars"/>
</mx:verticalAxis>
<mx:horizontalAxis>
<mx:CategoryAxis title="Year"/>
</mx:horizontalAxis>
</mx:CartesianChart>
</mx:Application>
[/code]
The only difference is the left definition for
mx:CartesianChart. When it's defined in terms of the width of the
legend, the axis titles disappear. Is there another way that I
should be displaying my chart using the full span of the
application?
Thanks again for your help.

How to display formated html in a TextArea?

Hi,
I'm trying to display some html in a TextArea. But the formatting does not look good.
here is my mxml file
<?xml version="1.0" encoding="utf-8"?>
<mx:Panel xmlns:mx="http://www.adobe.com/2006/mxml"
 width="100%" height="100%">
 <mx:TextArea id="legend"
 width="100%" height="100%" editable="false" selectable="false" toolTip="map legend" wordWrap="true">
 <mx:htmlText>
 <![CDATA[
 <img src="images/projects.png" /> projects
 <img src="images/publications.png" /> pubpcations
 <img src="images/persons.png" /> persons
 <img src="images/news.png" /> news
 <img src="images/events.png" /> events
 <img src="images/documents.png" /> documents
 ]]>
 </mx:htmlText>
 </mx:TextArea>
</mx:Panel>
and here is the result...
Any idea what I am doing wrong?

I had problems like what you are describing. A picture is worth a thousand words, so take a lookee here: http://www.timos.com/timos/green/ct/CounterThink.cfm. When the app displays, press the link button "About CounterThink", then scroll down to the text block with Mike Adams' photo.
My problems were fixed when I eliminated all the spaces in the HTML code. My source code for that block now looks like this:
<img src="../../assets/images/green/mike.png" alt="Mike Adams" width="150" height="149" hspace="5" vspace="3" align="left" />The creator of the cartoons, Mike Adams is a consumer health advocate with a mission to teach personal and planetary health to the public He is a prolific writer and has published thousands of articles, interviews, reports and consumer guides, impacting the lives of millions of readers around the world who are experiencing phenomenal health benefits from reading his articles. Adams is an honest, independent journalist and accepts no money or commissions on the third-party products he writes about or the companies he promotes.In 2007, Adams launched EcoLEDs, a manufacturer of mercury-free, energy-efficient LED lighting products that save electricity and help prevent global warming. He's also a successful software entrepreneur, having founded a well known email marketing software company whose technology currently powers the NaturalNews email newsletters.Adams is currently the executive director of the Consumer Wellness Center, a 501(c)3 non-profit, and regularly pursues cycling, nature photography, Capoeira and Pilates. Known as the 'Health Ranger', Adams' personal health statistics and mission statements are located at <a href=http://www.healthranger.org target="_blank">www.HealthRanger.org</a>.
Notice there are no indents, no line breaks, not a single space except for those within the text. The code is a little harder to read this way, but that is what worked. Try it, I hope this works for you. Have fun,
Carlos

Dynamically adding ColumnSeries doesn't work

I created the following code to create different series dynamically:
<?xml version="1.0" encoding="utf-8"?>
 <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
 creationComplete="application1_creationCompleteHandler(event)"
 xmlns:s="library://ns.adobe.com/flex/spark"
 xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600">
 <fx:Script><![CDATA[
 import mx.charts.series.ColumnSeries;
 import mx.collections.ArrayCollection;
 import mx.collections.Sort;
 import mx.collections.SortField;
 import mx.events.FlexEvent;
 [Bindable]
 public var Loc01:ArrayCollection = new ArrayCollection([
 {date:"2002", close:41.87, loc: "Location 01"},
 {date:"2005", close:48.06, loc: "Location 01"},
 {date:"2006", close:48.06, loc: "Location 01"},
 {date:"2002", close:157.59, loc: "Location 02"},
 {date:"2003", close:160.3, loc: "Location 02"},
 {date:"2003", close:45.74, loc: "Location 01"},
 {date:"2004", close:42.77, loc: "Location 01"},
 {date:"2004", close:150.71, loc: "Location 02"},
 {date:"2002", close:45.74, loc: "Location 03"},
 {date:"2003", close:42.77, loc: "Location 03"},
 {date:"2004", close:150.71, loc: "Location 03"},
 {date:"2005", close:156.88, loc: "Location 02"}
 protected function application1_creationCompleteHandler(event:FlexEvent):void
 // TODO Auto-generated method stub
 var obj:Object;
 var arr:Array = [];
 var i:int;
 var ac1:ArrayCollection;
 var NS:ColumnSeries;
 var sortA:Sort = new Sort();
 var sortByLocation:SortField = new SortField("loc",false,false,false);
 var sortByDate:SortField = new SortField("date", true, false, false);
 sortA.fields=[sortByLocation, sortByDate];
 Loc01.sort=sortA;
 Loc01.refresh();
 i=0;
 arr[i] = Loc01[0].loc;
 for each(obj in Loc01){
 if(arr[i] != obj.loc)
 i++;
 arr[i] = obj.loc;
 var str: String;
 i=0;
 for each(str in arr){
 ac1 = new ArrayCollection();
 for each(obj in Loc01){
 if(str == obj.loc)
 ac1.addItem(obj);
 ac1.refresh();
 if(!myChart.series[i])
 myChart.series.push(new ColumnSeries());
 NS = myChart.series[i];
 NS.dataProvider = ac1;
 NS.yField = "close";
 NS.horizontalAxis = h1;
 NS.displayName = str;
 NS.verticalAxis = v1;
 NS.id = "cs" + i.toString();
 i++;
 ]]></fx:Script>
 <fx:Declarations>
 
 </fx:Declarations>
 <mx:Panel x="49" y="30" width="868" title="Column Chart With Multiple Axes">
 
 <mx:ColumnChart id="myChart" width="601" showDataTips="true" dataProvider="{Loc01}">
 <mx:horizontalAxis>
 <mx:CategoryAxis id="h1" categoryField="date"/>
 </mx:horizontalAxis>
 <mx:horizontalAxisRenderers>
 <mx:AxisRenderer placement="bottom" axis="{h1}"/>
 </mx:horizontalAxisRenderers>
 <mx:verticalAxisRenderers>
 <mx:AxisRenderer placement="left" axis="{v1}"/>
 </mx:verticalAxisRenderers>
 <mx:verticalAxis>
 <mx:LinearAxis id="v1" minimum="30" maximum="170"/>
 </mx:verticalAxis>
 <mx:series>
 <mx:ColumnSeries id="cs0"/>
 </mx:series>
 </mx:ColumnChart>
 </mx:Panel>
</s:Application>
The hard coded ColumnSeries (the first one) works fine, but the next series which are created dynamically don't work. What's wrong in my code? Any help would be much appreciated.

I replaced the following part of the code:
 if(!myChart.series[i])
 myChart.series.push(new ColumnSeries());
with the following lines:
 if(!myChart.series[i])
 var tmp:Array = myChart.series;
 tmp.push(new ColumnSeries());
 myChart.series = tmp;
 myChart.invalidateSeriesStyles();
And it works fine now.

How to break up string of css code properly?

Is there a way to take css code that looks like this mess
(which I got elsewhere) and break it into its legible/workable
parts without going through it and hitting enter after every
closing } ? There are about 1000 lines of this stuff like
this...this is just a small bit of it...is there any easy way in DW
to break it up properly?
Thanks in advance...
Laura
#car .roundbox .topleft{background:no-repeat top
left;width:auto;}#car .roundbox .topright{background:no-repeat top
right;padding:0;}#car .roundbox .infobody{margin:-10px 0
0;padding:0 10px;}#car .roundbox .botleft{background:no-repeat
bottom left;}#car .roundbox .botright{background:no-repeat bottom
right;}#content #popupBody #carTypes #totals
td.totalLine{border-bottom:1px solid #eee;}#car
#rate-content{display:block;}#car #rate-content
#tally{width:706px;float:left;margin-top:8px;}#car #rate-content
#tally td.fee{padding:.25em 0 0 0;}#car #rate-content #tally
hr.hr{display:none;}#car #rate-content #tally
td.price{text-align:right;padding:.25em 0 0 1.2em;}#car
#rate-content #tally
td.legend{width:60%;text-align:right;padding-right:23px;}#car
#rate-content #tally td.legend
img.greenIcon{height:14px;width:13px;margin-right:8px;}#car
#rate-content #tally
span.total{font-size:1.2em;font-weight:bold;}#car #rate-content
#tally tr.hilite td{padding-top:.25em;}#car #rate-content #tally
tr.hilite div.hr-tally{border-top:1px solid #999;}#car
#rate-content #upsell .img{padding:0;margin:0;}#car #rate-content
#rate-disc{width:54%;float:left;border-left:1px solid
#ccc;margin:8px 0 0 18px;padding-left:18px;}#car #rate-content
#rate-disc div{width:11em;float:left;}#car #rate-content #rate-disc
input{width:10em;}#car table#upsell{width:706px;border-right:1px
solid #ccc;border-bottom:1px solid #ccc;border-left:1px solid
#ccc;margin-top:20px;margin-bottom:4px;}#car table#upsell
td{border-top:1px solid #ccc;padding:0 4px;}#car table#upsell
tr.selected{background:#eaeaea;}#car table#upsell
td.upsell-hd{background:#ccc;padding:4px;font-size:1.1em;font-weight:700;text-align:cente r;}#car
table#upsell td.img{width:120px;}#car table#upsell
td.price{padding:4px;font-weight:700;cursor:pointer;font-size:1.2em;}#car
table#upsell
img.greenIcon{height:14px;width:13px;margin-left:8px;}#car
#spcl-opt{margin:20px 0;width:100%;}#car #spcl-opt
ul{width:30%;float:left;margin:0;padding:0;}#car #spcl-opt
li{list-style-type:none;}#car #spcl-opt
img{vertical-align:middle;}#car-rules
#links{width:180px;float:left;background:#e7ebf0;margin:12px 20px 0
0;}#car-rules #links-content{padding:4px 8px 8px 8px;}#car-rules
#links h4{padding:0;}#car-rules #links ul{margin:0 0 0
14px;padding:0;}#car-rules #links li{margin:2px
0;padding:0;}#car-rules
#policies{width:504px;float:left;margin-top:8px;}#car-rules
#policies h4{margin:8px 0 0;padding:4px 0 2px;}#car-rules #policies
th{padding:6px 12px 0 0;border-bottom:1px solid
#eaeaea;font-weight:bold;empty-cells:show;vertical-align:bottom;}#car-rules
#policies td{padding:6px 12px 0 0;border-bottom:1px solid
#eaeaea;empty-cells:show;}#car-rules p{margin:4px 0;}#location-map
p{margin:4px 0 8px;}#location-map
#map-main{width:705px;height:530px;}#location-map #map-main
ul{padding:0;list-style:none;}#location-map #map-main ul
li{padding:0;list-style:none;}#car #workspace
#nav-btn-hr{width:auto;text-align:center;}#about-content
p{margin:4px 0;}.vendOpts
span{font-size:1.1em;font-weight:700;}#car .recapad{padding:8px 8px
8px 0;position:absolute;right:8px;top:24px;width:315px;}#car
.recapad img{float:right;}#titleRecap.wb_noad #recap{margin:0
8px;}.recap_promo{float:right;text-align:center;width:34%;margin-top:8px;padding-right:8p x;}.recap_promo{width:28%;}.promo_box{background-color:#ffc;border:1px
solid #06c;padding:4px
8px;margin-bottom:6px;}.recap_emph,.pagin_emph,.rev_emph,.gen_emph{font-weight:bold;color :#000;}#content
.promo_box .pkgprice,#content .svgswrap
.pkgprice{font-size:1.27em;font-weight:bold;}.smfont{color:#666;text-align:center;}#hotel Recap{margin-bottom:1em;}#sCase{border:1px
solid #c8d1b6;background:#fff;color:#000;position:relative;}#sCase
h2{background:#c8d1b6;padding:5px;border:0;color:#53574c;font-size:1.3em;}#sCase
#carRecap{margin:5px 10px;}#sCase
.mod_search_link{margin-left:10px;}.carVendor a.shuttle{padding:3px
0 2px 17px;background-repeat:no-repeat;background-position:center
left;}#content #shuttleLegend{display:none;width:338px;padding:8px
0;background-color:#FFF;border:#5f7896 1px solid;}#content
#shuttleLegend h2{margin-left:8px;}#content #shuttleLegend
ul{margin:-7px 0 0 -16px;}#content #shuttleLegend
li{padding-left:28px;background-repeat:no-repeat;background-position:8px
3px;line-height:1.5em;list-style-type:none;}#content #shuttleLegend
li.highlight{background-color:#d5e2eb;font-weight:bold;}#snappy{margin:8px
0;position:relative;}#snappy
.tfArrow{font-size:1.1em;font-weight:900;padding-left:10px;height:35px;}#snappy
#arrow1{position:absolute;left:-1px;top:4px;z-index:1;}#snappy
#arrowText{position:absolute;left:0;top:14px;z-index:3;}#snappy
.snappy_scroll{position:relative;left:110px;height:41px;width:612px;overflow:hidden;z-ind ex:0;padding-top:1px;background:#fff;border-width:1px;border-style:solid;border-color:#036
#959f80 #036 #959f80;}#snappy .snappy_scroll
span{font-size:1.5em;font-weight:900;color:#cb6732;vertical-align:middle;}#snappy
.snappy_scroll img{vertical-align:middle;margin-left:20px;}#snappy
.snappy_scroll span
span{font-size:.69em;font-weight:400;color:#000;}#snappy
.snappy_scroll
#ha_logo{margin-top:3px;margin-right:4px;padding-top:2px;}#advSearch
.stepcontent #pu,#advSearch .stepcontent #do{width:50%;}#advSearch
.stepcontent .sel_loc_off{border-right:solid 1px
#959F80;border-top:solid 1px #fff;border-left:solid 1px
#fff;border-bottom:solid 1px
#959F80;background:#FFE7D0;cursor:pointer;padding:3px 0;

Open in CS4 and use Commands > Apply Source Formatting
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"Lvanhoff" <[email protected]> wrote in
message
news:[email protected]...
> Is there a way to take css code that looks like this
mess (which I got
> elsewhere) and break it into its legible/workable parts
without going
> through
> it and hitting enter after every closing } ? There are
about 1000 lines of
> this
> stuff like this...this is just a small bit of it...is
there any easy way
> in DW
> to break it up properly?
> Thanks in advance...
> Laura
>
> #car .roundbox .topleft{background:no-repeat top
left;width:auto;}#car
> .roundbox .topright{background:no-repeat top
right;padding:0;}#car
> .roundbox
> .infobody{margin:-10px 0 0;padding:0 10px;}#car
.roundbox
> .botleft{background:no-repeat bottom left;}#car
.roundbox
> .botright{background:no-repeat bottom right;}#content
#popupBody #carTypes
> #totals td.totalLine{border-bottom:1px solid #eee;}#car
> #rate-content{display:block;}#car #rate-content
> #tally{width:706px;float:left;margin-top:8px;}#car
#rate-content #tally
> td.fee{padding:.25em 0 0 0;}#car #rate-content #tally
> hr.hr{display:none;}#car
> #rate-content #tally
td.price{text-align:right;padding:.25em 0 0
> 1.2em;}#car
> #rate-content #tally
>
td.legend{width:60%;text-align:right;padding-right:23px;}#car
> #rate-content
> #tally td.legend
>
img.greenIcon{height:14px;width:13px;margin-right:8px;}#car
> #rate-content #tally
span.total{font-size:1.2em;font-weight:bold;}#car
> #rate-content #tally tr.hilite
td{padding-top:.25em;}#car #rate-content
> #tally
> tr.hilite div.hr-tally{border-top:1px solid #999;}#car
#rate-content
> #upsell
> .img{padding:0;margin:0;}#car #rate-content
> #rate-disc{width:54%;float:left;border-left:1px solid
#ccc;margin:8px 0 0
> 18px;padding-left:18px;}#car #rate-content #rate-disc
> div{width:11em;float:left;}#car #rate-content #rate-disc
> input{width:10em;}#car
> table#upsell{width:706px;border-right:1px solid
#ccc;border-bottom:1px
> solid
> #ccc;border-left:1px solid
#ccc;margin-top:20px;margin-bottom:4px;}#car
> table#upsell td{border-top:1px solid #ccc;padding:0
4px;}#car table#upsell
> tr.selected{background:#eaeaea;}#car table#upsell
>
td.upsell-hd{background:#ccc;padding:4px;font-size:1.1em;font-weight:700;text-al
> ign:center;}#car table#upsell td.img{width:120px;}#car
table#upsell
>
td.price{padding:4px;font-weight:700;cursor:pointer;font-size:1.2em;}#car
> table#upsell
img.greenIcon{height:14px;width:13px;margin-left:8px;}#car
> #spcl-opt{margin:20px 0;width:100%;}#car #spcl-opt
> ul{width:30%;float:left;margin:0;padding:0;}#car
#spcl-opt
> li{list-style-type:none;}#car #spcl-opt
> img{vertical-align:middle;}#car-rules
>
#links{width:180px;float:left;background:#e7ebf0;margin:12px 20px 0
> 0;}#car-rules #links-content{padding:4px 8px 8px
8px;}#car-rules #links
> h4{padding:0;}#car-rules #links ul{margin:0 0 0
14px;padding:0;}#car-rules
> #links li{margin:2px 0;padding:0;}#car-rules
>
#policies{width:504px;float:left;margin-top:8px;}#car-rules
#policies
> h4{margin:8px 0 0;padding:4px 0 2px;}#car-rules
#policies th{padding:6px
> 12px 0
> 0;border-bottom:1px solid
>
#eaeaea;font-weight:bold;empty-cells:show;vertical-align:bottom;}#car-rules
> #policies td{padding:6px 12px 0 0;border-bottom:1px
solid
> #eaeaea;empty-cells:show;}#car-rules p{margin:4px
0;}#location-map
> p{margin:4px
> 0 8px;}#location-map
#map-main{width:705px;height:530px;}#location-map
> #map-main ul{padding:0;list-style:none;}#location-map
#map-main ul
> li{padding:0;list-style:none;}#car #workspace
> #nav-btn-hr{width:auto;text-align:center;}#about-content
p{margin:4px
> 0;}.vendOpts span{font-size:1.1em;font-weight:700;}#car
> .recapad{padding:8px
> 8px 8px
0;position:absolute;right:8px;top:24px;width:315px;}#car .recapad
> img{float:right;}#titleRecap.wb_noad #recap{margin:0
>
8px;}.recap_promo{float:right;text-align:center;width:34%;margin-top:8px;padding
>
-right:8px;}.recap_promo{width:28%;}.promo_box{background-color:#ffc;border:1px
> solid #06c;padding:4px
>
8px;margin-bottom:6px;}.recap_emph,.pagin_emph,.rev_emph,.gen_emph{font-weight:b
> old;color:#000;}#content .promo_box .pkgprice,#content
.svgswrap
>
.pkgprice{font-size:1.27em;font-weight:bold;}.smfont{color:#666;text-align:cente
> r;}#hotelRecap{margin-bottom:1em;}#sCase{border:1px
solid
>
#c8d1b6;background:#fff;color:#000;position:relative;}#sCase
>
h2{background:#c8d1b6;padding:5px;border:0;color:#53574c;font-size:1.3em;}#sCase
> #carRecap{margin:5px 10px;}#sCase
> .mod_search_link{margin-left:10px;}.carVendor
a.shuttle{padding:3px 0 2px
>
17px;background-repeat:no-repeat;background-position:center
left;}#content
> #shuttleLegend{display:none;width:338px;padding:8px
> 0;background-color:#FFF;border:#5f7896 1px
solid;}#content #shuttleLegend
> h2{margin-left:8px;}#content #shuttleLegend
ul{margin:-7px 0
> 0 -16px;}#content
> #shuttleLegend
>
li{padding-left:28px;background-repeat:no-repeat;background-position:8px
> 3px;line-height:1.5em;list-style-type:none;}#content
#shuttleLegend
>
li.highlight{background-color:#d5e2eb;font-weight:bold;}#snappy{margin:8px
> 0;position:relative;}#snappy
>
.tfArrow{font-size:1.1em;font-weight:900;padding-left:10px;height:35px;}#snappy
>
#arrow1{position:absolute;left:-1px;top:4px;z-index:1;}#snappy
>
#arrowText{position:absolute;left:0;top:14px;z-index:3;}#snappy
>
.snappy_scroll{position:relative;left:110px;height:41px;width:612px;overflow:hid
>
den;z-index:0;padding-top:1px;background:#fff;border-width:1px;border-style:soli
> d;border-color:#036 #959f80 #036 #959f80;}#snappy
.snappy_scroll
>
span{font-size:1.5em;font-weight:900;color:#cb6732;vertical-align:middle;}#snapp
> y .snappy_scroll
img{vertical-align:middle;margin-left:20px;}#snappy
> .snappy_scroll span
> span{font-size:.69em;font-weight:400;color:#000;}#snappy
> .snappy_scroll
>
#ha_logo{margin-top:3px;margin-right:4px;padding-top:2px;}#advSearch
> .stepcontent #pu,#advSearch .stepcontent
#do{width:50%;}#advSearch
> .stepcontent
> .sel_loc_off{border-right:solid 1px
#959F80;border-top:solid 1px
> #fff;border-left:solid 1px #fff;border-bottom:solid 1px
> #959F80;background:#FFE7D0;cursor:pointer;padding:3px 0;
>

Creating Axes Titles, Chart Titles from Sheet Cells

Hi all,
I'm trying to create a completely automated document from Numbers 09. I'd like my chart to grab its category, x-axis and y-axis titles from text placed in cells within the spreadsheet. Although I could create an AppleScript to do this on my Mac, the iPad and iPhone do not operate with AppleScript. So, how would it be possible to make a self-contatined Numbers 09 doc such that whether I use the sheet on my Mac or iPhone, a chart's titles for the x-axis, y-axis and chart come from data contained in a spreadsheet's cells?
Thanks

I've isolated the issue, but I'm not sure if it's a bug or if
something I'm doing wrong. The following simplified version of my
chart application doesn't display the axis titles:
[code]
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
<mx:Legend dataProvider="{chart}" left="0" top="25"
id="legend"/>
<mx:CartesianChart left="{legend.width}" top="30"
right="0" bottom="0" id="chart">
<mx:verticalAxis>
<mx:LinearAxis title="Dollars"/>
</mx:verticalAxis>
<mx:horizontalAxis>
<mx:CategoryAxis title="Year"/>
</mx:horizontalAxis>
</mx:CartesianChart>
</mx:Application>
[/code]
The following version does:
[code]
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
<mx:Legend dataProvider="{chart}" left="0" top="25"
id="legend"/>
<mx:CartesianChart left="{0}" top="30" right="0"
bottom="0" id="chart">
<mx:verticalAxis>
<mx:LinearAxis title="Dollars"/>
</mx:verticalAxis>
<mx:horizontalAxis>
<mx:CategoryAxis title="Year"/>
</mx:horizontalAxis>
</mx:CartesianChart>
</mx:Application>
[/code]
The only difference is the left definition for
mx:CartesianChart. When it's defined in terms of the width of the
legend, the axis titles disappear. Is there another way that I
should be displaying my chart using the full span of the
application?
Thanks again for your help.

Resizing WaveformChart adds 24 pixels for no reason

Hello all,
I've been working on automatically resizing the front panel of a VI I use very frequently on many different computers. It's all working quite well, but I've run into a strange bug that's driving me insane. A screenshot of where the problem occurs is below:
The rest of the code isn't really relevant (and there's a lot of it), but suffice it to say, I'm scaling the size of the waveform chart and it's accompanying legend according to a scaling factor that works for my application as determined elsewhere. The scaling factor is coerced to be between 0 and 1 as a double. It works beautifully for every value I've tested it on, except if the scaling factor I'm multiplying by is 1. When the scaling factor is 1, the legend width (LegWidth above) somehow gets 24 pixels added to it. Probing what I read from LegWidth, what I write to it after multiplying by the scaling factor and the scaling factor itself, everything looks great. It starts as 270, I multiply by 1.00, the value I write to LegWidth on the other side is 270 as expected. But the legend grows 24 pixels wider (making it look awful) and subsequent calls to this same code show that the value is now 294. Probing again, everything appears to be doing what it's supposed to (294 is read, the scaling factor is 1.00, the write value is 294) and again the legend grows by another 24 pixels. Same story for subsequent executions, every time i call this code another 24 pixels is added despite that never showing up in my code. An XY Chart in another tab on the same tab control has the exact same behavior (legend grows 24 pixels wider for every resizing).
So, I can fix this easily by adding a case statement to not execute this code if the scaling factor is 1.00, but it worries me that this isn't behaving correctly. Are there any settings that could be affecting this? Autosizing the legend is definitely turned off. I don't think it's another part of my code because it works beautifully for all other values I've tested. For the record, I'm running 32 bit Labview 2013 on Windows 7 with a 64 bit processor (Intel Core i7). Any ideas/thoughts are appreciated, I'm pretty thoroughly stumped and about to just add the case statement and live with the anxiety that my program is going to start adding 24 pixels in undesired places against my will...
Kevin

Can you attach your actual VI rather than just a picture of a portion of your code so that we can experiment with?

Long plot names

hi
I am trying to update the plot names according to the files I open (the plot gets the files name).
my problem is I can only have 12 characters in the plot name and could not enlarge the plot name area. any suggestions?
thank
Amos
Attachments:
graph.png ‏50 KB

amose wrote:
I am trying to update the plot names according to the files I open (the plot gets the files name). my problem is I can only have 12 characters in the plot name and could not enlarge the plot name area. any suggestions? ... I have LV 6.1
Amos,
Unfortunately, LV6.1 doesn’t have the AutosizeLegend property.
If you're interested in doing it manually:
Use the positioning tool to resize the legend from either left corner. That increases the width for the plotname.
Programatically:
Unfortunately (again), you can't use the graph's Legend:Width property because it expands/contracts on the right side … which is the wrong side for the plotname.
If you have more than the base LabVIEW package, you could do something like the attached which uses an array for the plotnames and makes use of Get Text Rect.vi (which is not in the base package).
=====================================================
Fading out. " ... J. Arthur Rank on gong."
Attachments:
PlotNameWidthChanges_61.vi ‏40 KB

Legend width

Similar Messages

Maybe you are looking for