ForceFeedbackProgramming
ForceFeedbackProgramming copied to clipboard
robinsedlaczek
All calls to the ForceFeedbackMachine are now wrapped so that any exceptions will be caught and logged to a global error log (in the user's root folder): `.forcefeedbackprogramming.log` The logger...
The config file should be renamed to `.forcefeedbackprogramming`. This would follow the convention for config files in some other tools. A file with this name can exist on all levels:...
It is not clear what the certain parts of the source code mean. - What's the purpose of the ForceFeedback.Setup project? - What are the entry points (controllers) into the...
Add a "page" to the usual VS config editors. FFP configuration values then can be edited easily from within VS instead of fiddling with a JSON file. That way it...
Errors (exceptions) which happen during execution of the extension should be logged somewhere. Maybe in a VS window (eg error log). Or at least in a textual log file in...
Keys pressed (a-zA-Z0-9) will not be changed, but retarded. They don't appear immediately but only after a (short) while: ``` { "lines": 5, ... "keystrokeDelayms": 100 }, ``` With the...
Exclude single methods from feedback eg. by adding an attribute on top of them: ``` [ForceFeedbackProgramming(Check=false)] public void Do_sth(...) { //... } ``` Such exclusions could be useful during a...
Do not apply coloring and hampering equally to all functions. Exclude (or include) functions explicitly by through regular expressions. A reg ex can be applied to the fully qualified name...
Derzeit vermischt die Assembly `ForceFeedback.Rules.dll` zwei Verantwortlichkeiten: - Zum einen ist sie Schnittstelle zur Umwelt; sie kapselt den VS Extension API. `MethodTooLongTextAdornment{}` ist der Handler für Ereignisse, die in VS...