Dipscom last won the day on January 12

Dipscom had the most liked content!

Dipscom

Moderators
  • Content count

    951
  • Joined

  • Last visited

  • Days Won

    31

Dipscom last won the day on January 12

Dipscom had the most liked content!

Community Reputation

1,458 Superhero

About Dipscom

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    London

Recent Profile Visitors

6,175 profile views
  1. If I were in your position - I'd not minify the whole code. If everything is breaking on that stage, leave it out. I don't think anyone using IE10 will notice a dip on performance if you don't minify the deployment code. To me, and take my word as an opinion - not a rule or guidance, that would be the solution. And, good luck! I've been on that position of having to support unsupported browsers. Not a fun place to be.
  2. Timeline - call/pause/resume

    No brownies for you @PointC.
  3. Oh yes, that's one tall order. And I'd second @Carl's suggestion - particles and probably some blending. If/When @OSUblake shows up, he'll: show something he's made just after brushing his teeth before going to bed that fits your needs using PIXI or just RAW mental power, blow us away, melt a couple brains, Feel slightly surprised that one/few of us are shocked he didn't even break a sweat. So, start sinking your teeth into PIXI so that when the above happens you've already mastered the basics.
  4. I have. Although I won't be able to tell you exactly how to fix. From what you are describing, your minification is mangling the code in a manner that IE can't parse it. As @Jonathan once taught me, IE is very strict when parsing and while some other browser will read a mangled bit of code and still make some sense of it, IE will simply consider that invalid code and will ignore it. Do use the opportunity to flag to your client that they're using out of date browsers who will not have security patches applied to them and are more vulnerable to malicious attacks.
  5. Queueing .ticker callbacks before visual updates?

    I should have read your post a bit more slowly... I just realised I misread your first sentence as: "I'm looking for..." rather than "I'm looking at...". Apologies for that. I personally am can't say for sure but, my understanding of the way requestAnimationFrame and GSAP works is that, the ticker will dispatch its events after everything is computed and then, the rendering occurs. The browser is the one scheduling the draws, GSAP only updates whatever numbers its working with. But, don't listen to me. I can't even read correctly... Mr. @GreenSock or @Carl should be able to give you a more definitive answer.
  6. Queueing .ticker callbacks before visual updates?

    Hey @lunelson@gmail.com, Here's the .ticker documentation: https://greensock.com/docs/TweenLite/static.ticker There's a section there talking about the priority parameter, see if that's what you are after. Happy Tweening!
  7. I went to the shops yesterday after seeing the above comment. No brownies in the shop. Pedro went to bed very, very, very sad.
  8. Using scope -solved

    Damn semicolons; we should burn them all at the stake.
  9. Using scope -solved

    I 'a' is an already bound function, I see no reason why it wouldn't work. I have in the past had to create a variable to hold the binding before adding to an event listerner, for example, in order to preserve the bind when accessing it from another place. It could be that you might have to do something similar. // Sorry if this isn't too clear, trying to remember without going after some sample code var a = function() {} var b = a.bind(c) var obj { d: b } timeline.add(obj.d)
  10. Right. The gif you uploaded made a world of difference. I have my CodePen in a different layout than yours (with the code on the left, rather than on top) and copying your layout enabled me to replicate the error you are reporting. I have never used SVG.js (although I do a fair bit of SVG myself) so, I haven't got much insight, you will have to help me to help you. The issue stems from the fact that you are modifying the width of the 'line' based on the 'x' of your 'point_dr'. At some point, for some reason, one manages to drive that number into the negative, which causes SVG.js to throw an error. I don't feel you have the best setup by changing the width but it appears to me that you can stop the SVG.js error by simply doing a Math.abs() before you assign it to the 'x'. var x = Math.abs(point_dr.x); Since you're using draggable, you will have access to a lot of information if you look into the 'this' object inside your mySlider() - In your case 'this' will be the actual Draggable object, it probably will be safer to track how much the mouse has moved (deltaX), subtract that from the width of your line making sure that if you get a number that's less than zero to make the end value equals to zero. Something along the lines of: var x = line.width() - this.deltaX; if(x <= 0) { x = 0 } Hope that helps! ps: Shooooo @Carl! I'm trying to earn some brownie points here! Don't steal my thunder...
  11. Using scope -solved

    Jumping on the bandwagon! If the mighty @GreenSock is confused, what do you think will happen to us mortals? Brain melts and generalised panic. On a side note, you can bind scope and add in a timeline... As the man himself has said, a simple pen showcasing your issue will greatly help.
  12. Hi @21cm, Welcome to the forums! I can't replicate your error. Maybe if you set the edgeResistance to 1 will stop it from happening?
  13. Hi @RenHe, Welcome to the forums! The link you have in the GIF url is pointing back to this post, I had to copy and paste it to be able to see what you are referring to. I am a bit lost here on what help you are looking for. What do you mean when you say 'unsure how to approach the special effect'. Have you got a mock of what you are trying to achieve? We will be more than happy to help as much as possible.
  14. Good idea for practice

    What works for me is to hound forums and look at what issues people are having and try to answer them. You don't have to post an answer or it doesn't even matter if it has been answered by someone else if all you want is a challenge. Just look at the problem, try and solve it. If someone else answers it, you can always check their reply and compare your approach with theirs. I recently replied to a question here that really fits the bill - It made me feel really proud of the solution I came up with and felt I learnt something as well. It also spawned another idea I would like to try in the future (maybe will never see the light of the day given my current ideas-wish-list but, hey, it's there). Another thing I would recommend is to read the docs. Do it a dozen times. I didn't get any of it to begin with but the more you read, the more it makes sense. A lot of the cool things a lot of people do is nothing more than an exploration of some basic functionality in a novel way.
  15. strange behavior in Safari (only) - drawSVG

    Hello, hello! That is indeed a very strange behaviour. I can see what you are describing and probably @GreenSock is the individual that will be able to tell you why exactly this is happening and if there's anything he can do about it. I can only have a guess based on inspecting the element and what I know of SVG behaviour. Basically, everything is doing what is supposed to do, in my eyes. The catch is how stroke-dashoffset and stroke-dasharray work together with the length of the line you're working with. I will assume you know the theory behind animating a stroke in SVG (if you don't, let me know and I'll dig something out from the interwebs). All is working wonderfully until you rotate the line - as soon as you do that, it looks like the line is no longer the same length and Safari is not having a good time working out where the visible bits of the stroke should be. When inspecting the line, you will see that it is in the right place and the correct length but, the stroke-dashoffset is not quite where it should. Possibly a Safari bug... Possibly something @GreenSock can fix with his magic. Possibly, that's something you need to take in consideration when creating your SVGs... I've amended my pen to just rotate one of the lines, so you can compare them. PS: As for the selector engine - The difference will probably be negligible unless you are selecting thousands of elements - even then, it's probably not worth fretting over it. I never use jQuery myself - don't really need it - so I default to GSAP's selector. Less code to write.