User story

As a user, I want to manage enumerations, in order to set predefined data in my behaviour.

Conditions of satisfaction

Technical remarks

• The declaration view must add a new button to declare enums
• A new model for enumerations must be provided
• The property panel must provide literal management
• The property panel must provide storage type assignment

Node Input/Output are now created by type, with a specific color we can access from the settings

Add a highlight on selected entity

Add min and max size for the left and right panel

Parameters order isn't correctly saved.

The font awesome font are not displayed properly

Model is not correctly update in the treeview when a new item is created, this cause a segfaulft on the binding.

Menu

Sous menu

• grossir la font
• mettre plus de padding

View Menu

• toogle => toggle
• mettre une icône pour dire si c'est activé pour les toggles

Le feedback traduisant que le projet est bien save est cassé quand on open le projet

User story

As a user, I want to manage the parameters/returns of a function, in order to create custom behaviours.

Conditions of satisfaction

Technical remarks

• When clicking to the function, the NodeCanvas is open and not the DeclarationView
• Must provide parameters/returns managment into the property panel
• When a parameter/return is added or removed from a function, all the CallFunction instructions must be updated

Description

The program crash when we close contexts in treeview

Reproduce

• Open the test.dnaisolution file
• Expand the following contexts in treeview: Test A*, context1, context1.1, class1.1
• Reduce the contexts that you've open
• Reopen Test A* context

We can use them to display some additional information when we hover the element

Problem

The instructions can be linked but, when we undo the action, the interface is not correctly refreshed

Start of solution

We have to connect the InstructionHandler::dataLinked/dataUnlinked/executionLinked/executionUnlinked signals in the nodecanvas and call views::GenericNode::createLink.

Description

In the declaration process, I found (or maybe create) a bug that invalidate the tree view.

When you declare an entity without expanding any context, the tree view add an empty field at the end.

Reproduce the bug

First of all, you'll need to open the project test.dnaisolution.

Then, open the declaration view of the context context1

Declare a new Context (green button) in the openned context.

As you can see, a new blank line have been added to the tree-view.

The bug only occurs on if you didn't expand any context yet.

If you tries to expand the context1 in the tree view.

And try to redeclare another Context.

As you can see, no blank items have been added to the tree view.

Even if we close the context1 from the tree view, the problem is not here.

When creating a project, the root entity is not set.

This problem make impossible to build a project.

If I load the test.dnaisolution and I click to open the class1 entity, I have the following message qrc:/resources/Views/DeclarationView.qml:176: TypeError: Cannot read property 'entityType' of null

It points to the following lines into the file resources/Views/DeclarationView.qml at the following line

AddButton {
    id: _addContext
    width: 45
    visible: modelData.parentRef.entityType === 0
    onPressed: {
        console.log(idx)
        console.log(modelData.listIndex)

        var name = proj.generateUniqueChildName(modelData.parentRef);

        proj.addEntityColumnUid(modelData.parentRef.id, name, modelData.listIndex)
        Controller.declarator.declare(modelData.parentRef.id, 0, name)
    }
}

The problem is in the line visible: modelData.parentRef.entityType === 0 where it says that modelData.parentRef is null.

If we look into the class Column, the function used to get the property modelData is the following one.

Entity* Column::parentRef() const
{
    if (m_entities.empty())
        return nullptr;
    return m_entities.first()->parentItem();
}

In the case where the column have no entities declared, the parentRef is null and can't be accessed in the QML. Indeed, the class1 entity have no children declared in it.

This issue is problematic because we use the modelData.id to declare an entity.

Description

1. Open a dnai project
2. Then clic on a variable
3. Set the variable type to boolean
4. Save the project
5. Exit dnai editor
6. Open the save project
7. Select the same variable
8. Set variable type to integer
9. Save project
10. Exit dnai editor
11. Open the save project
12. clic on the same variable
13. The Integer variable is set as a string "true" or "false" instead of 0

Les menus d'ajout (de contexte / classe / variable / fonction) sont mal affiché

User Story

As a user, I want to edit variable attributes, in order to have a consistent behaviour environment.

Conditions of satisfaction

Technical remarks

• The QML view must call the right core controller method.
• The core controller must emit a signal at the end of its action.
• The signal must be catched by an object in order to edit the interface.
• The property panel must be used to this feature.

Description

Each core command can fail.
We need to remove a core command that has failed from the CommandManager.
You can remove a core command from the CommandManager with its adress.
We can detect that a command has failed by the network communication between DNAI editor and the CoreDaemon.
We need a way to find the core command adresse that has failed in order to remove it.

Conditions of satisfaction

When you have finished this task, i can start to fix the Travis Build :)

User story

As a user, I want to add instructions into a function, in order to create my own behaviour.

Conditions of satisfaction

Technical remarks

• Big issue in the editor
• The instruction instanciation must be provided by the core controller
• The interface would only have to call controller method
• An easy way to handle the system is to provide an any type from Core that is set into the GUI
• The instruction to call a function must be created with the right input/output
• Others instructions like operators are instanciated with any type
• Instructions like getters/setters must be correctly handled

Settings pop-up that asks the theme to set into the GUI now always open when we launch the editor.

The pop-up is not very beautiful and moreover, if I choose the light theme, there is no significant changes that appears in GUI.

Instead of sending time to fix this, better disable the pop-up and choose the dark theme by default.

Conditions

To reproduce the bug :

• Open the file test.dnaisolution
• Click on a certain number of context/class (generally between 5 and 10)
• Select the 2nd project
• Leave the application by pressing the top right cross button
• You'll notice the following message in Qt after few seconds : The process was ended forcefully.
  D:\EIP\Duly-GUI\build-DNAI-Desktop_Qt_5_10_1_MSVC2017_64bit-Release\app\release\DNAI.exe crashed.

Description

We can load .dnaiproject in the editor.
Once a project is loaded, it's vital to replicate it in the CoreDaemon in order to manipulates the AI.
Then we need mecanism that calls the right core commands to correctly replicate the entities.

Conditions of satisfaction

By default call CoreCommand with False instead of True, this should be resolve the bug

Move column is to high add a margin on it

Description

Each core command can fail.
We can detect that a core command has failed by the network communication between the DNAI editor and the CoreDaemon.
When a command fail, we need to provide a system that removes it from the CommandManager in order to prevent the undo and redo to use them.

Condition of satifsaction :

Rendre toute la zone clickable (voir image)
Aujourd'hui comme ça :

Je pense que c'est plus intuitif si la partie clicable est :

A discuter

Change the column title style (for now it's editable text)

Add dialog to confirm suppression operation or warning closing without saving for exemple

Update contextMenu evenIf the view is already open but not active