C

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

Please describe what are you missing or wanting to be improved
Recently I read a new syntax coloring technique for programing languages. Instead of highlighting grammar, highlight the things you are likely to mistake. So make sure strcpy and strncpy are easily distinguishable by their color. It would be cool to apply this to immediate values in assembly and the ? command

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

Description of Change

References

Checklist