From: Michel L. <mic...@kd...> - 2006-08-27 20:02:39
|
On Sun 27 Aug 2006 15:25, Jeroen Wijnhout wrote: > If you add actions for each script then the shortcuts will be configurable > through the common shortcut configuration dialog. I was > wondering why you didn't use normal shortcuts for scripts. The key sequence approach was a (local) user wish. For the configuration of how a specific script is called, I'll then use a dialog where the user can either enter a key sequence or a regular shortcut. The shortcut configuration will be less sophisticated than in KShortcutDialog though. (the user can still use the normal configuration dialog to have advanced configuration options) > You can also take a different approach: When creating a new script let the > user choose a name, say Script. When > you have the name you can automatically save a file to > $KDEHOME/share/apps/kile/scripts/Script.js. It is probably > difficult to change the default directory of the save file dialog, because > this is controlled by the KatePart. Oh, that would also have been a nice idea ! :-) But this morning, I found a different solution: one can bypass the katepart save function by reconnecting the save action to a different slot. So, it works now and I'll also do some cleanup of the functions that check whether the selected file name is valid. By the way, is the space character still problematic for LaTeX file names ? Otherwise that character could be removed from the containsInvalidCharacters method in kdocumentinfo.cpp. (in FC5, it works nicely with spaces in file names). Greetings, Michel |