IP problems

[TheQwerty]

maybe it's because you keep your IP closed, since that's where the bug is more evident.

Indeed, it is less noticeable when it is only the status bar that should change. But I think this might even point towards the bug occurring (well, being triggered) only when the IP is open.

[Muroph]

Is it still that the statusbar shows the correct file but the IP does not?

i can't remember right now.
i'll have to wait 'till the bug appears again to test it...

[Muroph]

Is it still that the statusbar shows the correct file but the IP does not?

OK, here's what happens:
the file shown in the status bar's 3rd field is the same as the one in the IP (i.e. it's the wrong file).
but the file size, in the 2nd field, is always correct.

[admin]

Is it still that the statusbar shows the correct file but the IP does not?

OK, here's what happens:
the file shown in the status bar's 3rd field is the same as the one in the IP (i.e. it's the wrong file).
but the file size, in the 2nd field, is always correct.

Ok, next version there's little debug log when the properties tab is not updated. When the bug appears please pass this through the address bar:

Code: Select all

text <get debuglog>;

Then you will see something like this:

Code: Select all

13:05:52.436 >> 
  New File: E:\VB-Don\TestFiles\Media\Audio\Bomb.ogg
  Cur File: E:\VB-Don\TestFiles\Media\Audio\Brandenburg_Concerto_no._1_in_F_major_minus_one.ogg
  fBPL: Falsch
  fSel: Wahr

Post it here. It might contain the path to the light.

Please try to get the bug quick because I have to remove the debug log part tomorrow morning!

[Muroph]

Post it here. It might contain the path to the light.

Please try to get the bug quick because I have to remove the debug log part tomorrow morning!

OK, but this bug is really unpredictable.
i can't make any promises.

also, i have a trip planned for tomorrow, and then i'll be away from my pc 'till the 26th.

[admin]

Post it here. It might contain the path to the light.

Please try to get the bug quick because I have to remove the debug log part tomorrow morning!

OK, but this bug is really unpredictable.
i can't make any promises.

also, i have a trip planned for tomorrow, and then i'll be away from my pc 'till the 26th.

No, problem, then we do it when you are back.

[Muroph]

No, problem, then we do it when you are back.

yeah, that might be the best thing to do.

BTW, i'll be using 2 other PCs during that time.
i'll let you know if i see the bug on them.

[TheQwerty]

Think I had this happen again yesterday while using v9.70.0038 on XP SP3.
I treated it like a new bug though and tried to pinpoint its origin (looked like v9.70.0003 at the time), only to discover v9.70.0000 was working properly.

Then today v9.70.0038 is working correctly again, which made me realize it's probably this bug rearing it's ugly head. Just odd that v9.70.0000 was working, as previously when I've seen this happen it remains broken in all new instances of XY until the system magically corrects itself...

[admin]

"this" happened again? What is this "this"?

[TheQwerty]

"this" happened again? What is this "this"?

Sorry, "this" being that for whatever reason the IP quits updating on focus changes made via keyboard, only to eventually start working again.

Previously, it seemed more global since once it happened in one copy of XY it happened to all other instances (fresh or not) regardless of version.

What's strange this time is when my normal install of XY gets into that state a fresh copy of v9.70.0000 updates correctly. However, the broken behavior is still present when trying a number of versions since and including v9.70.0003 at the same time that v9.70.0000 works.

[admin]

Well, I cannot repro it. But I will soon rewrite related code from the scratch and that will probably fix it.

[TheQwerty]

Well, I cannot repro it.

Unfortunately I cannot reproduce it either.. it just happens every now and again. It'd been so long since I noticed it that at first I thought it was related to the focus changes you made in v9.70.0003, but when it went away the next day I figured it was the same issue we (okay you and Muroph) were trying to hunt down here.

But I will soon rewrite related code from the scratch and that will probably fix it.

Well that's hopeful. Though I keep coming back to the thought that it seems system related, so not sure you'll be able to avoid it. Just wish we could figure out the cause or at least how to reproduce it at will.

[Muroph]

i think it's about time i bring this up again.
especially since it's happening in win7 as well.
yup, both my XP SP3 x86 and Win7 SP1 x64 have this problem.

for a while i had thougth that somehow my XP, heavily customized and filled with apps, was causing it.
but win7 is really fresh, with only a few apps installed.

any ideas/theories?

[admin]

Hm, I'm still waiting to see this here. No new ideas...