Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • V VISPA web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 84
    • Issues 84
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • 3pia3pia
  • VISPAVISPA
  • VISPA web
  • Issues
  • #513
Closed
Open
Issue created Dec 15, 2014 by Benjamin Fischer@benjamin.fischerOwner

file selector callbacks

The callback functions passed as arguments to the “openFileSelector” emission should always be executed, i.e. even if the selector is
closed without any selection.
This feature/bug is crucial for situations in which a selection of some path is mandatory in order for an extension to proceed
(e.g. the pxl browser must have given a proper path in order to work; an operation without any is still possible by closing the selector and not selecting anything which eventually leads to errors. The easiest solution is that the selector executes the callbacks at each “close”).

P.S. - Target version is 1.0.1 because the pxl browser, which might be installed this week, will depend on it.

  • If this fix is unwanted or too time-consuming (dT>~ minutes), this should not be a show stopper and/or I will implement a different but rather ugly solution to my problem.

(from redmine: issue id 2021, created on 2014-12-15 by root, closed on 2015-10-08)

  • Changesets:
    • Revision 2348 by Fabian Heidemann on 2015-10-08T14:44:28Z:
[fileselector] fix #2021: the file selector always fires the callback. The first argument is null, if it is just closed
  • Revision 2348 by Fabian Heidemann on 2015-10-08T14:44:28Z:
[fileselector] fix #2021: the file selector always fires the callback. The first argument is null, if it is just closed
Assignee
Assign to
Time tracking