XYplorer Beta Club

Right now on my system, the ".dat" extension is associated with a WMP movie clip and I've seen it linked before to other apps, so could this be renamed to something unique to XY as we did with .XYS so that it could also be included on Preview as known type?

Given that there are two distinct types of .dat within XY, one being like the Catalog and not easily readable but the other is more like an .ini so could easily be viewed as they are...and it's only this second type that I'm referring to here for a different suffix.

Part of the reason for doing so would be to allow one to take a quick peek at search results stored within it while still on the Preview tab instead of having to use Raw View or QFV.

F11 will open it for the quick peek.

But you are right when you talk about the tab_#.dat files. I named them DAT years ago to avoid a name collision with FindTemplates which were in the same path at that time.

Now, since DP, the stuff has been reorganized and indeed they should be called INI. I'll see whether I can do that without breaking too much...

admin wrote:Now, since DP, the stuff has been reorganized and indeed they should be called INI. I'll see whether I can do that without breaking too much...

They wouldn't need to be called INI if that causes name conflicts...maybe something like XYC for cache? As long as it's unique, it could be just about anything...true, they do look like INI but I've seen many a file that looks that way called other things in various apps, and as long as we can define it to open like an INI, that's all that matters.

.xyc seams to be not associated by others right now

admin wrote:F11 will open it for the quick peek.

Yes, but that is QFV, right? And I said "while still on the Preview tab instead of having to use Raw View or QFV." (emphasis added now)

It may be that INI could work just fine but given my mistakes yesterday, I figured I better not say that it would or not.

Stefan wrote:.xyc seams to be not associated by others right now

Thanks, but their format is INI so I will call them *.ini.

admin wrote:I'll see whether I can do that without breaking too much...

I presume that any newly saved caches will have the INI name but it would still find any existing DAT files? But that would also leave some obsolete files laying around so....

Hope I didn't suggest something that breaks it for others...

j_c_hallgren wrote:

admin wrote:I'll see whether I can do that without breaking too much...

I presume that any newly saved caches will have the INI name but it would still find any existing DAT files? But that would also leave some obsolete files laying around so....

Hope I didn't suggest something that breaks it for others...

It should work. If you get problems, tell me...