Klever

Done for unknown problem description and safe proof (branch "feature_7020"). But I think we need to do this for all pages. The only question is will it be new feature, or extension of this one?

Feel free to do this for all pages.

It has sense to finish this issue at last. Please, see discussion what to do.

Implemented in branch "feature_7164".

You forgot to scale problem descriptions. In addition I suggest to arrange elements at the Unknown page in the same way as at the Unsafe page. For Safes we likely don't have proofs now, but it would be also nice if you arrange elements at the Safe page like at the Unsafe page and scale proofs.

Evgeny Novikov wrote:

You forgot to scale problem descriptions. In addition I suggest to arrange elements at the Unknown page in the same way as at the Unsafe page. For Safes we likely don't have proofs now, but it would be also nice if you arrange elements at the Safe page like at the Unsafe page and scale proofs.

Fixed for problem description and other windows I found.

Arrangement of elements on Unknown/Safe is good enough. Unsafe page has two windows with text (error trace and source code), but unknown - only problem description. It would be ugly to stretch error description to full width of screen. Now these pages are handy.

Vladimir Gratinskiy wrote:

Evgeny Novikov wrote:

You forgot to scale problem descriptions. In addition I suggest to arrange elements at the Unknown page in the same way as at the Unsafe page. For Safes we likely don't have proofs now, but it would be also nice if you arrange elements at the Safe page like at the Unsafe page and scale proofs.

Fixed for problem description and other windows I found.

Arrangement of elements on Unknown/Safe is good enough. Unsafe page has two windows with text (error trace and source code), but unknown - only problem description. It would be ugly to stretch error description to full width of screen. Now these pages are handy.

I didn't notice any positive changes in scaling. I disagree that stretching error descriptions to the whole screen will be ugly. Please, see various error descriptions, e.g. here, and you will soon understand that many of them, say, from Weaver or CPAchecker are quite wide. Indeed error traces can be also very wide - to meet this issue we even introduced artificial "threads" that required extremely much efforts for full support but allows to very considerably reduce error traces width and to increase their readability.

Vladimir Gratinskiy wrote:

Evgeny Novikov wrote:

I didn't notice any positive changes in scaling.

But it exists. Problem description window is 70% of browser height for unknown page and 80% for creating unknown mark page.

It also depends on actual problem description heights in contrast to error traces, so likely I didn't notice this because of I opened a too small problem description.

I disagree that stretching error descriptions to the whole screen will be ugly.

Fixed. Unknown and safe pages are the same as unsafe.

Perfect!

I merged the branch to master in 54ec67d. Error traces and problem descriptions can be analyzed more easily now.