Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 2,002
    • Issues 2,002
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 57
    • Merge Requests 57
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ParaView
  • ParaViewParaView
  • Issues
  • #19288

Closed
Open
Opened Aug 29, 2019 by Cornelis Bockemühl@cobo
  • Report abuse
  • New issue
Report abuse New issue

Splash image of custom app not found due to naming inconsistency

A little bug in the ParaView build setup files that is related to handling a splash screen image: in ParaViewClient.cmake(207) [referring to v5.7-RC2] I had to change this line

":/${_paraview_client_NAME}/${_paraview_client_splash_image_name}")

into this:

":/${_paraview_client_NAME}/${_paraview_client_splash_base_name}")

Without this change, the pqAPPLICATIONInitializer::Initialize() function would look for a resource named "APPLICATION_splash.img" while in reality the name of the resource would be "APPLICATION_splash" - without the “.img” extension. (Of course the fix could have been done in a way that the naming of the splash bitmap is adapted to have the extension - only it has to match!)

Edited Aug 30, 2019 by Cornelis Bockemühl
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: paraview/paraview#19288