Cons Dist in Standard Report

[QUOTE=me_hungry;113101]First method is to use UDA.

Second method is to customize with PML
Create PML function:
define function !!getDist(!pos1 is POSITION, !pos2 is POSITION) is STRING
   var !dist cons dist $!pos1 to $!pos2
   return !dist
endfunction

Run in commandline to show pdms new function:
pml rehash all

And after you create quick report and run. Open file that it generated here %pdmswk%/TMP.MAC .
Add this line, after declaration of variable !col2 ... ignore any ||.
In my case !col2 - is for second column

!col2 = !selection.EVALUATE(OBJECT BLOCK('!!getDist(!selection[!EVALINDEX].dbref().PPos[1],!selection[!EVALINDEX].dbref().PPos[3])'))


Awesome, Thanks, I will check this.

[COLOR="silver"]- - - Updated - - -[/COLOR]

[QUOTE=mno;113100]My apologies, I did not read your entire question, truly sorry about that. What I suggested will not work in a quick report.
Now to get that info into a report might be slightly tricky, the only way I can think of is to create a pseudo uda that does the calculation when you query it. You could then add this uda to your quick report. I tried with a standard report as well but that didn't work either. Does anyone else have any ideas about this?

Thanks MNO for the update

[QUOTE=me_hungry;113101]First method is to use UDA.

Second method is to customize with PML
Create PML function:
define function !!getDist(!pos1 is POSITION, !pos2 is POSITION) is STRING
   var !dist cons dist $!pos1 to $!pos2
   return !dist
endfunction

Run in commandline to show pdms new function:
pml rehash all

And after you create quick report and run. Open file that it generated here %pdmswk%/TMP.MAC .
Add this line, after declaration of variable !col2 ... ignore any ||.
In my case !col2 - is for second column

!col2 = !selection.EVALUATE(OBJECT BLOCK('!!getDist(!selection[!EVALINDEX].dbref().PPos[1],!selection[!EVALINDEX].dbref().PPos[3])'))


Awesome, Thanks, I will check this.

[COLOR="silver"]- - - Updated - - -[/COLOR]

[QUOTE=mno;113100]My apologies, I did not read your entire question, truly sorry about that. What I suggested will not work in a quick report.
Now to get that info into a report might be slightly tricky, the only way I can think of is to create a pseudo uda that does the calculation when you query it. You could then add this uda to your quick report. I tried with a standard report as well but that didn't work either. Does anyone else have any ideas about this?

Thanks MNO for the update