It is not possible to bring up the completion menu or manually add code outside of functions. Only new lines can be added outside of functions. Macros, constants, variables, new functions, etc, does not work.

Tested on Linux.

Works with Java:

See below that the checker didn't complain (neither in Java nor in C)

It is currently not possible to refer from one feature block to another:

Adding an else if statement to a module jumbles the code in the colored annotative view, universal view,and colored product view. This is not an issue in the the ifdef or product views, and it does not appear to affect code generation.

Colored annotative view:

Ifdef view:

Universal view:

Colored product view:

When creating an alternative return type the editor breaks.

Adding an if-statement, while-loop, or for-loop in the modular view results in a broken body. It is not possible to add statements to the body in the modular view. It is possible to switch to the annotative view, add a statement (for example an empty line), and then switch back to the modular view where everything now works as intended.

Two if-statements, one fixed in the annotative view and one unaltered, added in the modular view:

Opening the completion menu in the modular view:

Or, while, and for all work the same in the modular view.

Tested on Linux.

In the ifdef view, alternatives look like alternatives (i.e. ifdef, elif, endif):

In the colored annotative view, the same appears to be separate feature annotations:

The modular view simply omits the feature not selected, instead of replacing it with the selected feature:

Error message for function call where there appears to be 3 arguments rather than one alternative argument and one non-alternative:

Yet, the two are alternative to each other:

Instantiating a class in a static method and calling instance methods via that object from another module than it was instantiated in results in a "reference is out of search scope" error message.

Method calls to other classes, and method calls within the same block, are fine:

Workaround: an undo seems to resolve the issue?!

After deleting a misplaced VP that came to be because of issue #10, any code added to where that VP was will not be added to a feature block.

Here, the VP was added below the if statement, and then removed. The second if statement and the first push()-call is not surrounded by a feature block. The area where one can "write code" outside of a feature block can be expanded by hitting enter a few time where the misplaced VP was.

Here, the VP was added above the switch statement. After removing it, the if statement was added without being automatically added to a new feature block.

EDIT: Tested on Windows & Linux. Same issue in C and Java.

Replacing a node annotated with an nonOptionalAlternative results in deletion of the annotation (e.g., replace the return type).
To reproduce:
i) create an alternative return type
ii) change the original return type we created an alternative for
=> all annotations are accidentally removed

In the Colored Annotative view, the following Intentions are available:

When switching to other projections, the Split Block intention is missing:

Tested on Windows & Linux.

When you click unassign while the caret is placed in the module name, the statement is removed.

Nothing happens when pressing enter within a function body, making it impossible to add new lines of code.

Tested on Linux.

The PEoPL-related icons are entirely missing/replaced with standard icons when using the plugins. This is true for creating new solutions:

As well as for within existing PEoPL solutions:

Tested on Windows & Linux.

The fallback editor is used for the body of foreach statements in the modular view. It is possible to add statements, but the rendering is broken even with added statements.

Empty foreach:

Foreach with statements:

Tested on Linux.

E.g. ifdef view:

Universal view:

Same issue on both Linux & Windows

Trying to assign a piece of code in a switch/case statement to a feature moves that feature from the switch statement to above the switch. This is also true for creating new variation points within a switch statements.

This issue is present in both C and Java.

C:
1.

Java:
1.

Tested in Windows & Linux.

EDIT: The same thing issue exists with if statements.

Using the universal editor is quite cumbersome. Thus, the annotative editor should be activated by default.

Switching to the modular view when the implementation module belongs to a feature breaks the modular view. The projection is completely blank, and it is not possible to switch back to the annotative view using keyboard shortcuts.

Annotative:

Modular:

Tested on Linux.