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 10 20H2
OBS Studio version: 26.0.2, 26.1.0-rc1, current master

Expected Behavior

The Edit menu's contents should make sense for the currently selected source. Including if the source is deselected.

Current Behavior

The enabled/disabled state of menu items in the Edit menu are only set when the user right clicks a source in the

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,

Currently it's possible to list possible variable values in the CLI with e search.in=?.
But in Ve visual configuration options navigator the feature is missing:

$ r2 -
[0x0000000]> Ve
[EvalSpace < Variables: search.align]
                                                                                                                                                                    

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

The sprite compiler function sprite build is inefficient with the way it builds a new g2.dat file. As this function is run every time we compile on the CI's. It may reduce compile times by improving it. See this link for more info on the sprite compiler: https://github.com/OpenRCT2/OpenRCT2/wiki/Sprite-compiler

The problem with the sprite build is that it opens adds an image and finally saves