Activity for SwiftSearch
-
JackyDoggy posted a comment on discussion General Discussion
Needs Drag Drop of found files to other applications. If I didn't have so many bugs in my own software and a stroke to boot I would have liked to study it and implement DnD (not dragons and dungeons).
-
- modified a comment on discussion General Discussion
This seems unrelated to this program. And without any way to reproduce it I don't think there's anything I can do.
-
Alexandros Stefanidis posted a comment on discussion General Discussion
When ever i try to open .pdf/.odt or .rtf files the text inside get distorted (language is Greek)
-
This seems unrelated to this program.
-
This seems unrelated to this program.
-
Those are not duplicates; they are different streams of the same directory. This is by design.
-
Yes, the program only captures a snapshot of the filesystem at a given point in time. It doesn't dynamically update. This is by design and difficult to avoid.
-
When ever i try to open .pdf/.odt or .rtf files the text inside get distorted (language is Greek)
-
Folders get duplicated
-
Forgot to log in before posting .
-
Anonymous posted a comment on discussion General Discussion
SwiftSearch can't find a file if its already open while creating the file
-
John posted a comment on discussion General Discussion
You are right it is moving towards no BOM but not yet a completely settled issue. In one of my programs that exports CSV, BOM use is a user option so if needed it can be enabled. In any case this is a great piece of work. Thanks for the discussion too. Regards, John416
-
Anonymous posted a comment on discussion General Discussion
Ah I see. Note that BOMs are actually discouraged by Unicode, and Excel has weird quirks opening CSVs anyway, so that's why I leaned toward excluding them. Some programs can't open them well either.
-
My apologies for not being more clear. Sorry. Yes the SwiftSearch table does in fact show the foreign characters (Chinese in this particular case) correctly. It is just the 'dump to table' where the characters appear wrong in Excel. I think it is simply missing a UTF-8 BOM, granted that not all programs require BOM for UTF-8. This is what I see "China_Lexar\0-已转新pc\ " although the table shows "C:\Temp\China_Lexar\0-已转新pc\ " . Copy row and paste is fine as well. I really like this excellent...
-
Anonymous posted a comment on discussion General Discussion
Thanks for the suggestion! I'm confused though, doesn't it already support Unicode? What are you searching for that you're not seeing?
-
Great utility! Would be even better with a minor upgrade to support Unicode file and directory names, the world is multilingual. Should not be too difficult, I did it for FileImg from Microsoft creating FileimgU which is on Sourceforge too. https://sourceforge.net/projects/fileimgu/ Don't know if it will help you but changed code and original are there for comparison. Regards, John416
-
Anonymous posted a comment on discussion General Discussion
Please add thumbnails to the large icon view! Thumbnails would allow for quick pruning of duplicates as many different files can have the same filesize down to the byte. Also, please add file rename to the right click menu!
-
Hi there! Thank you for reaching out! I actually haven't yet established a general commercial license or pricing model (though I may do so as I see recent interest!), but I'm of course happy to license it on a case-by-case basis for your company. If you could please read the following and message me directly with the aforementioned information so I can understand your intended use, I'd be grateful & more than happy to discuss potential options: Will you need the license to include any kind of ongoing...
-
DarnF posted a comment on discussion General Discussion
Hi, I am working with a large international company and would like to use SwiftSearch to scan our central file servers for different reporting tasks. As SwiftSearch is distributed under the "Creative Commons Attribution Non-Commercial License V2.0", I am not allowed to use it. What would a commercial license cost? N.B: There is another topic with similar title "Commercial using", but this topic covers including parts of source code, whereas I do not want to modify it, only to use. Thanks
-
Anonymous posted a comment on discussion General Discussion
SwiftSearch automatically loads the NTFS indices on startup. This leads to "input lag" especially on slow systems. The progress bar I'm requesting is already implemented, but it's only displayed after pressing F5 and immediately starting a search. P.S. I tried doing it myself. I had no programming experience aside from writing a couple of if and while loops a couple of years ago, but I asked myself this: How hard can it be?More-than-fifteen-hours-of-fiddling-and-trial-and-error hard... I started...
-
Anonymous posted a comment on discussion General Discussion
Glad to hear! Unfortunately no there isn't. The Name column I didn't include because it's redundant and takes up extra space when the path is already there. The Type I didn't include because it would be far too slow if I included it. (It can easily take several minutes.)
-
Travis Bowen posted a comment on discussion General Discussion
So far this is working out really well. Still need to test on really big volumes. I'm able to export to .csv files from powershell using SwiftSearch. But the export does not include the Name and Type fields. Is there a way to get them to export? Thanks, this is a great tool.
-
I remembered something: you can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console). You can either do this in any of 3 ways: Via an app like CFF Explorer Via PowerShell: $f = [System.IO.File]::Open('C:\SwiftSearch.exe', [System.IO.FileMode]::Open); $f.Position = 60; $x = 0 + $f.ReadByte(); $x += $f.ReadByte() * 0x100; $f.Position...
-
Thank you. I'll give it a try!
-
I remembered something: you can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console). You can either do this in any of 3 ways: Via an app like CFF Explorer Via PowerShell: $f = [System.IO.File]::Open('C:\SwiftSearch.exe', [System.IO.FileMode]::Open); $f.Position = 60; $x = 0 + $f.ReadByte(); $x += $f.ReadByte() * 0x100; $f.Position...
-
I remembered something: you can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console). You can either do this in any of 3 ways: Via an app like CFF Explorer Via PowerShell: $f = [System.IO.File]::Open('C:\SwiftSearch.exe', [System.IO.FileMode]::Open); $f.Position = 60; $x = 0 + $f.ReadByte(); $x += $f.ReadByte() * 0x100; $f.Position...
-
I remembered something: you can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console). You can either do this in any of 3 ways: Via an app like CFF Explorer Via PowerShell: $f = [System.IO.File]::Open('C:\SwiftSearch.exe', [System.IO.FileMode]::Open); $f.Position = 60; $x = 0 + $f.ReadByte(); $x += $f.ReadByte() * 0x100; $f.Position...
-
You can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console). You can either do this in any of 3 ways: Via an app like CFF Explorer Via PowerShell: $f = [System.IO.File]::Open('C:\SwiftSearch.exe', [System.IO.FileMode]::Open); $f.Position = 60; $x = 0 + $f.ReadByte(); $x += $f.ReadByte() * 0x100; $f.Position = $x + 0x5C; $f.WriteByte(0x3);...
-
You can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console). You can either do this in any of 3 ways: - Via an app like CFF Explorer - Via PowerShell: $f = [System.IO.File]::Open('C:\SwiftSearch.exe', [System.IO.FileMode]::Open); $f.Position = 60; $x = 0 + $f.ReadByte(); $x += $f.ReadByte() * 0x100; $f.Position = $x + 0x5C; $f.WriteByte(0x3);...
-
You can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console). You can either do this in any of 3 ways: - Via an app like CFF Explorer - Via PowerShell: $f = [System.IO.File]::Open('C:\SwiftSearch.exe', [System.IO.FileMode]::Open); $f.Position = 60; $x = 0 + $f.ReadByte(); $x += $f.ReadByte() * 0x100; $f.Position = $x + 0x5C; $f.WriteByte(0x3);...
-
You can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console). You can either do this via an app like CFF Explorer, or if you have Python, via a command like the following: python -I -c "import struct, sys; f = open(sys.argv[1], 'r+b'); f.seek(60); f.seek(struct.unpack('I', f.read(4))[0] + 0x5C); f.write(struct.pack('H', int(sys.argv[2])));"...
-
You can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console). You can either do this via an app like CFF Explorer, or if you have Python, via a command like the following: python -I -c "import struct, sys; f = open(sys.argv[1], 'r+b'); f.seek(60); f.seek(struct.unpack('I', f.read(4))[0] + 0x5C); f.write(struct.pack('H', int(sys.argv[2])))"...
-
You can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console). You can either do this via an app like CFF Explorer, or if you have Python, via a command like the following: python -I -c "import struct, sys; f = open(sys.argv[1], 'r+b'); f.seek(60); f.seek(struct.unpack('I', f.read(4))[0] + 0x5C); f.write(struct.pack('H', int(sys.argv[2])))"...
-
You can actually use other versions of the program (including 7.5.1) as a console program too. The only thing you need to do is to change the "Subsystem" bit in the .exe's "optional header" from 2 (Windows GUI) to 3 (Windows Console). You can either do this via an app like CFF Explorer, or if you have Python, via a command like the following: python -I -c "import struct, sys; f = open(sys.argv[1], 'r+b'); f.seek(60); f.seek(struct.unpack('I', f.read(4))[0] + 0x5C); f.write(struct.pack('H', int(sys.argv[2])))"...
-
I have the 1.5 version running now on a test machine. When I move it to something more robust, it crashes. So when I try to run it on a really large volume, it crashes. Is this possibly because this is a 32 bit version? Is there a way to make it work with 64 bit, if so? Sorry for the flurry of questions.
-
When I run the command line version, it opens and closed co quickly it's hard to see. I'm using windows server 2019. Is there something I need to do to get the command line version runnning? Thank youl.
-
I thought so based on what I've read so far. Is there instructions or guidance on how to get that version up an running?
-
There's nothing more recent than version 1.5 I believe, unfortunately.
-
Is there a command line version of this tool? I saw the version 1.5 but after downloading it to my computer it does not run.
-
I don't know what it could be unfortunately... how old are the versions you've tried? Have you tried version 6.4? 1.3? Does this really occur on those too?
-
Anonymous posted a comment on discussion General Discussion
The GUI starts OK but then after a few seconds the Error message occurs even if I do nothing. If I ignore the message and start a search it begins but 'freezes'. Have tried older versions with the same Error. Looked at the processes with Process Monitor and have attached a file with some of the Events near the end when Error appears in case that assists. Have tried most of the older versions but get the same Error. I know how fast your App is on another PC - so I really hope you can help me to solve...
-
Thanks for reporting! Unfortunately I'm not sure. Does this occur immediately when you start the program, or does it happen when you do something? Have you tried running an older version to see if it works for you?
-
Anonymous posted a comment on discussion General Discussion
"Microsoft Visual C++ Runtime Library Program SwiftSearch32.exe (v7.5.1) This application has requested the Runtime to terminate in an unusual way. Please contact the application's support team for more information." Please can someone help me to get the App to run without this error. Have installed the latest Microsoft VisualC++ Redistributable (VisualStudio2015,2017,2019) Running Windows XP SP3
-
Anonymous posted a comment on discussion General Discussion
Hello excellent program thank you I would like to be able to throw several instance of swiftsearch you have to close and reopen and sometimes it is not practical thank you
-
Anonymous posted a comment on discussion General Discussion
Yes, please!
-
Anonymous posted a comment on discussion General Discussion
There's no support for this directly. But you can make a regular expression that matches files from multiple directories. For example, this pattern will match anything under C:\Windows or C:\Users: >^(C:\\Windows\\.*|C:\\Users\\*.)\\.*
-
Anonymous posted a comment on discussion General Discussion
How can i add multiple searched from different folders?
-
Yup!
-
Anonymous posted a comment on discussion General Discussion
Thanks for the quick response! I very seldom use Explorer. All my searches are done with swiftsearch.
-
Great question! Blue/green are the same as in Explorer. (By default blue means NTFS-compressed, and green means encrypted.) Teal (actually it's the midpoint between the above two colors^, which is teal by default) means the file has the "sparse" flag set. This can happen either because the file is a sparse file, or because the data is stored in a special way. For example, Windows 10's CompactOS feature (WOF compression) can set the "sparse" flag, so this can also indicate your data is using WOF compression....
-
Anonymous posted a comment on discussion General Discussion
Could you please describe what the different colors mean in the search results. Most of the lines in my search results are displayed in black, but there are lines which are displayed in teal. Are there any more colors/meanings than these two and what are they?
-
You can start your pattern with >(?!.*:Zone\.Identifier$) to exclude :Zone.Identifier streams. Note that anything after this will match the entire path (not just file name).
-
You can start your pattern with >(?!.*:Zone\.Identifier$) to exclude :Zone.Identifier streams.
-
Anonymous posted a comment on discussion General Discussion
How Exclude <file>:Zone.Identyfier with Regex to just conserv <file> ?</file></file>
-
The list is rather static currently, so changes won't be visible in it. But you should be able to delete files by right-clicking them and selecting Delete. You just won't see the changes until you refresh SwiftSearch.
-
Yes, the list is rather static currently.
-
Anonymous posted a comment on discussion General Discussion
Are you saying there is no way to delete files found in the search window of SwitftSearch?
-
Hi, As far as danger is concerned, no, the program should never have been dangerous. It only opens the volume directly for reading -- it doesn't try to bypass the filesystem for writing purposes. But I'm pretty sure I have indeed fixed a wide variety of issues in everything from NTFS reading to the indexing, matching, UI, and everything else. I don't have all the changes memorized, and I don't necessarily even list them in the release notes, but I can tell you that you're running buggy versions I...
-
Anonymous posted a comment on discussion General Discussion
Hi wfunction, I appreciate your work and I have been using Swiftsearch for several years including many older versions such as 5.1 and 6.0 on my machines (x64 or x86) fine. What I really wonder is whether newer versions fix errors reading NTFS table or fixes issues with the program itself such as displaying/interface issues or keyboard issues or wildcard operation issues etc.? I do not think that the core functionality of the program like reading/operating over NTFS system had any crucial errors...
-
I am OK to just name it the way you suggsted incl. all other changes to the code and only share binaries... if that is what you want. Yes thanks, I'd appreciate that. I admit I might be wrong about this... but hopefully there won't be too many people who will come to me for bugs that you might have introduced. I guess I'll take the risk and see :-) thanks!
-
Robert Nio posted a comment on discussion General Discussion
Sorry for the missunderstanding. I understood that you wanted to prevent ANY confusion between the two versions ... thus using a VERY different name would do the trick. Otherwise people will still contact you for things I implemented ... as the name is just very similar ... people might think the "bug" might be in the core software ... and thus also an your side ... I am OK to just name it the way you suggsted incl. all other changes to the code and only share binaries... if that is what you want....
-
Isn't using a "totally different name" the exact opposite of what I wrote? :\ I was just trying to explain, if SwiftSearch isn't in the name, then it will look like your version is the original. 99% of users will not look inside Help->About; they just look at the software name. They won't have a clue what you're giving them is really SwiftSearch with some modifications. Why not do "SwiftSearch (Robert Nio edition)" or something like that? That's what I suggested, not replacing the name entirely with...
-
Isn't using a "totally different name" the exact opposite of what I wrote? :\ I was just trying to explain, if SwiftSearch isn't in the name, then it will look like your version is the original. 99% of users will not look inside Help->About; they just look at the software name. They won't have a clue what you're giving them is really SwiftSearch with a few modifications. Why not do "SwiftSearch (Robert Nio edition)" or something like that? That's what I suggested, not replacing the name entirely...
-
Isn't using a "totally different name" the exact opposite of what I wrote? :\ I was just trying to explain, if SwiftSearch isn't in the name, then it will look like your version is the original. 99% of users will not look inside Help->About; they just look at the software name. Why not do "SwiftSearch (Robert Nio edition)" or something like that? That's what I suggested, not replacing the name entirely with your own.
-
Isn't using a "totally different name" the exact opposite of what I wrote? :\ I was just trying to explain, if SwiftSearch isn't in the name, then it will look like this is the original. 99% of users will not look inside Help->About; they just look at the software name. Why not do "SwiftSearch (Robert Nio edition)" or something like that? That's what I suggested, not replacing the name entirely with your own.
-
Isn't using a "totally different name" the exact opposite of what I wrote? :\ I was just trying to explain, if SwiftSearch isn't in the name, then it will look like this is the original. 99% of users will not look inside Help->About; they just look for the software name. Why not do "SwiftSearch (Robert Nio edition)" or something like that? That's what I suggested, not replacing the name entirely with your own.
-
Isn't using a "totally different name" the exact opposite of what I wrote? :\ I was just trying to explain, if SwiftSearch isn't in the name, then it will look like this is the original. Why not do "SwiftSearch (Robert Nio edition)" or something like that? That's what I suggested, not replacing the name entirely with your own.
-
Excellent ... will just do that :) Thanks for mentioning the GUID (very important) ... yet I would have missed that ... Will use a TOTALLY different name ... so that there is NO visible connection whats however ... still will mention in about the attribution to you. Binaries only
-
Binary is better, yeah. Let's think this through. So if you change the name entirely, ordinary users aren't going to know it's a modification of this project without digging into the authorship details (which most people won't do). But of course, if you keep the name, then it's going to confuse users and think it's an official release. Here's an idea: Could you change the name to something like "SwiftSearch (Robert Nio's version)", or similar? That way the original and also the modification are both...
-
I want to share the binary of what I did ... I am OK to keep the code to myself. Also there would not have been any CONFUSION about who is who ... as mentioned I would use a different name throughout the app. (Giving you the honors for developing the "guts" however :) Would that work for you?
-
I'm not sure about the regex unfortunately... I'd have to debug it when I get the chance and see. Regarding your GitHub idea though, I'm actually not OK with it; please don't do that. It's not something I want to see happening right now. If you'd really like to share your changes, you can post a .patch file here, but I think some of your changes (such as your quoting) are very specialized to your use case and will likely break if applied to other users. I would just use the tool for your own pur...
-
Thanks again for all your help & support ... during the last couple weeks I learned a lot of C++ ... and your code :) I am almost done with my little programming ... I added a few more "features" to the tool e.g. a better CLI parser, more flexible output etc. etc. The last thing (nice to have) is proper REGEX processing as mentioned above. I used your code form this site to "trouble shoot" tried all permutations of boost / wtl / atl (incl. boost 1.68 / wtl 467) to no avail. ... still cant parse >(?i)...
-
Thanks again for all your help & support ... during the last couple weeks I learned a lot of C++ ... and your code :) I am almost done with my little programming ... I added a few more "features" to the tool e.g. a better CLI parser, more flexiable output etc. etc. The last thing (nice to have) is propper REGEX processing as mentioned above. I used your code form this site to "trouble shoot" tried all permutations of boost / wtl / atl (incl. boost 1.68 / wtl 467) to no avail. ... still cant parse...
-
I'm guessing it's probably your Boost version. I think I must've used 1.68 for my binaries. You might want to add that feature yourself locally since I might not be adding it in the near future.
-
I'm guessing it's probably your Boost version. I think I must've used 1.68 for my binaries. You might want to add that feature yourself since I might not be adding it in the near future.
-
[EDIT] BTW, I want to be able to switch case sensitivity ON / OFF mmhhh ... for the test I took your binaries … and both work … no problem with regex. I just compiled versions using the code you have on this site ... and I get the error on both (GUI / CLI) ... The BOOST version is the 1.72 / WTL is 467 Is the source here a tid bit older than what you used to create the binaries with? TEST STRING: SwiftSearch.com ">(?i)C:\TemP.*.txt" "C:" ==> ERROR
-
mmhhh ... for the test I took your binaries … and both work … no problem with regex. I just compiled versions using the code you have on this site ... and I get the error on both (GUI / CLI) ... The BOOST version is the 1.72 / WTL is 467 Is the source here a tid bit older than what you used to create the binaries with? TEST STRING: SwiftSearch.com ">(?i)C:\TemP.*.txt" "C:" ==> ERROR
-
Ohh I had no idea you're talking about the CLI version! Please mention that when that's the case. I'm not sure to be honest, you might need to debug this yourself. Could you show the actual invocation of the console version? Your console window isn't really a screenshot of the program but a screenshot of something else you made.
-
The error is caught by catch (std::invalid_argument &ex) { fprintf(stderr, "%s\n", ex.what()); result = ERROR_BAD_PATHNAME; } the GUI version seems to be OK ...
-
What error are you seeing exactly? Would you mind posting a screenshot? Also, I think everything is already case-insensitive? I'm not sure there's any way to make it case-sensitive.
-
REGEX: ... Why is this WRONG (Syntax Error)? >(?i)D:\data\.*.py Apparently the GLOBAL (?i) Case insensitivity is not recognized ... Any idea how to add this global token? Thanks in advance :)
-
Sorry haha. If you mean as a std::tstring (i.e. std::basic_string<TCHAR>), you can always just use the iterators (std::tstring(s.begin(), s.end())). If you actually mean std::string then you'll also need an encoding conversion (most likely you want UTF-8?) in which case you can take a look at wcstombs in string_matcher to see how to do it.
-
Quick question ... I am loosing my mind over your std::tvstring structure LOL :) I want to get some of the data as a std::string e.g. "i->root_path()" Any pointers ? ... Thanks & have a great weekend.
-
Ah this just seems like a new feature than a bug. I'm glad it's useful :) but it requires a lot of screen space so I'm not sure about adding it. Thanks for sharing it though!
-
LINE# 5158 ==> commented out LINE# 5117 ==> WTL::CHeaderCtrl hdr = this->lvFiles.GetHeader(); { int const icol = COLUMN_INDEX_NAME ; LVCOLUMN column = { LVCF_FMT | LVCF_WIDTH | LVCF_TEXT, LVCFMT_LEFT , 250, this->LoadString(IDS_COLUMN_NAME_HEADER )}; this->lvFiles.InsertColumn(icol, &column); } { int const icol = COLUMN_INDEX_PATH ; LVCOLUMN column = { LVCF_FMT | LVCF_WIDTH | LVCF_TEXT, LVCFMT_LEFT , 280, this->LoadString(IDS_COLUMN_PATH_HEADER )}; this->lvFiles.InsertColumn(icol, &column); } { int...
-
Thanks for considering! :) I think most of these are somewhat subjective customizations, so I'm not sure about adding them right now. However, the last 2 GUI items you listed seem like possible bugs that need to be addressed. Would you mind sharing "before" + "after" screenshots for the "Fit columns to Window" change, as well as the column width change? I'd be interested in seeing what the problem was and what it looked like after your fixes. Thank you!
-
Now, I added a few cosmetic things ... how do I offer those as potential enhancemenet to you ? I tried to stay as close to the original source "style" as much as I could ... so it does not look out of place :) Here is what I added / changed: More colors for file types in the GUI version e.g. hidden files a little less red ... system files full red Expanded the ATTRIBUTES of each file. got rid of the "fit columns to screen" for now ... on my systemn the win does NOT maximize on first call ... I guess...
-
... was too quick ... had a little typo in my code ...
-
That's impossible. There are already lines that do line_buffer.push_back(_T('\t')) so line_buffer.push_back(_T('\''))shouldn't be any different. I think you're typing something incorrectly. Are you using push_back like I wrote?
-
Tried these: _T('\''); _T("'"); and this: _T('='); All gave the SAME error as above ...
-
Oh sorry, just use line_buffer.push_back(_T('\'')); instead.
-
upps .. sorry for the REPOST ... didn't see the previous post working ... ok, tried it as you suggested ... now I get THIS error: C++ no operator matches these operands operand types are: std::tvstring += const wchar_t [2]
-
See my previous reply.
-
Hi, after working with your code for a while, I was able to get all the attributes collected and presented in the GUI as well as the CLI. Now I am STUCK at a "simple" problem (at least for you) ... Trying to encaplulate the PATH / FILENAME with " ' " ... I though I could just do this: buffer.push_back(_T("'")); but that is NOT working ... tried all sorts of string / char types ... but std::tvstring is giving me grey hairs :) Idealy, would like to add a CHAR or STRING to these structures: @ LINE #...
-
Try including the subsequent line: line_buffer += _T("'"); line_buffer += root_path; i->get_path(key, line_buffer, false); line_buffer += _T("'"); I wouldn't recommend surrounding with ', though. Single quotes are valid path characters. If you have to do this, I would suggest double-quotes instead. (Actually those are also valid inside alternate data streams, but unlikely to occur in practice.)
-
Was able to collect all the ATTRIBUTES and make them available to GUI and CLI. I ran into I guess (for you) simple issue ... I need to ENCAPSULATE the PATH with " ' " ... LINE# 7643 I thought I can do this: line_buffer.push_back(_T("'")); line_buffer += root_path; line_buffer.push_back(_T("'")); But that did not work ... I am totally lost with the std:tvstring / etc. etc. I like to just ADD a string or char to the LINE-BUFFER or TEXT @ Line 6684 Any help is appreciated :) Thanks
1 >