-
Notifications
You must be signed in to change notification settings - Fork 268
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
2.10 CINF broken #517
Comments
HellGore
pushed a commit
that referenced
this issue
Jan 25, 2017
Fixed |
Thank you, work well now! :) |
ronag
pushed a commit
to nxtedition/casparcg
that referenced
this issue
Jan 16, 2018
Former-commit-id: f0af280
ronag
pushed a commit
that referenced
this issue
Jan 16, 2018
ronag
pushed a commit
that referenced
this issue
Feb 21, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The implementation of
CINF
seems to be nearly the same in 2.0.7 and 2.1.0, but 2.1.0 still produces another result than 2.0.7, and some cases aren't possible to sucessfully do withCINF
in 2.1.0CINF
you pass a filename, andCINF
then searches recursivly through all folders, matching the file-name against all files, and reports the file attributes for all files with a matching file name.auto file = path.replace_extension(L"").filename();
(2.0.7)vs.
auto file = path.replace_extension(L"").filename().wstring();
(2.1.0)This is a to be considered a breaking bug, as with the current 2.1.0 result you simply can't access
CINF
-info from sub folders.I suggest that the new implementation should allow for passing in
subfolder/subsubfolder/filename
and match agains bothpath
andfile
, allways producing a single line of result, never listing an array of multiple files with the same file-name in different sub folder.The text was updated successfully, but these errors were encountered: