FlatView = true | false
2 Sans
You are funny

BTW, why don't u make this plug open source ?
Moderators: Hacker, petermad, Stefan2, white
To be honest? I'm too lazy, for this. But I swear - if sometime TC will allow to load plugin at startup I'll implement fast search on startup in background thread.How about having an option to make the searches permanent?
For me too, but it is absolutely impossible.For me even the plain filenames are enough,
Because first it have to be implemented.Why don't you add ini option:
Somebody want to develop such plugin? I'm ready to help with all my knowledge.BTW, why don't u make this plug open source ?
I already suggested that here, but I don't expect this:but I swear - if sometime TC will allow to load plugin at startup
Except for the lack of time, is that a problem ?Because first it have to be implemented.
Well, I wanted to do this thing for a while, without using Locate as its DB is open source. Your way is nicer as it requires no knowledge of Locate internals. It would be good to make it open source, I might add some code one day....BTW, why don't u make this plug open source ?
I dont understand this. I thought (not knowing the internals of the plugin system) it works just like the normal filesystem, where after pressing ctrl-b, several files appear with the same filename.For me too, but it is absolutely impossible. Laughing What do you expect to see after search for "readme.txt"? Several files in the single folder with identical names? No chance.
Yes, I've seen it. I've suggested it before too. Without success but I hatch a hope.I already suggested that here, but I don't expect this:
Yes, I know. I've used this method in one of my plugins. Unfortunately this method have major drawback - user have to keep this plugin custom view as startup view. It good for me, but many users don't like it.There is a way to execute plugin on startup now, using dummy content field. This requires to have content plugin along with your FS plugin witch sole purpose will be to start your FS resident part.
High spirit.Except for the lack of time, is that a problem ?
I prefer to help you write your own plugin (if you need such help). Ok?It would be good to make it open source, I might add some code one day....
It is big difference. TC offers to you kind of service "shows different files with same names", but TC know about difference between files. In FS-plugins TC knows only what plugin reports to TC. So plugin cannot report about different files with the same name in the same location.several files appear with the same filename.
No, it has not. Read the entire procedure I posted in the mentioned topic.Unfortunately this method have major drawback - user have to keep this plugin custom view as startup view. It good for me, but many users don't like it.
That was not the point. This plugin is preatty much trivial. However, even the trivial things require time. That was the point.I prefer to help you write your own plugin (if you need such help). Ok?
Believe me, I'm not only understand entire procedure, I even tried to implement it half year ago while looking way to load plugin at startup.Read the entire procedure
Yes, it is. If TC starts in any non-custom view (Full, Brief etc...) it not loads content plugins. If you prefer I can rephrase it: user have to keep as startup view any custom view containing field from this plugin.No, it has not.
what about 1C crashed when column width was 0.
Yes, it must start in custom view. Well, there are limitations of that system.Yes, it is
Ha ha, how that compares to our story ? It will be started even when TC is not, witch is not the point.About modification wincmd.ini - no, thanks. Much more easy and safely to write external program to detect TC startup and inject required dll in TC.
AFAIR minimum is 5.what about 1
Well, it is matter of taste. BTW, I didn't wrote "better" - I wrote "easy and safely".Much better then resident program running all the time
Now imagine my anger, because I personally want always start TC in brief view.Well, there are limitations of that system.
Yes, you absolutely right.The only good solution is to support this by Ghisler itself. Nothing easier. Just see the ini, load all dlls and call 1 func.... can be done within an hour or so including interface for adding/removing start up plugins.
You don't understand my point. Problem is not to have several installations.What's the problem?
I run 2 different installations. And have absolutely no idea what could be the problem with having more.