Life In 19x19

fwiffo wrote:Just so I'm clear - which is showing up wrong, the text in the "show diagram code" thing or the text in the <textarea> when you're editing a post?

Textarea.

Give it a refresh - does it work now?

fwiffo wrote:Give it a refresh - does it work now?

Works now for Chrome 5 on OS X (thanks!) but not for Safari 4 on OS X.

Does Safari usually use a proportional font in <textarea>s? Let me try one more thing... Does that work? If not, can you check to see if your browser actually has a monospace font set as its default monospace font?

I freaking hate web browsers.

fwiffo wrote:Does Safari usually use a proportional font in <textarea>s? Let me try one more thing... Does that work? If not, can you check to see if your browser actually has a monospace font set as its default monospace font?

I freaking hate web browsers.

I think so; I tried pasting the same stuff into GD's textarea and it comes out looking okay. Still doesn't work here. Safari has a Standard font set to Times 16 and a "Fixed-width font" set to Courier 13, but nothing on monospace font settings - assuming they're not the same thing.

Yeah, that fixed width setting is what I'm looking for, and Courier is a monospace font. I assume you've tried clearing your cache?

fwiffo wrote:Yeah, that fixed width setting is what I'm looking for, and Courier is a monospace font. I assume you've tried clearing your cache?

Ah, forgot about that sorry. Yes, it works all dandy now. Thanks!

Sweet. For future reference, those wishing to help debug problems like this please remember to do that (or at least do a hard-refresh).

fwiffo wrote:Sweet. For future reference, those wishing to help debug problems like this please remember to do that (or at least do a hard-refresh).

Darn QA testers... always reporting problems when the devs say "works for me"

Thanks for all the work guys. I have one more request. I'd like to see closing delimiters in the same column as opening delimiters. ( In this instance, I think that means at the beginning of a new line. )

This is ok:


TAG_TYPE_1
misc stuff
TAG_TYPE_2
more misc stuff which might be a really really really long sentence.
CLOSE_TAG_2
other misc text
more misc stuff which can be arbitrarily long but doesn't affect readability.
CLOSE_TAG_1


This is a pain in the rear:


TAG_TYPE_1
misc stuff
TAG_TYPE_2
more misc stuff which happens to be very long so you don't see the closing tag. CLOSE_TAG_2
other misc text
more misc stuff which also happens to be rather long. CLOSE_TAG_1


The two posts have the same logic, but the first is much easier to read. I can write a post in the first style, and when I edit it, the editor has transposed it into the second style.

fwiffo wrote:Just so I'm clear - which is showing up wrong, the text in the "show diagram code" thing or the text in the <textarea> when you're editing a post?

What happened with me was that the text in "show diagram code" was in proportional font, and remained so when I copied it to the window I am in now.

I just checked, and now the same diagram code shows up right. Many thanks.

sumiyaka wrote:Sounds good, it should be a good fix, at least for the time being.

At some point the diagrammer could be taught to ignore any whitespace prior to a '$', but for now, who cares, on with the Malkovich games!

Quoting myself... bah...

But, I'm running into spaces showing up in diagrams after cut and pasting again. I am not sure why. Any way for the parser to ignore whitespace prior to the $$? I know its probably a more difficult fix, but completely eliminates the issue no matter what stupid users like me type between to the "go" tags.

sumiyaka wrote:

sumiyaka wrote:Sounds good, it should be a good fix, at least for the time being.

At some point the diagrammer could be taught to ignore any whitespace prior to a '$', but for now, who cares, on with the Malkovich games!

Quoting myself... bah...

But, I'm running into spaces showing up in diagrams after cut and pasting again. I am not sure why. Any way for the parser to ignore whitespace prior to the $$? I know its probably a more difficult fix, but completely eliminates the issue no matter what stupid users like me type between to the "go" tags.

I've had this happen a few times here and there, and it seems random...can't quite figure out why it happens.

Now that I think about it, I think the best solution is to have a "Click Here to Copy Diagram Code" instead of a "Click Here to Show Diagram Code" link.

I'll try to work on diagrams sometime this week... Sorry for the delay.

No worries on timing... It didn't happen to me this afternoon, so maybe it is a bit more random.