shunia

Results 30 comments of shunia

> None at all? Not even the C# layer trying to initialize itself? At the very least C# should have done something. Ah, of course. I mean there's no Sentry...

Possible solution here: https://github.com/netpyoung/unity.webp/pull/24

Oh, I forgot to organize `WebPDecoderWrapper.cs`. The `flip` option won't work, though i forgot the details: https://github.com/webmproject/libwebp/blob/be738c6d396fa5a272c1b209be4379a7532debfe/src/dec/buffer_dec.c#L153 And `Texture2DExt.LoadRGBAFromWebP` works just great and implemented well so I just used it.

Note that most of the commits of that surf repo is like 'rename xxx'/'update readme'/'fix typo'. In 5 days they did fantastic job on marketing by make a fancy readme,...

> What pops my head when I'm writing is 'Do they just copy-pasted some chrome/firefox extension code to make there own `official` extension?' Could be but didn't check it out...

Sorry for my bad description. What I was going to pointed out is actually the first lines in this file: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/react-router-dom/index.d.ts Which is: Libraries in the `React` world are all...

> Regarding problem 3, it seems like a common issue for UWP apps that clipboard occasionally stops working. Please try relaunching the app and see if it works. Also be...

果然是个老问题:https://github.com/Tencent/vConsole/issues/587 真巧咱俩最近都遇到了,我翻了一下源代码,应该是因为`log.model`里面的限流逻辑`window.requestAnimationFrame`的回调方法`_flushLogs`里面的代码导致的。 我的log是一个interval性质的,调用destroy之后,`log.model`的`unbind`方法没有正确的屏蔽掉限流逻辑,但是又把`Store`里的东西删了,导致限流回调触发后可能会去获取`Store`里面的内容,但是获取的代码没做空保护,从而触发报错了。 这个改动的方法很多,比如在`unbind`的时候清空`logQueue`,比如增加一个flag来阻止限流回调的运行同时阻止`addLog`的执行,比如在限流回调中获取`store`的时候加一个空保护。 做一个空保护是最简单的,但是从代码设计的角度来说也许不是最优的。

> > 果然是个老问题:#587 真巧咱俩最近都遇到了,我翻了一下源代码,应该是因为`log.model`里面的限流逻辑`window.requestAnimationFrame`的回调方法`_flushLogs`里面的代码导致的。 > > 我的log是一个interval性质的,调用destroy之后,`log.model`的`unbind`方法没有正确的屏蔽掉限流逻辑,但是又把`Store`里的东西删了,导致限流回调触发后可能会去获取`Store`里面的内容,但是获取的代码没做空保护,从而触发报错了。 > > 这个改动的方法很多,比如在`unbind`的时候清空`logQueue`,比如增加一个flag来阻止限流回调的运行同时阻止`addLog`的执行,比如在限流回调中获取`store`的时候加一个空保护。 > > 做一个空保护是最简单的,但是从代码设计的角度来说也许不是最优的。 更正一下触发的原因,并不是因为`interval性质的`log导致的,**而是在destroy之前打一条log就可以必现这个报错**。

同上,应该是下载的源站挂了,不知道有没有修复的可能。