Difference: CDColorGetName (1 vs. 2)

Revision 22011-11-16 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="CDChartDirectorDesignerAPI"

.COLOR GET NAME

Changed:

<
<

This subroutine is called to get the name of the "current" color spec.

>
>

This subroutine is called to get the name of the "current" color object.

.COLOR GET NAME

Usage:

Line: 15 to 15

Description:

Changed:

<
<

<color_spec_name> is the value returned to you, and is the name which uniquely identifies the "current" color spec. The receiving field should be at least 30 characters in length.

>
>

<color_spec_name> is the value returned to you, and is the name which uniquely identifies the "current" color object. The receiving field should be at least 30 characters in length.

Changed:

<
<

If the "unnamed" color spec is the current color spec, then the name returned will be blank.

>
>

If the "unnamed" color object is the current color object, then the name returned will be blank.

The name of the current color is returned in <color_spec_name> so this parameter must be passed shared.

Revision 12011-11-15 - JeanNeron

Line: 1 to 1

Added:

>
>

META TOPICPARENT	name="CDChartDirectorDesignerAPI"

.COLOR GET NAME

This subroutine is called to get the name of the "current" color spec.

.COLOR GET NAME

Usage:

      PASS         <color_spec_name>          FIELD            SHARE? Y
      GOSUB    0CD .COLOR GET NAME
      *        Check for error
      IF       0CD .COLOR GET NAME            NE

Description:

<color_spec_name> is the value returned to you, and is the name which uniquely identifies the "current" color spec. The receiving field should be at least 30 characters in length.

If the "unnamed" color spec is the current color spec, then the name returned will be blank.

The name of the current color is returned in <color_spec_name> so this parameter must be passed shared.

See ColorSpec for more information on working with colors.

Comments:

Read what other users have said about this page or add your own comments.

<--/commentPlugin-->

-- JeanNeron - 2011-11-15

View topic | History: r4 < r3 < r2 < r1 | More topic actions...