- Nov 18, 2021
-
-
Loïc Correnson authored
-
Loïc Correnson authored
-
Loïc Correnson authored
-
Loïc Correnson authored
-
Loïc Correnson authored
Diagonal simplification is far too incomplete
-
Loïc Correnson authored
-
Loïc Correnson authored
-
- Nov 08, 2021
-
-
Allan Blanchard authored
Remove legacy WP engine See merge request frama-c/frama-c!3438
-
- Nov 05, 2021
-
-
Allan Blanchard authored
-
Allan Blanchard authored
-
Allan Blanchard authored
-
David Bühler authored
[ivette] Better visualization of the selected expressions See merge request frama-c/frama-c!3413
-
David Bühler authored
-
David Bühler authored
-
David Bühler authored
When the layout changes, the model fires the 'laidout' event. The number of rows may have changed (when callstacks are shown or hidden, for instance), and the values panel must be updated accordingly.
-
Allan Blanchard authored
-
David Bühler authored
-
David Bühler authored
-
David Bühler authored
-
David Bühler authored
-
David Bühler authored
-
It is a minor detail
-
The bug was that a clic on the by callstack button would not display the values of all callstacks, instead showing only the consolidated one and a unique callstack. A second clic was necessary to perform the request, update the caches and finally display the complete data. The fix we use here is quite brutal: we invalidate the values cache in the model. I would like to find a cleaner way.
-
David Bühler authored
-
The Valuecomponent had lots of weird bugs, triggering the warning <Can't perform a React state update on an unmounted component>. This was caused by an ugly, full of unsafe effect, way to handle the Model used by a lot of components used by the ValueComponent Now, the Model is created only once by the ValueComponent itself, and given as a property to every component that needs it. As a consequence, the useModel() function is now useless.
-
-
-
-
-
- Nov 04, 2021
-
-
Virgile Prevosto authored
-
Virgile Prevosto authored
-
Maxime Jacquemin authored
[ivette] Messages panel: show complete message in a bottom foldable panel. See merge request frama-c/frama-c!3433
-
Maxime Jacquemin authored
-
Maxime Jacquemin authored
The warning was: Cannot update a component from inside the function body of a different component It happened because a call to the model's method <setOrderingByFields> was done at each rendering, which somehow was a bad idea. Now it is done during the model's creation, and everything's fine.
-
-
The bottom panel is not shown by default: it appears at a click on a table row, and can then be closed. In the table, clips too long messages with an ellipsis '…'. Increases the size of columns for the category and the function.
-
Virgile Prevosto authored
-
Virgile Prevosto authored
-
Virgile Prevosto authored
-
Virgile Prevosto authored
-