These are chat archives for highfidelity/hifi

1st
Jul 2014
AlericInglewood
@AlericInglewood
Jul 01 2014 00:10
$%@$$% rpath
Sean Devin
@SeanDevin
Jul 01 2014 00:12
That level of bash substitution probably won't work @AlericInglewood
AlericInglewood
@AlericInglewood
Jul 01 2014 00:12
Hmm, though it makes a little sense for C++ I guess... hmm.
Basically - I think what the problem is @Atlante45 - I changed Qt5's ABI with my debug code, and there is another library (libqxmpp) that also links with Qt5 libs. libqxmpp is the one that creates a QSslSocket - that's where things go wrong.
AlericInglewood
@AlericInglewood
Jul 01 2014 00:19
Ok, that's the only lib that uses Qt. Will have to recompile that too... but first sleep now.
Sam Gateau
@samcake
Jul 01 2014 00:22
Hi,
Clément Brisset
@Atlante45
Jul 01 2014 00:23
Hey @samcake
Sam Gateau
@samcake
Jul 01 2014 00:24
Is there a way to reset the age of a Particle from Javascript ?
It seems that reapplying the ParticleProperties to the same ParticleID cheange the position and other parameter but not the age
Any IDea ?
Clément Brisset
@Atlante45
Jul 01 2014 00:25
Gotta check on that
Sam Gateau
@samcake
Jul 01 2014 00:26
There is no age property exposed,
maybe that would be useful ?
in my case it's to show joints position, i create a particle at the current position and give it a 1second lifetime
then when the joint's change, i create a new Particle and so on
What i really want is to reset the Particle if it already exist at full time and update the position, but not necessarly create a new one
Clément Brisset
@Atlante45
Jul 01 2014 00:28
Ok
The age is computed using the difference between the time it was created and the current time.
I think It’d be better to have a way to reset it instead.
Sam Gateau
@samcake
Jul 01 2014 02:30
it works too, sounds good
AlericInglewood
@AlericInglewood
Jul 01 2014 12:05
[2014-07-01T14:04:26] Calling receiver->event(e); e->t = 51
[2014-07-01T14:04:26] Calling receiver->event(e); e->t = 51
[2014-07-01T14:04:26] Calling receiver->event(e); e->t = QEvent::KeyPress
[2014-07-01T14:04:26] Application::keyPressEvent(1000023)
[2014-07-01T14:04:27] Calling receiver->event(e); e->t = 23
[2014-07-01T14:04:27] Calling receiver->event(e); e->t = 9
[2014-07-01T14:04:30] Calling receiver->event(e); e->t = 8
[2014-07-01T14:04:30] Calling receiver->event(e); e->t = 207
[2014-07-01T14:04:30] Calling receiver->event(e); e->t = QEvent::KeyRelease
[2014-07-01T14:04:30] Calling receiver->event(e); e->t = 77
[2014-07-01T14:04:30] Calling receiver->event(e); e->t = 12
AlericInglewood
@AlericInglewood
Jul 01 2014 12:40
It seems that the menu bar steals the keyboard focus upon an ALT-key release, causing the application not to see when that ALT-key is released even the user is NOT using a menu bar shortcut :/
imho, this focus stealing (from the canvas) is undesirable, no?
AlericInglewood
@AlericInglewood
Jul 01 2014 12:48
QStyle::SH_MenuBar_AltKeyNavigation 18 Menu bars items are navigable by pressing Alt, followed by using the arrow keys to select the desired item.
We should turn that off :/
AlericInglewood
@AlericInglewood
Jul 01 2014 16:10
I created a job for the above... I ran into this because I want to write a script that makes controlling my avatar more like it is in SL.
https://worklist.net/19830
omg - /opt is in my / partition??? No wonder that my harddisk ran full :/
No it isn't... stupid k4dirstat... Apparently /tmp is in the root though, wtf...
AlericInglewood
@AlericInglewood
Jul 01 2014 16:15
Ah, I set my konsole scrollback history to unlimited... and THEN I started to compile Qt5. Now I have a 1.5 GB file of scroll back :P
AlericInglewood
@AlericInglewood
Jul 01 2014 22:43
I get a new assert, due to a recent commit: [2014-07-02T00:34:00] ASSERT: "alloc >= 0 && extra >= 0" in file tools/qbytearray.cpp, line 72
Clément Brisset
@Atlante45
Jul 01 2014 22:43
Stacktrace?
Or log maybe?
AlericInglewood
@AlericInglewood
Jul 01 2014 22:44
I'm first going to do a bisect to find the commit :\
Clément Brisset
@Atlante45
Jul 01 2014 22:44
Oh, it crashes on launch?
AlericInglewood
@AlericInglewood
Jul 01 2014 22:44
yes
AlericInglewood
@AlericInglewood
Jul 01 2014 23:06
Grr, this bisect is near impossible because of an essential fix that still wasn't merged... now I have to constantly merge with a branch of me before I can even check if a commit is good or bad - and git doesn't like that.
AlericInglewood
@AlericInglewood
Jul 01 2014 23:47
@Atlante45 The crash is caused by a commit by Andrzej Kapolka drzej.k@gmail.com .. causing corruption in reading from a stream, resulting in trying to allocate a string of 1.3 GB.