Hercules | Hercules is a source-code transformation tool

In order to move the cursor to a specified position, it's necessary to use the underlying QTextDocument using document().
Through findBlockByLineNumber you can construct a QTextCursor and use setTextCursor() to "apply" that cursor (including the actual caret position) to the plain text.

You imported the wrong Element class. Change

You could use a single pattern with 4 capturing groups.

Only when this constructor is done, the UI can show up, but it blocked by the endless while loop.You need to move the while loop to another place, a manual trigger function or a thread will be OK.

You do open two times, I guess second one should be isOpen

Inside Nix, you can't run npm install. Each step can only do one of two things:

• either compute a new store path without network access: a regular derivation
• or produce an output that satisfies a hardcoded hash using a sufficiently simple* process that can access the network: a fixed output derivation

These constraints ensure that the build is highly likely to be reproducible.

npm install needs access to the network in order to fetch its dependencies, which puts it in the fixed output derivation category. However, dockerTools.buildImage will execute it in a regular derivation, so it will fail to contact the npmjs repository.

For this reason, we generally can't map a Dockerfile directly to a series of buildImage calls. Instead, we can build the software with the Nix language infrastructures, like yarn2nix, node2nix or the various tools for other languages. By doing so, your build becomes reproducible, it tends to be more incremental and you don't have to worry about source files or intermediate files ending up in your container images.

I'd also recommend to limit the contents parameter to a pkgs.buildEnv or pkgs.symlinkJoin call, because the contents are copied to the root of the container while also remaining in its store.

*: sufficiently simple excludes anything beyond fetching a single resource, because that tends to be too fragile. If, for any reason, the fixed output derivation builder produces a different result and the only way to fix it is by changing the output hash, your entire build is essentially not reproducible.

The way to change the height only one of the card is to define the function individually. Here what I did:

• I convert the PageOne class into Statefull widget and CardDue class to Stateless widget.
• CardDue has two extra parameter in constructor, that takes a function and a bool variable.

why I did ?

having a separate bool variable for each CardDue class make sure only one of them is true. If its true, we simply set other two bool variable to false.

Here's the code:

When initializing an object at definition, it's not using assignment even when the = syntax is used.

When you do:

I think a lot of what you did, specifically around data wrangling, was not necessary, especially since you called d3.hierarchy() and d3.cluster() afterwards. I've replaced this with d3.stratify (which deals with hierarchical data that is not yet in the right format).

I've also replaced d3.cluster with d3.tree() because it was unclear to me why you'd want to use d3.cluster here. Your data has multiple parents, multiple roots and even floating nodes, and d3 is not meant to deal with that. My workaround has been to attach pseudonodes to every level, so as to make sure that there is only one node and that all nodes are at the right level at all times. To make sure the links were drawn correctly, I've written a custom getLinks function, that can deal with multiple parents.

I've also written a custom link generator that draws the links somewhat in the way that you want them. d3 doesn't offer much of flexibility here, but you can use the source code for inspiration.

Edit

I've changed the logic to be more focused on which "partners" got a child, so both links to the same child are on the same level - like in your picture. I've also drawn the nodes based on how many partners they have, and have given every link an offset so the lines are more distinct.

I've sorted the nodes so that the real pro-creators are at the top (Zeus), which gives a more balanced and less crowded view.