depwl9992 / anomalyjobs

Automatically exported from code.google.com/p/anomalyjobs
0 stars 0 forks source link

First comment not reported as "published" when job has multiple sources #170

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
* What steps will reproduce the problem?
1. Find a job with multiple dbrefs in OPENED_BY
2. switch( extract( get( <job dbref>/comment_1 ), 3, 1, | ), get( <job 
dbref>/OPENED_BY ), 1, 0 )

This is from code found in DEFAULT_READ to display the +.

* What is the expected output?
"1" -- I would think that the initial comment, showing as [1+] in other jobs, 
would be seen as [1+] in multi-sourced jobs as well.

* What do you see instead?
"0"

* What version of the product are you using? On what MU* Server?

<jobs> VERSION: v6.4

MUX 2.10.1.12 #2 [2012-JUL-07]
Build date: Tue Jan  1 20:04:41 PST 2013

* Please provide any additional information below:

This works for me: 

think t( setinter( extract( get( <job dbref>/comment_1 ), 3, 1, | ), get( <job 
dbref>/OPENED_BY )))

I'm not sure what the expected behavior of aJobs is, or why. Explanation would 
help me untangle bits of it. Thanks.

Original issue reported on code.google.com by thenomain@gmail.com on 20 Mar 2013 at 4:39

GoogleCodeExporter commented 9 years ago
Looking deeper, this has been entered to fix the issue already. Thanks.

http://code.google.com/p/anomalyjobs/source/detail?r=422 

Original comment by thenomain@gmail.com on 20 Mar 2013 at 4:44

GoogleCodeExporter commented 9 years ago
I was just about to post that.  And I'm long overdue to get version 6.6 out.   
But yes, r422 should fix the issue and will be in version 6.6.

I'll leave this issue open as a reminder that someone other than myself has 
identified this as a problem and I should release 6.6.

Original comment by widdis@gmail.com on 20 Mar 2013 at 5:03

GoogleCodeExporter commented 9 years ago
Fixed in r422. 6.6 will be releasing 'soon'.

Original comment by Fleety...@gmail.com on 27 May 2014 at 2:51