#dev | Logs for 2017-08-08

« return
[00:24:25] <TheMightyBuzzard> FatPhil, looking to have the default be last story's time +90ish minutes. that work?
[00:26:41] <Bytram> ^^ ignoring stories marked NOT display
[00:27:47] <Bytram> FatPhil: thanks for the explanation in the notes on why you put that story off to the next day... and it brings up a possible issue in computing the date/time for the next story. =)
[06:46:49] <FatPhil> TheMightyBuzzard: auto sensible spacing would be ideal
[16:30:06] <Bytram> FatPhil: 'auto sensible spacing' of... what? the release date/time stamp?
[16:35:27] <FatPhil> yup, when you click preview, rather than just putting the current time stamp in the date field it scans the upcoming queue and looks for a gap.
[16:37:39] <Bytram> ohhhh, now I get what you mean. problem arises though, as we don't always keep the same 'gap'
[16:38:18] <Bytram> maybe a bot could take a date/time stamp, a delta, and post that as a reply in the proper format?
[16:39:56] <Bytram> I've got a windows batch program that does the work for me:
[16:39:58] <Bytram> CALL SN_story_next 1 93
[16:41:22] <Bytram> skips the top-most story, gets the date/time stamp of the (second-to-the-top) story, adds an offset of 93 minutes, and displays what the resulting date/time stamp would be (as well as pasting it into the windows copy/paste buffer)
[16:41:35] <Bytram> it's output (just tried it a moment ago) is:
[16:41:37] <Bytram> Selected story is scheduled for: 2017/08/09 11:56:00
[16:41:37] <Bytram> Requested date/time delta in minutes: 93
[16:41:37] <Bytram> Next story should be scheduled for: 2017/08/09 13:29:00
[16:42:43] <Bytram> with the "2017/08/09 13:29:00" value in my copy/paste buffer, I can just paste that into the release date/time stamp for the current story, hit preview to make sure nobody snuck something in while I was not looking (it happens) and then hit save.
[16:43:18] <Bytram> I find it tremendously helpful and saves much time/aggravation... just trying to think of how to make it more accessible.