After the latest Windows 10 upgrade cleared all of my Textpad settings, I have been feeding them all back in again. However,
* Find in files now does nothing at all.
* The List option in the keyboard mapping setup also does nothing.
* Same for Compare Files.
I assume there is something wrong with the running of the embedded commands or the capturing of their output.
Where do these commands actually run?
Do they need a specific directory to use?
Are there any other settings I could check?
I have version 7.6.3
Find in files does nothing
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
Re: Find in files does nothing
This is causing me all sorts of grief.IanOfYork wrote: Find in files now does nothing at all.
Anybody got any ideas?
By "Nothing at all" do you hit the button and never see the dialog box? Next question, have you recently altered your screen resolution, or connected another monitor? If yes, then it's a known pain in the rear. Select or click find (You would then expect to see a dialog box pop up), then try Alt+Space, M Then you are moving the box.
Alt+Space opens system menu, then M Moves it, try/practice on a different application if I haven't made sense.
Not complaining, and Textpad is the best, but the dialog box must have an OnShow event. I don't understand why it can't check it's on the screen.
Alt+Space opens system menu, then M Moves it, try/practice on a different application if I haven't made sense.
Not complaining, and Textpad is the best, but the dialog box must have an OnShow event. I don't understand why it can't check it's on the screen.
No output
Sorry ... The dialog box asks all the right questions, but then pressing "Find" does nothing.
It is responding to the click.
It just fails to do anything.
Other tools that would output to a new view (such as compare files) also do nothing.
Also, changing one of the existing (working) tools to Capture Output then kills the tool.
It is responding to the click.
It just fails to do anything.
Other tools that would output to a new view (such as compare files) also do nothing.
Also, changing one of the existing (working) tools to Capture Output then kills the tool.
Fixed it although I have no idea how ...
Having no config file must have "reset something", but that is hardly a valid diagnosis.
- Closed Textpad
renamed ConfigState.xml to saved-ConfigState.xml
Opened Textpad
Tools output still fails
Closed Textpad
renamed saved-ConfigState.xml back to ConfigState.xml
Opened Textpad
Tools output now works
Having no config file must have "reset something", but that is hardly a valid diagnosis.