Lieber Besucher, herzlich willkommen bei: krpano.com Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.
please, check out the link - https://look360.kr/vr/indyspot/indyspot_member/2521
I hope the link will work on your country as well.
press 'o' key will show the log.
Here is a video sample with closed Chrome dev tools : https://www.dropbox.com/sh/dq9jntg58uo9z…tpIn4lxPma?dl=0
But normally such bug should be reported to the browser developer and fixed there...
It's a Windows 10 (Fall Creators version) bug.
According to the bug report that problem should be fixed with Chrome 64.
I've also an override for the style of the log on the website : it's white on almost white !!please, check out the link - https://look360.kr/vr/indyspot/indyspot_member/2521
I hope the link will work on your country as well.
press 'o' key will show the log.
Yes, this is a css override in https://look360.kr/assets/bootstrap/3.3.…otstrap.min.css
pre {
display: block;
padding: 9.5px;
margin: 0 0 10px;
font-size: 13px;
line-height: 1.42857143;
color: #333;
word-break: break-all;
word-wrap: break-word;
background-color: #f5f5f5;
border: 1px solid #ccc;
border-radius: 4px;
}
unfortunately, i don't know which of my style file (.css, .less or other?) causes this problem
merci Jérome pour ce début de piste ;) [en même temps, c'est un problème bien mineur]unfortunately, i don't know which of my style file (.css, .less or other?) causes this problem
http://photo.maelbathfield.net/wp-conten…?ver=1516348878
please, check out the link - https://look360.kr/vr/indyspot/indyspot_member/2521
|
|
Quellcode |
1 2 3 4 5 |
<action name=my_local_action scope=local arg="hs, direction" >
if(hs,
set(hs.alpha,0.5);
...
</action>
|
Right, thanks for noting - the tween animation system is currently not 'multi-scope-able'. That means when internally registering a tween animation, it doesn't check if the variable might be from a local scope. The animation itself should be working correctly, but tweens with SAME-NAMED variables from other scopes would be wrongly stopped.The contextmenu "Next only" is tweening both clowns. This is not working in the case when the scope=local.
|
|
Quellcode |
1 2 3 4 |
calc(myid, 'id_' + timertick + '_' + random); delayedcall(get(myid), ...); ... stopdelayedcall(get(myid)); |
Yes, that's valid and intended.BTW I found that only the action scope=local is passing as an argument the reference to the object
...
Is this construction valid and will work in the next releases, too?
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »Birdseye« (9. Februar 2018, 05:21)
Please, can you give us some more insides how to use scope=private:NAME ?
I tried to learn from the showtext.xml plugin, but no success. How to reference the variables in this case?
The check happens only once per frame, so it should be not very heavy.I found the callwhen() function as a very powerful instrument. But before using it more I'd like to learn about.
- how heavy the function is (resource consuming, limitations,...)?
The function runs until the condition is met. When the condition is already true, it acts like a normal if() check.- what is the lifespan of the function? (Until the condition is met or is there some 'garbage collection'?)
There is currently no API for canceling or defining an id (but I will consider one).- how can I cancel obsolete callwhen() when I need to start "my new era"?
- is/will be there a way to control a callwhen() selectively like delayedcall(id, ...);
No, but good idea - I will look if that could be exposed somewhere for debugging.- is there a queue where I can see (debug) callwhen functions pending for execution?
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »pur« (12. Februar 2018, 18:23)