felt | On-demand bundler for ES6 / CSS Next

The issue is that the ??= operator assigns to the left if it is null. Expanded, it would look something like this:

For problem One, you don't need to create headers outside of a the table itself -- you can just add another TableRow. Additionally, a TableCell accepts the property colspan which allows you to define the number of columns you would like each cell to occupy.

I have absolutely no idea what frequency has to do with this and you don't appear to need it given that it's simple to get the next date to use as a join test

You need to ask yourself a question : Why should B not be copyable?

The example you described, with a graph owning one (or probably multiple) vertexes shows the opposite : B should be copyable! What you don't want is two graphs sharing the same vertex instance.

So you can create a copy constructor / clone method for V along those lines :

I believe that such kind of "inversion" of a type family is impossible in current GHC, at least without unsafe functions.

Even with unsafe functions, I don't know if it is safe to add it. Kinds are weird beasts, and often contain more terms than one would expect. E.g. type family X :: Bool compiles, still we can not prove X ~ 'True nor X ~ 'False.

The code below does not fully answer the question, but I wanted to remark that, if we can add a few constraints to Foo so to carry a few singletons around, then we can write the wanted Eq instance.

The code below can probably be simplified further. Still, here it is. Below, I defined "conversion" functions fooT1, fooT2 to convince GHC that in Foo k and Foo j we do have k ~ j ~ 'True.

The current documentation in the openjfx tutorial for getting started with JavaFX using Idea is incorrect, at least for recent Idea releases (2021.3 +).

The tutorial is written as though a new Java project was created, rather than a new JavaFX project. Once a new JavaFX project has been created, most of the rest of the steps in the tutorial are either redundant or wrong.

Step 1, “Create a JavaFX project", does a lot more than just “Create a Java project”, which is why everything else is different from the tutorial.

A better tutorial for getting started with JavaFX with Idea, is the official Idea documentation:

• Create a new JavaFX project.

Differences between creating a new Java project and creating a new JavaFX project

The new JavaFX project:

1. Provides a build script for Maven (pom.xml) or Gradle (build.gradle).

2. Adds the appropriate dependencies for JavaFX base, graphics, controls and fxml.

3. Provides an example application and controller code that you can run immediately.

4. The example project is modular and provides a module-info.java

5. Because the program is modular and dependencies are downloaded via maven and recognized by the IDE, you don’t need to manually configure VM runtime options for the module path and adding modules.

6. Idea will recognize the Maven or Gradle projects and automatically synchronize the initial transitive dependent libraries with the Idea project.

7. There are options in the Idea Maven tool window which will allow you to synchronize further changes to dependent libraries or javadoc and source code in libraries.

8. Selects a JDK and attaches it to the project, automatically downloading the selected JDK version if not already present.

9. Sets an appropriate language level for the project.

When you just use the create new Java Project option, it doesn’t do any of those things, so you need to do things manually instead, which is what the rest of that tutorial is about:

1. Manually download the JDK and configure it in the SDK.

2. Manually download the JavaFX SDK and add the libraries from it to your project.

3. Manually configure VM modular arguments.

4. Manually maintain any other dependencies.

5. Manually associate javadoc and source code.

6. Manually write the code for a basic application.

7. Manually set the project language level.

Doing all this stuff manually is more work and more error prone. The manual work usually leads to a worse outcome and a project that is more difficult to maintain for many people getting started with JavaFX, so I do not recommend it.

Versions

In terms of the versions to use, I recommend using the most recent stable (non-beta) releases of both JDK and JavaFX, regardless of what versions may be referenced in any tutorials you may be using.

You can set JavaFX versions in the Maven file generated by the new JavaFX project wizard, then press the button in the Maven Tool window to synchronize the Maven project with the Idea project.

Language level settings

These are important later on, but pretty irrelevant when just getting started.

The language level settings:

1. Tell the compiler what version of the java byte code to compile the application to.

2. Tell the IDE what language syntax rules to enforce and provide help with.

If you use Java 17 only features, the app won’t run on a Java 11 VM.

You can define the settings in Idea manually:

• language setting level.

But it is better to set them in the compiler section of the maven project and synchronize the project with Idea, which will also configure the settings in the IDE.

IMO, set it to the most recent stable version and have a requirement that your application be run with that Java version as a minimum (you can enforce that by using jlink or jpackage to bundle the JRE version you choose with your packaged app).

Using g++ (Debian 11.2.0-10) 11.2.0 and GDB-10.0:

I found my fix. I'm still at a loss as to why the previous setup worked with "FILE" version but not the "AUTHOR", but this fix works for both. That being said, it does make sense to look at the getChildAt(0) position since that is always the button position and receives the setTag. Anyhow, here is the fix. I had to include the .getChildAt(0) on the tblRow then get the tag and check.

This