It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
JoeSapphire: yeah, they use internet explorer 0_o
avatar
SirPrimalform: Oh wow.

I wonder if it's the same problem I have on my phone. When you go to the PM page are you unable to open any of the conversations?
I can sort of get around this by finding a post from that person on the forum and choosing "start conversation" on the little pop up menu. It probably won't work, but might be worth a try.
There is another trick to make PMs work on mobile, you can't click on people's names in the list but if you type the name and hit enter it should open a conversation.
avatar
adaliabooks: There is another trick to make PMs work on mobile, you can't click on people's names in the list but if you type the name and hit enter it should open a conversation.
Or you can go to their name in a thread and when you click on their avatar you get the option to "Start conversation"


I see SirP already said that....
Post edited September 03, 2018 by trentonlf
Or type https://www.gog.com/u/*name*/chat in url bar.
Post edited September 03, 2018 by ZFR
avatar
ZFR: Or type https://www.gog.com/u/*name*/chat in url bar.
YOU'RE ALIVE! I'm so relieved.
avatar
SirPrimalform: YOU'RE ALIVE! I'm so relieved.
Nah, he somehow managed to get his hands on a phone at that Zombier festival he's attending.
I think Joe should modkill Bookwyrm in retaliation for Yog's transgression. It's only fair!
@Joe: will Sage be replaced? Or was she able to fix her connection problems and can actually play again?
avatar
Lifthrasil: @Joe: will Sage be replaced? Or was she able to fix her connection problems and can actually play again?
Oh yeah, Sage has been replaced by Hunter65536.
thanks for reminding me
avatar
trentonlf: Or you can go to their name in a thread and when you click on their avatar you get the option to "Start conversation"
Sadly, that no longer works on my mobile device.

I'll try to remember some of these other methods so I can try them.


avatar
SirPrimalform: I think Joe should modkill Bookwyrm in retaliation for Yog's transgression. It's only fair!
...What in the everloving boop has been happening in the game while I've been afk?? (To prevent any question of out-of-game game discussion, don't actually answer that.)

I let it slide over the weekend, but I see I'm really going to need to catch up.
Post edited September 04, 2018 by Bookwyrm627
avatar
Bookwyrm627:
Oh, I didn't mean you! I meant Bookwyrm628, he's the first one I tend to think of when I read/write Bookwyrm. I forgot there were two Bookwyrms, how embarassing.
Post edited September 04, 2018 by SirPrimalform
avatar
mchack: I bought it.
only caught that it wasn't you because you talked yourself down like that.
"!= true" reads as "not true", no?
hmm, what would be the right syntax ... maybe "if x NOT true" ... or "if x false".
anyway it's c pseudo code isn't it? I have no Idea how you'd actually write it down, but I feel like I completely understood how bookwyrms code should run, so mission accomplished for pseudocode, right? :)
avatar
Bookwyrm627: Eh, he kind of has a point. That was really, really lazy pseudo code on my part, though it seems to have accomplished its objective.

A better formatted example would look more like this:

if(!shotTaken) {
Shoot();
} else {
AskOthersToShoot();
}

-The variable was obviously a boolean, so just use the 'not' on it directly in the if statement.
So... this company is helping us on a project, and they have a practice that in their code they ALWAYS include "true ==" or "false ==" in their conditionals. So for example they'd do:

if (true == condition) {
// stuff
}

Apparently it's good practice to spot any errors. And I have to agree that c

while (false == condition1 ||
false == condition2)

can be easier to read than

while (!condition1 ||
!condition2)

especially if going through someone else's code.

Also it's in line with their policy of comparing a number to a variable
if (1 == var)
instead of
if (var == 1)
which makes it easier to avoid mistakes of putting = instead of == (the former won't compile in such a case, the latter will compile and lead to unexpected behaviour).

This last thing I've seen already before (though I don't use it myself since it's not an issue in C#). The adding of true or false is a new one.

You live and learn.
avatar
ZFR: [replay to a post nearly a year old]
You...have a long memory.

Those coding practices do make sense, though.
avatar
ZFR: [replay to a post nearly a year old]
avatar
Bookwyrm627: You...have a long memory.
I was reading through those old threads like a month ago only, when I was preparing the "flavour" (if you can call it such) of my last game.
avatar
Bookwyrm627: You...have a long memory.
avatar
ZFR: I was reading through those old threads like a month ago only, when I was preparing the "flavour" (if you can call it such) of my last game.
Ah. That makes sense.

I was looking at some of these posts and going "Eh, I don't remember saying that, but it looks like something I might say".