Tags:
tag this topic
create new tag
view all tags
---+ .PIE SECT ADD NEXT _This subroutine is called to create a new pic chart sector spec._ <br />%TOC% ---++ Usage: <pre> PASS <sector_data_point> FIELD SHARE? N PASS <sector_label> FIELD SHARE? N PASS <text_spec_name> FIELD SHARE? N GOSUB 0CD .PIE SECT ADD NEXT * Check for error IF 0CD .PIE SECT ADD NEXT NE</pre> ---++ Description: <div id="_mcePaste">This subroutine creates a new pic chart sector spec for the "current" chart, and optionally adds a label. This is an easy way to add data and labels to your pie chart simutaneously. If you want to change the attributes of the sector just added (ie, 3D Depth, Color, etc), do that before adding the next sector. Any changes you made to the attributes of the newly added sector will be inherited by the next sector you add, unless you pass 'initialize' as the <text_spec_name> parameter (see below).</div> The <sector_data_point> parameter is optional. If a <sector_data_point> is received, then the corresponding data point record is created or updated. The <sector_label> parameter is optional. If a <sector_label> is received, that label will be used on your pie chart and a text spec will be created for the label. You can use the .TEXT routines to change the attributes of the text associated with this data point. Remember that any changes you make will be inherited by the next sector you add, unless you pass 'initialize' as the <text_spec_name> parameter The <text_spec_name> parameter is optional. If a <text_spec_name> is received, that text spec will be used to create the label. You can also pass "current" to use the "current" text spec, or "initialize" to reset the text spec back to defaults before adding the sector. The "initialize" value is useful if you have changed the attributes on the previous sector and you want the next one(s) to use default values. If you do not pass a <text_spec_name>, the previous text spec will be used. The newly added data point is set to be the "current" data point, the newly added sector is set to be the "current" sector spec, and if a <text_spec_name> is provided, it becomes the "current" text spec. ---++ Comments: _Read what other users have said about this page or add your own comments._ <br /> I ran into the problem that <sector_dat_point> in my application (because of system parameters) the decimal notation is a comma instead of a dot. If you give this parameter a value with a comma in it, you get two sectors instead of one. After I set the value in an alpha field and changed the comma to a dot, the problem was over and I got a nice "one-sector". I believe this is reported to ASI. -- %BUBBLESIG{WimJongejan - 2015-03-06}% %COMMENT% -- Main.JeanNeron - 2011-10-03
E
dit
|
A
ttach
|
Watch
|
P
rint version
|
H
istory
: r5
<
r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r5 - 2015-03-06
-
WimJongejan
Home
Site map
Main web
MedicaidBilling web
Sandbox web
TWiki web
Main Web
Users
Groups
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
P
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
E
dit
A
ttach
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback