[Bug/Feature Request] Quality of Life Improvements and Bug Report

[ALingll]

[Bug/Feature Request] Quality of Life Improvements and Bug Report

• Allow dynamic closing and opening of docking widegt. This can be useful in the following ways:

  • Brush Pack widget Improvements:
    • Users might have many brush packs but do not necessarily use all of them simultaneously. To ensure a clean user interface, it should be possible to close individual brush pack widgets and reopen them from the menu. This way, users can choose which brush packs to display and which to hide.
    • When new brush packs are loaded and WP is reopened, the interface layout often becomes cluttered with the newly loaded brush packs. Setting new brush packs to be hidden by default can prevent this issue.
    • Adding new brush packs to the brush folder often requires restarting the program to recognize the new brush packs. A refresh brush packs feature would be helpful.
  • Similarly, it would be helpful if the palette widget could be opened or closed from the menu to keep the interface clean.

• File Organization Improvements:

  • The ability to customize the default save path for files, brush pack paths, custom objects paths, and default export paths for different versions in the preferences.
  • It is suggested that scripts and plugins should be located in the same directory as the WP software. The default current path in scripts is the WP software path. Using relative paths in scripts should be relative to the WP directory, not relative to script file's path. If static resources need to be called in scripts, keeping them in the WP directory is a good way.

• I have noticed that layers loaded using wp.getLayer().fromFile().go() in WPScript do not appear in UI. Normally, we expect these layers to remain in the UI for use. Additionally, it would be helpful to have an interface to explicitly register layers in the UI, such as wp.registerLayer(layer).go(), allowing users to dynamically create and load layers into WP via code.

• It appears that WP does not read the path from JAVA_HOME but instead uses the Java path registered in the computer's registry. Many of my teammates have found this issue. Should there be an explicit way to specify the Java path, such as adding a .config file with the specified Java path?

• Other issues:

  • Noticing that quit() and exit() interfaces are not disabled in WPScript. Calling these interfaces can exit the WP program process without saving the project, which could be exploited maliciously.
  • There are multiple ways in which page layout can be read incorrectly, causing the layout to revert to the default configuration.