Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File dialog: Show sequences shows no files unless Show hidden files is checked #5810

Closed
Anti-Distinctlyminty opened this issue Apr 20, 2024 · 1 comment · Fixed by #5831
Closed

Comments

@Anti-Distinctlyminty
Copy link

Version: Gaffer 1.4.0.0-windows
Third-party tools: None
Third-party modules: None

Description

When choosing a file sequence from the ImageReader node, the dialog shows no images sequences, even though one is present. If I uncheck the 'Show sequences' checkbox, select a file, then replace the digits with ####, everything works as expected.
Also, if I check the "Show hidden files" checkbox, the sequence now appears. The file sequence in question does not start with a ".".

Steps to reproduce

  1. Start a new session.
  2. Place an ImageReader.
  3. Open the file chooser dialog and navigate to a location containing an image sequence.
  4. Toggle the "Show hidden files" checkbox. The sequence should now appear.
@LichiMan
Copy link

This is happening to me too. I thought it was in mapped samba network drives but it's happening in local folders too.

ericmehl added a commit to ericmehl/gaffer that referenced this issue Apr 29, 2024
Fixes GafferHQ#5810

When checking a path that has the `#` character for frame substitutions,
`HiddenFilePathFilter` would always treat it as hidden. The file with
`#` does not exist, so the Windows API would return
`INVALID_FILE_ATTRIBUTES` whose value is `-1`. `FILE_ATTRIBUTE_HIDDEN`
has a value of `2`. `-1 & 2 = 2`, so sequences would always be
considered hidden.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants