Set size in d.northarrow

[wenzeslaus]

Size of the north arrow cannot be changed. All symbols are scaled to one common size, that's good, but this size should be further rescaled by a value of a size option.

[lazaa]

Replying to wenzeslaus:

Size of the north arrow cannot be changed. All symbols are scaled to one common size, that's good, but this size should be further rescaled by a value of a size option.

The size of symbol is manually tuned and for each symbol is quite different. I would add size option. If user doesn't use size manually tuned size will be used. But if user writes size=25 for some symbols it will have increasing size effect and for others decreasing size effect. Is it OK? User would have to find right size for a symbol and after that if he changed mind and wanted use another symbol he would have to find the right size one more time.

    /* sizes manually tuned */
    switch (n_arrow_num[0]) {
    case '7':
        symbol_size = 23.;
        break;
    case '8':
    case '9':
        symbol_size = 17.;
        break;
    case 'b':
        symbol_size = 80.;
        break;
    case 'f':
        symbol_size = 100.;
        break;

[wenzeslaus]

Replying to lazaa:

Replying to wenzeslaus:

All symbols are scaled to one common size, that's good, but this size should be further rescaled by a value of a size option.

If user doesn't use size manually tuned size will be used. But if user writes size=25 for some symbols it will have increasing size effect and for others decreasing size effect.

I don't know what is better if to scale, as I suggested, which is different behavior from all the other modules (so it might be better to call it scale), or if it is better to overwrite the size, as you suggest and consequently make it potentially harder for the user (symbols in d.vect behave the same but they have more similar sizes).

For now, I suggest to skip this issue.

[martinl]

Milestone renamed

[neteler]

Ticket retargeted after milestone closed

[martinl]

Can we close the issue?

[annakrat]

No, it's still valid problem. But I am not sure which is the right solution at this point.

[martinl]

All enhancement tickets should be assigned to 7.6 milestone.

[martinl]

Ticket retargeted after milestone closed

[martinl]

Ticket retargeted after milestone closed