Bug with the DVXuser interface...

[joeloud]

I'm a keyboard shortcut user, and on a Mac, holding Command+Left Arrow navigates one page back in Firefox. Also, when typing, Command+Left Arrow moves the cursor to the beginning of the line. How come on every other website I go to, when I'm typing in a text box, Firefox ignores the command as an attempt to navigate back, and moves the cursor to the beginning of the line. On DVXUser, when I'm typing, I hit Command+Left, and it navigates back, ignoring the fact that the text box has focus.

This isn't usually a huge problem, since when this happens on the advanced text editor, I can navigate forward and the text will still be there. However, in the Quick Reply box, it always clears the box when I do this accidentally. It also wouldn't be a huge problem if every other website worked this way, I'd learn to compensate, but it's such a habit with every other website and word processor I've ever used, I always run into it when I'm posting here.

Anyone else get hit with this? Is there maybe a fix on a to-do list or something?

Don't get me wrong, I love the boards, it's just this one bug has killed a couple long posts in the past and today's was the last straw.

[Anhar Miah]

Thats why for long posts I use offline word processors, even notepad is nice; then just C&P.

Simple solution, fewer heahaches, more time to enjoy life..

[joeloud]

Yeah, I do that sometimes if I'm planning on writing a long post, but usually my long posts are just because I meant to write something short and then kept adding more to it, and got lazy with opening the word processor. It's not a huge deal, I wrote the above post immediately after losing a semi-long post, so I was just annoyed with myself. I re-wrote it, no big deal.

[Beat Takeshi]

Wow, You know you spend too much time online when you have to use a word processor to compile your posts. ;)

[Mattykins]

It's Anhar - would you expect any less? :)

[Tom Marshall]

Yeah, but Aram is the one talking about "compiling" posts... :D

[Mattykins]

Oh, rough.

More effort then I care to spend. My solution to this is simple. It has happened to me countless times before. I finish writing a profound post (mostly about explaining how digital camera systems work) and then I lose everything.

I briefly stare at my computer in hatred. And then think:

"I guess that isn't getting posted"

And move on. Haha. The technical fix - couldn't help you.

[Tom Marshall]

The technical fix is don't use a Macintosh. :D

[Dingos8mybaby]

Shift+Command+Left Arrow will get the cursor to the beginning of the line. It highlights it but just push the Left Arrow again...wow, that was such a noob response. :)

[joeloud]

Yeah, it occurred to me shortly after posting in the first place that I could highlight it and it would work. Now I have to get used to doing that, heh.

I briefly stare at my computer in hatred. And then think:

"I guess that isn't getting posted"
I try to do that, but I usually end up going back to the page and re-typing it anyway.

[Anhar Miah]

to answer your question:

16 6 44 14 ; 22 44 ; 50 6 42 ; 32 34 44 ; 30 14 6 32 ; 44 8 ; 8 14

hint:
Its half as large and off by 2 :D

[Tom Marshall]

Hey Anhar, can I get some Excedrine to go with all that math? :laugh:

[Gord.T]

I had a quick look at the code Anhar. It's not Ascii hex or oct.
If the character can be either *2+2 or *2-2 then at best the first two characters would be " and a line feed,
just to show how much time I have to waste (while I'm rendering, ofcourse). http://www.freesmileys.org/smileys/computer003.gif (http://www.freesmileys.org)

That and the fact these are short statements, annnnd, knowing you, I'm thinking it's ASM.
We'll, sorry I can't solve it right now, cause I've got things to do, places to go, people to meet.
http://www.freesmileys.org/smileys/alien011.gif (http://www.freesmileys.org)

[joeloud]

I think you might have written your code wrong... I got "fate it was not mean tb be"

Did you mean "fate it was not meant to be?"

If that were the case, the code should have read:
16 6 44 14 ; 22 44 ; 50 6 42 ; 32 34 44 ; 30 14 6 32 44 ; 44 34 ; 8 14

;)

[Anhar Miah]

I think you might have written your code wrong... I got "fate it was not mean tb be"

Did you mean "fate it was not meant to be?"

If that were the case, the code should have read:
16 6 44 14 ; 22 44 ; 50 6 42 ; 32 34 44 ; 30 14 6 32 44 ; 44 34 ; 8 14

;)

Yep thats right, damn made a typo! :P

@ Raptor, :D man your over analysing again its just simple A = 1 B =2 etc !

of course if you want it in assembly...