| | <<<Back 1 day (to 2018/04/25) | 20180426 |
| Robin_Watts | kens: Morning | 10:18.39 |
| kens | Hi | 10:18.43 |
| ghostbot | Welcome to #ghostscript. If you have a question, please ask it, don't ask to ask it. Do be prepared to wait for a reply as devs will check the logs and reply when they come on line. If you are looking for help or infomation about MuPDF, try the new #mupdf channel. | 10:18.43 |
| kens | Seems you had some problems ? | 10:18.49 |
| Robin_Watts | yeah. Got there in the end, I think: | 10:19.08 |
| | http://git.ghostscript.com/?p=user/robin/ghostpdl.git;a=commitdiff;h=8419ee218c0ca070686596a8743767aeaf097689 | 10:19.09 |
| kens | Hmm, I don't think I can realisitcally review it, not with any meaningful input. I didn't write teh code and this is probably the first tiem I've actually looked at it. I'd need to follow it through to have much chance of contributing anything useful. | 10:20.26 |
| | In the long run I'd prefer a proper device, but obviously that's not going to happen in the time available. | 10:20.49 |
| | So if it passes cluster testing then I guess its good enough | 10:20.59 |
| Robin_Watts | kens: cool. The main thing is that I don't want to put it in only to find you strenuously object :) | 10:21.46 |
| kens | To be honest, I object more to the way it was originally done :-( | 10:22.02 |
| Robin_Watts | Yeah, this whole gs thing of "I'll get a device and feel free to poke around inside its device functions" is really grotty. | 10:23.19 |
| | poke around inside your *own* device functions, sure. | 10:23.34 |
| kens | Yeah that's pretty much waht I mean. Would be better to write a complete new device and have it do thte footling. But I guess that looked hard at the time | 10:23.59 |
| | Maybe one day we could do a decent device that works in a reliable fashion. But not today. | 10:25.14 |
| Robin_Watts | kens: Maybe today :( | 12:19.26 |
| kens | Seriously ? | 12:19.33 |
| | More bad news ? | 12:19.40 |
| Robin_Watts | yeah. | 12:19.45 |
| kens | :-( | 12:19.51 |
| Robin_Watts | I've got a case where it uses one of these things for a type3 image. | 12:19.55 |
| | so it has to cope with a begin_typed_image. | 12:20.13 |
| kens | can't remember what a type 3 image is offhand | 12:20.18 |
| Robin_Watts | and that (as best I can figure) means it has to make a penum into which it puts the device. | 12:20.42 |
| kens | I think a typed image will need an enumerator yes | 12:20.56 |
| Robin_Watts | and so that device can't have the right height/width for both cases :( | 12:21.02 |
| | so I get memory corruption. | 12:21.08 |
| kens | Yeah that was what I was talking about yestreday with enumerators | 12:21.17 |
| Robin_Watts | So either I need to alter the calling code, and just ignore this problem, or I need to do the device properly. | 12:21.27 |
| Robin_Watts | goes to get lunch to ponder it. | 12:21.36 |
| | Forward 1 day (to 2018/04/27)>>> | |
Log of #ghostscript at irc.freenode.net.