Version 1.1.1: Named Parameters!

Hello There !

Since the possible number of arguments (x_indent, y_indent, angle, scale, tint and additional arguments for filters) is increasing - and will increase even more with the features planned - I took the time to implement an alternative way to write the parameters to the <ADJ > object notation: The Named Parameters

Before this addon, the notation had to contain the first 5 parameters before it was possible to attach filters to the events' image. This means that you had to assign the parameters defaults to them to be able to continue to the next parameter. This said, this notation maybe didn't work because "expected" parameters were missing: 

<ADJ: 0 10 glow:10>
This failed because the process expected <ADJ: [x_indent] [y_indent] [rotation_angle] [scale_factor] [tint_color] glow:10>.

The new approach does work with the old queuing (handling the arguments in a specific order), but also understands the Named Parameters:

<ADJ: y:10 x:0 glow:10>
This works since there is no queuing in this version. Also notice that the y-parameter now is positioned before the x-parameter, which also would have caused unwanted results in the queuing-approach.

So here's the list of new Named Parameters:

• x (=> x_indent value, eg. x:5)
• y (=> y_indent value, eg. y:10)
• angle (=> rotation angle of the events' image in degrees, eg. angle:15)
• scale (=> scale value of the image, eg. scale:1.2)
• tint (=> tint value of the image, eg. tint:0xff0000)

To decide which method should be used here, the process looks at the first parameter. If the first parameter is a number, the Queue-Method will be expected, if not the Named-Parameters-Method will be used.

So in conclusion you can assign the parameters in two ways now:

1. Queuing => <ADJ: [X_INDENT] [Y_INDENT] {ANGLE] {SCALE] [TINT] (optional)[FILTER_1] (optional)[FILTER_2] ... >
2. Named Parameters => <ADJ: (optional)y:[Y_INDENT] (optional)scale:[SCALE] .... >

Have Fun !

Yossaya