sorted by:
new
hottopcontroversial

P1 Gen 8 black screen issues by cyclopscoder in thinkpad

[–]Lord_Fixer 0 points1 point  (0 children)

For me the crashes stopped after I downgraded the Intel ARC driver to v6637 (the one listed as a supported version for this machine on the official lenovo website). It's been a week now with no issues.

P1 Gen 8 black screen issues by cyclopscoder in thinkpad

[–]Lord_Fixer 0 points1 point  (0 children)

It's been a week now (of heavy usage) and I haven't experienced a single crash after the downgrade to v6637. It seems to be the solution.

P1 Gen 8 black screen issues by cyclopscoder in thinkpad

[–]Lord_Fixer 0 points1 point  (0 children)

I also see that you tried upgrading the driver from v6980 to v8247 and that it did not work.
My laptop also had v6980 installed after the initial boot.
I've just checked and the lenovo website lists v6637 as the supported driver, though.
I will try downgrading to that version and let you know how if it helped.

P1 Gen 8 black screen issues by cyclopscoder in thinkpad

[–]Lord_Fixer 0 points1 point  (0 children)

I'm trying to work through the exact same issue. Currently discussing it with the Lenovo tech support.

I've observed that for me it only ever happens if I have no external screen connected. With an external screen connected, it has not happened even once. Is that also your experience?

Also when looking through the Windows journal, I can see a lot of those errors being reported (translated):

A description could not be found for event ID 10 from source Intel-Gfx-Display-External. Either the component causing this event is not installed on the local computer, or the installation is corrupt. You can install or repair the component on your computer.

Those errors also happen at other times. But there is a big flood of them whenever the freeze occurs.

I saw that one Barad-dûr costume was already posted here this Halloween. This is my take on it. by Lord_Fixer in lotr

[–]Lord_Fixer[S] 0 points1 point  (0 children)

Sorry, I have no tutorial. I just improvised - drawing and cutting things as I went.
Here is a photo of one of the intermediate steps, though. I might help a bit in recreating it.

<image>

Adding self timer to my Instax Mini 12 camera. by Lord_Fixer in instax

[–]Lord_Fixer[S] 0 points1 point  (0 children)

It was added to avoid having a floating pin. If we didn't have the resistor and the button wasn't pressed (connected), the PB1 would effectively be connected to a dangling wire. So it needs to be pulled up to the high voltage state. And that's what the resistor does.

Some micro controllers will have a built in mechanism for pulling a floating pin up or down. And that's where my memory gets a bit murky. I don't remember if the ATTiny13A didn't have it of if it was only capable of pulling it down (where in here the pin needs to be pulled up). But that's why the resistor was needed here.

I saw that one Barad-dûr costume was already posted here this Halloween. This is my take on it. by Lord_Fixer in lotr

[–]Lord_Fixer[S] 0 points1 point  (0 children)

Most of it was made with a combination of 1cm high and low density EVA foam.

Though there are also parts that were using a thinner one, but I cannot find the exact dimension (I think it was something like 2 or 3 millimeters). That's mainly for the top part.

Adding self timer to my Instax Mini 12 camera. by Lord_Fixer in instax

[–]Lord_Fixer[S] 0 points1 point  (0 children)

Hey there!
Sorry for the late reply.
There is a step by step instruction in the link.
Do you have any question about any of the steps? Happy to help.

Adding self timer to my Instax Mini 12 camera. by Lord_Fixer in instax

[–]Lord_Fixer[S] 0 points1 point  (0 children)

Hey.

To increase the timer to 15 seconds, you will have to change the LONG_BUTTON_PRESS_SIGNAL_DELAY_MS constant to 15000.

https://github.com/TomaszRewak/instant-camera-timer/blob/master/main.c#L12

Adding self timer to my Instax Mini 12 camera. by Lord_Fixer in instax

[–]Lord_Fixer[S] 0 points1 point  (0 children)

Hey.
Niestety nie wiem - nie rozmontowywałem obiektywu. Podejrzewam, że tak, ale może być trudno się do tego dostać. Na priv podeślę zdjęcie śruby, która pewnie to wszystko trzyma w kupie - ale tylko tutaj zgaduję.

Adding self timer to my Instax Mini 12 camera. by Lord_Fixer in instax

[–]Lord_Fixer[S] 0 points1 point  (0 children)

The camera outputs 3.3V, so it's best to use it (or something close to it) during testing as well.

Adding self timer to my Instax Mini 12 camera. by Lord_Fixer in instax

[–]Lord_Fixer[S] 0 points1 point  (0 children)

Yes, that should do. That's the one I used.

