It is currently expected that UIs will figure out when to hide msg_history_show messages by themselves.

I think this is bad for two reasons:

• It makes UIs less similar, increasing the number of things to learn when going from one UI to another.
• It makes UIs different from the TUI, which offers a press ENTER prompt when the time to hide msg_history_show messages has come.

After [di

Platform

Operating system and version: Windows
OBS Studio version: 26.1.1
OBS Log file: N/A

Expected Behavior

EITHER:
a) Multiple transform panels open for different sources and closed manually (not preferred)
b) The transform panel shows the appropriate information for the respected layer selected

Current Behavior

The transform panel sometimes shows the newly selected item

We have currently simple GitHub page, but we need to think about it's update with some better design.

Currently register looks like:

   private static <T> void register(Map<T, T> substitutions, T annotated, T original, T target) {
        if (annotated != null) {
            guarantee(!substitutions.containsKey(annotated) || substitutions.get(annotated) == original || substitutions.get(annotated) == target, "Already registered: %s", annotated);
            substitutions.put(annotated,

Description

Motivation

When inserting new submaps into a RIOBank, adjusting the boundaries of existing submaps is necessary, to ensure that submaps don't intersect.

Task

Implement r_io_submap_set_from and r_io_submap_set_to in libr/io/io_submap.c on siol_eternal branch:

R_API bool r_io_submap_set_from(RIOSubmap *sm, const ut64 from);
R_API bool r_io_submap_set_to(RIOSubma

In my mind one of the key things (besides visualization) Sourcetrail provides is a useful graph structure for source code that can be used for various types of analysis, without having to go through the pain of writing a clang analyzer yourself. However, since sourcetrail doesn't have plugins (#1076), writing your own analysis tools is a bit of work, and may not let you use other kinds of graph an

Feature Request Type

• Core functionality
• New behavior

Description

We now have the pieces

We currently use a macro for writing down a money amount as a literal. We should move to a more modern C++ representation with a user defined literal like the below:

constexpr money32 operator"" _GBP(long double money)
{
    return money * 10;
}

static_assert(MONEY(2, 40) == 2.40_GBP);

Go through the codebase and replace all MONEY macro uses with the equivalent version. You m