gorgon | A simple multiplier process analysis tool in Python

The byte order of the target is, in memory, R G B A. The byte order of the source is, in memory, B G R. So in addition to expanding every 3 bytes to 4 bytes and putting FF in the new A channel, the R and B channel need to swap position. For example,

Such skewing with wrapping is typically a stride vs width problem. You can use the direction of the skew (in combination with the row order, usually top down but not always) to see whether it's a problem in the source address calculations or the destination address calculations. Here the skew is angled "backwards", meaning the src address is advancing too slowly and as a result pixels end up further and further to the right and downward compared to where they should be. In principle the same effect could be caused by the destination address advancing too quickly, but that is less likely (a stride vs width problem wouldn't do that, using the wrong stride might)

So it would be position that is wrong, and (y * info.Width + x) * 4 uses a width instead of a stride which is suspicious.

The source stride is map.Pitch so position should be y * map.Pitch + 4 * x

You are depending on several libraries that haven't been updated for Dart 2. Unfortunately the only solution would be to remove these dependencies or move back to a Dart 1 SDK. For reference:

• browser_detect: v 1.0.4 • Updated: Mar 2, 2016
• gorgon v 0.14.2 • Updated: Dec 6, 2014
• jsonx v 2.0.2 • Updated: May 19, 2016
• slack 1.2.2 • Updated: Jun 6, 2015 WEB

In general, only libraries which were last updated sometime in 2018 will work in Dart 2, and usually only the very latest version. You can check the status of your dependencies by searching for the package name on pub.dartlang.org

Edit: gorgon in particular has a dependency on an older version of async, I would start by removing that

You need to return the value, not print it. Like so:

You can simply use text-align: justify; to spread the words over the whole line due to increasing existing spaces.

Seems to be due to the fact that you never close your initial while loop: while i < 1. Since the value of i stays at 0, your outermost while loop will never close, causing your program to be stuck in an infinite loop. If you close that loop by setting i = 1 at the end, this particular problem should be resolved.

It's because the string you're injecting from $tablica_artefakty contains quotes. This causes your HTML be improperly rendered - attribute is prematurely closed by the quote from your string. You should escape the quotes in your $tablica_artefakty so that they don't close the HTLM attributes in wrong places.

Why aren't you just doing this?

Having examined things here I now understand what happened (to a degree).

In fact the dataFields Array was obtained from the result of an AJAX call which loaded (or more accurately returned, as the data param in the callback function) an HTML fragment, containing several page elements with class .dataField, which I then gathered by going data.find( '.dataField' ).

But in fact these "page elements", despite having hundreds of properties, just like objects directly "mapping" to page elements, were indeed "phantom" objects: specifically, properties such as clientHeight were 0, seemingly an indication that this is a non-visible object.

It was only when the HTML returned in the AJAX callback was inserted into the document structure (and made visible by setting hidden to false for the encompassing DIV) that this HTML generated real page elements. I then had to select these page elements with class .dataField to get hold of the non-phantom objects (having clientHeight 20 or whatever).

Quite strange, as these initial "phantom" objects did NOT become "real" objects as a consequence of the HTML being added to the document. They remained ... useless (and confusing!).