Recent changes to bugs

Overflow of description in tactic profile editor

2025-12-09T09:54:54.265000Z

In the tactic profile editor, if we select a tactic with a long description (for example Clarify goal) and if the window is relatively small (on a small screen or if we resize it), the description does not fit in its box and there is no scroll bar.
The text widget should be resized correctly instead of overflowing and should be scrollable.

#834 Impossible to type some datatype constructors

2025-05-12T16:44:33.637000Z

status: open --> closed-fixed

#833 Clarify error message on invalid input for fresh name generation

2025-03-12T12:47:40.023000Z

status: open --> closed-fixed

#835 Inconsistent handling of Proof Control's global input

2025-03-12T12:46:57.031000Z

status: open --> closed-fixed

#834 Impossible to type some datatype constructors

2025-03-02T12:23:57.831000Z

In retrospect, this issue does not seem to be limited to datatype value constructors only. It is current practice to also define operators that behave like value constructors, but contain some additional WD condition. We would then have the same issue with these operators (which are usually prefix). I think we can live with a restriction preventing the definition of infix operators with such a typing scheme.

#837 Display issues in new tactic profile dialog

2025-02-27T08:20:04.460000Z

status: open --> closed-fixed

#834 Impossible to type some datatype constructors

2025-02-21T14:34:02.849000Z

Discussing this topic with Nicolas Beauger (the author of the parser for the event-B mathematical language), we have considered a fourth option:

left⟦ℤ, BOOL⟧(1)

This is like option 3 but using different square brackets, namely

MATHEMATICAL LEFT WHITE SQUARE BRACKET (U+27E6)
MATHEMATICAL RIGHT WHITE SQUARE BRACKET (U+27E7)

We would then need to also extend the event-B keyboard plugin and the Symbol view for these new characters. Their respective shortcuts would be [| and |] which is not a valid sequence in the current mathematical language.

#834 Impossible to type some datatype constructors

2025-02-19T14:53:16.337000Z

I can see three options for making explicit the type parameters on such constructors:
- (left(1) ⦂ Either(ℤ, BOOL))
- (left ⦂ Either(ℤ, BOOL))(1) -leftℤ, BOOL`

The first two reuse the oftype notation. The drawback of the first proposal is that the type annotation is quite far from the constructor operator (the actual parameters can take quite some space).

The second proposal is a bit of an abuse, as the given type is not that of the constructor operator, but rather of its result. It is however consistent with the type annotations of parameterless constructors.

The third proposal uses a very different way of annotating with types. It was used years ago when designing generic operators, then dropped in favour of type inference. If this kind of annotation is restricted to operators (that are a distinct category of tokens), then there is no ambiguity introduced in the event-B grammar.

Display issues in new tactic profile dialog

2025-01-15T14:33:47.928000Z

The dialog used to create new combined tactic profiles is made of three parts displayed side-by-side. Users can drag-and-drop elements from the parts on the left and right to the one in the middle. Since the middle part is initially empty, it gets resized to a tiny white box that is only a few pixels wide. One needs to resize the window to increase the size of the middle part and make it usable. This is unusable for someone who doesn't know what to do.
Moreover, the lists that are scrollable have excessive white space at the bottom that should be removed.

Display issues in new tactic profile dialog

2025-01-15T14:33:47.928000Z

Ticket 837 has been modified: Display issues in new tactic profile dialog
Edited By: Guillaume Verdier (gverdier)
Status updated: 'open' => 'closed-fixed'