Pattern File as project

[GhoulFool]

First time using ImHex.

I noticed that saving the workspace as a project that (custom) pattern files are not included and have to be reloaded each time. Is this an oversight or part of the design Or am I missing something?

[nebkat]

Have also found this to be an issue. All my workflows are pattern-centric and having to do File -> Export -> Pattern File is convoluted enough that I usually maintain a separate editor and just copy/paste the pattern as I am writing it.

[paxcut]

I don't know what issue that may be you are speaking of. As for your problems editing pattern files note that under 1.37.4 and before you could export patterns from the context menu of the pattern editor so you never needed to do File > Export > Pattern File.

Under 1.38.0 and from then on you can now load and save pattern files using the same shortcuts that are used to load and save input files. Which one is used depends on what part has the current focus. Opened/saved files are tracked for content and you will be notified if they are changed externally.

[nebkat]

Wasn't aware of that entry in the context menu but the 1.38.0 solution sounds perfect. Is it worth running the nightlies or better to stick to 1.37.4 for stability?

[paxcut]

I am not sure what custom pattern files mean. All pattern files that are opened for each provided are saved in the project together with all other internal files needed to restore the project afterwards. Even patterns auto-loaded from the library are saved with projects.