Sharp Stock

English

简体中文

English

简体中文

FAQ ​

This chapter summarizes common technical questions and their standard solutions encountered while using Sharp Stock.

Q: Why do some Spine assets fail to display thumbnails? ​

A: Please troubleshoot using the following steps:

  1. Associated File Check: Ensure the .skel skeleton file and its accompanying .atlas and texture images are stored in the same directory.
  2. Version Standards Check: Sharp Stock currently deeply supports Spine versions 3.7 to 4.1. If the exported version is too low or too high, the preview engine may fail to parse it.
  3. Forced Refresh: You can try right-clicking "Rebuild Preview" on the asset card, or execute "Deep Scan" in [Settings] → [Maintenance & Optimization].

Q: How can I quickly move assets between directories? ​

A: You can directly select target assets in the Main View Grid and drag them to a specified folder node in the left navigation tree. The system will simultaneously execute the physical disk move and database index update, ensuring that asset notes and tag information are not lost.

Q: What should I do if AI features prompt an error? ​

A: If you are on the Steam build, AI auto-tagging/description and the AI Model Configuration settings page are not offered due to platform review policies—use the Microsoft Store or App Store build instead. For other builds, try the following:

  1. Service Connectivity: Check if the API address in [AI Model Configuration] is accessible (e.g., whether the local Ollama service is running).
  2. Model Matching: Confirm the Model Name in settings is spelled correctly and that the model is deployed on the server side.
  3. Quotas & Permissions: If using commercial cloud services (like OpenAI), check if your API Key is valid and whether your account balance is sufficient.
  4. Log Troubleshooting: You can view detailed error stack information in the [Diagnostics & Debugging] panel to precisely locate the cause.

Q: Will executing "Rebuild Thumbnails" accidentally delete original resources? ​

A: Absolutely not. This operation only targets the preview cache files generated internally by the software (located in the thumbnails directory) to release redundant space. After clearing, the system will automatically regenerate missing previews the next time you browse the asset grid.

Q: Why does the SVN status display the message "Current directory is not an SVN working directory" or remain gray/fail to detect modifications under the macOS Sandboxed version (App Store)? ​

A: This is caused by the security restrictions of the macOS App Sandbox:

  1. Sandbox Access Boundaries: In sandbox mode, the application is strictly limited to accessing the directory you explicitly selected in the folder dialog (the asset library root).
  2. SVN Working Copy Path Constraint (.svn directory not in current directory): SVN determines the working copy by searching for a .svn folder in the current directory and its parent directories. If your .svn directory resides in the parent directory/external directory of the selected library root (for example, if you opened /Users/b1gm0use/SharpStockDemo/trunk but the .svn folder is located in /Users/b1gm0use/SharpStockDemo/.svn), the sandbox prevents the SVN command-line tool from reading parent paths, treating the selected directory as a non-working copy. This causes the application to display the tooltip "Current directory is not an SVN working directory" and blocks change detection.
  3. Solution:
    • Ensure that the selected asset library root is the root of the SVN working copy itself (i.e., the .svn folder must be inside the selected directory, such as /Users/b1gm0use/SharpStockDemo/trunk/.svn).
    • Alternatively, use the built-in "Checkout from Remote SVN" feature to check out the repository directly into the library root folder.
  4. Credential Caching Issue (Keychain Restrictions): In a macOS sandbox environment, the built-in SVN tool cannot interact with the macOS system Keychain to store or read credentials. This is now fully automated by the application:
    • When you check out a library using the "Checkout from Remote SVN" dialog and provide your username and password, the application automatically specifies an isolated config directory (--config-dir) for the bundled SVN client.
    • Credentials will be securely cached inside the sandboxed container's internal storage. Subsequent commands (like status, update, or commit) will automatically read from this private cache, without requiring any manual terminal commands or system Subversion configuration edits.