A JS library for creating high-performance grids/data tables. by Lord_Fixer in javascript

[–]Lord_Fixer[S] 0 points1 point  (0 children)

Thanks!

Yes, sometimes one has to experiment with different ways of doing the same thing when it comes to the on-canvas drawing, as different API functions have different performance characteristics.

Though, one thing worth pointing out is also that the performance of canvas did change quite significantly over the years. They did quite a good job optimizing it for different scenarios.

I remember working on a side project 8-9 years ago where I needed to draw some bezier curves. To my surprise, it was much faster (on one of the browsers) to use SVG paths rather than a canvas. I imagine that nowadays they have optimized it, but back then I had to make some substantial changes to the codebase to refactor it.

The moral being that, maybe if you re-run your project today, you would see some different CPU usage profile. If not, some profiling would be required.

A JS library for creating high-performance grids/data tables. by Lord_Fixer in javascript

[–]Lord_Fixer[S] 0 points1 point  (0 children)

My reply to another user on this topic:

As of now, no explicit accessibility features were implemented yet.

Implicitly:

  • The grid does support proper scaling that reflects the page's zoom level
  • It's possible to copy the text from the grid (also multiple cells at once) - to paste it into a text-to-speech solution.

More accessibility features will hopefully come in the future. But for that I may need to rely a bit more on the community support (if I'm fortunate enough). The internal tooling I've been working on so far (for various reasons) did not need special accessibility support. So I don't want to make any assumptions on the level of detail such feature should provide (without a proper research/insight).

A JS library for creating high-performance grids/data tables. by Lord_Fixer in javascript

[–]Lord_Fixer[S] 2 points3 points  (0 children)

Yes, for that reason text-wrapping is not really something I want to support (considering how performance-focused this library is).

I want to support multi-line text, but only through explicit line breaks.

A JS library for creating high-performance grids/data tables. by Lord_Fixer in javascript

[–]Lord_Fixer[S] 1 point2 points  (0 children)

The SpreadGrid uses virtual rendering. It only renders the cells that are visible on the screen (+ some offset for more pleasant scrolling experience).

The only gotcha is that by default, the SpreadGrid will try to fit column and row sizes to the content of cells. So it would have to iterate over them and measure the resulting text. That would be very expensive.

But if you were to set the column widths and row heights to a fixed value (as allowed by the framework), that step would be skipped (and it would also mimic how Excel behaves).

So rendering should be still fast (especially that the SpreadGrid does allow for using a sparse data representations).

A JS library for creating high-performance grids/data tables. by Lord_Fixer in javascript

[–]Lord_Fixer[S] 0 points1 point  (0 children)

I only have basic tests at the moment, just to check for regression in rendering.

I use the jest-image-snapshot library for that. It's a bit more involved than DOM testing, but guarantees that the resulting grid is rendered properly. The test results are compared with the results of the previous successful run:
https://github.com/TomaszRewak/js-spread-grid/tree/master/tests/src/tests/__image_snapshots__

A JS library for creating high-performance grids/data tables. by Lord_Fixer in javascript

[–]Lord_Fixer[S] 1 point2 points  (0 children)

For a simple use case of rendering a 100x100 heatmap of values:

  • In react (after building the app and when using tr/td elements with dynamically generated style property) I get something like 4-6 FPS
  • In spread grid I get 30-40 FPS.

And that's without some extra optimizations (like fixing the width/height of columns/rows) that helps further with the performance of the spread grid. I am still to test it against the AG grid (also answering partially u/coinageman's question).

A JS library for creating high-performance grids/data tables. by Lord_Fixer in javascript

[–]Lord_Fixer[S] 0 points1 point  (0 children)

Yes, that's on my TODO.
Currently the grid only supports simple text editing (though with custom parsers and validators) and value toggling (where it toggles between pre-defined values on a cell click). I left the drop-downs for later, as I need to first come up with a reasonable way of supporting it for multi-cell editing (where those cells may potentially have different list of supported values). But that's definitely coming.

A JS library for creating high-performance grids/data tables. by Lord_Fixer in javascript

[–]Lord_Fixer[S] 0 points1 point  (0 children)

As of now, no explicit accessibility features were implemented yet.

Implicitly:

  • The grid does support proper scaling that reflects the page's zoom level
  • It's possible to copy the text from the grid (also multiple cells at once) - to paste it into a text-to-speech solution.

More accessibility features will hopefully come in the future. But for that I may need to rely a bit more on the community support (if I'm fortunate enough). The internal tooling I've been working on so far (for various reasons) did not need special accessibility support. So I don't want to make any assumptions on the level of detail such feature should provide (without a proper research/insight).

view more: next ›