We believe in listening to the voice of the customer. But to do that, we need you to speak. That’s what this Feature Request section of our site is for.

 

Here’s how to get your voice heard:

  1. VOTE for existing ideas (this will also subscribe you to the idea’s status updates)

  2. SUBMIT new ideas (Please include only one suggestion per post. Duplicates are merged together.)

  3. COMMENT on other ideas, which we check regularly

We also publish Roadmaps here, based off these Feature Requests, so you can see what we’re working on.

 

Note, this site is for new Feature Requests. Bug Reports should be emailed to Support as normal.

3 votes

Generate Enter/Leave calls using attributes on class or method level

On a pre-build operation the Enter/Leave calls may be generated automatically. [SiGenerateEnterLeave] // For all methods within this class Enter/Leave will be generated public class SomeClass { } [SiGenerateEnterLeave] // For this method Enter/Leave will be generated public void SomeMethod() { } SiGenerateEnterLeave may have parameters for the log level to be used or the […]

Category: SmartInspect > Languages > .NET 0 comments
3 votes

Automatic execution time for Enter/Leave sections

Enter/Leave sections (Method, Tasks, Threads, ..) could display automatically the execution time, which is often interesting and SmartInspect can display this without any effort of the developer. Execution time should be displayed in the enter and/or leave line in the log. I can provide you with an implementation in combination with my IDisposable feature if […]

Under Review Category: SmartInspect > Languages > .NET 0 comments
3 votes

Provide .NET IDisposable support for sections (Method, Task, Thread, ...)

Provide a section object for various section methods (e.g. Method, Task, Thread, …) replacing the Enter/Leave method combination and the try/finally construct for safely leaving an entered section. Then logging can be done easily and safely by a single statement e.g. using var _ = Si.Section.MethodSection(type); I have also added (see extra feature requests) * […]

Category: SmartInspect > Languages > .NET 0 comments
3 votes

Add composite filters to a view

The basic filtering mechanism is great, but often is would be even better if multiple filters could be applied to a view. For example: In a single view it would be great to see just warnings and errors in SessionA AND All SessionB messages except for those beginning with "Checking for" AND all logging from […]

Category: SmartInspect > Console 0 comments
3 votes

Add Ability to lock Views in console

Any time the console is exited, all views are lost. Or if one autogenerates a lot of temporary views like views filtered on a threadID one cannot deleted just those temporary views. I propose a context menu option to be able to lock the current view and a menu option to deleted unlocked view. Thus […]

Category: SmartInspect > Console 0 comments
2 votes

Console: View Time Filters

Add new filter conditions to console views for start and end time. When double-clicking on a thread in the Process Flow, the start and (if not currently running) end times should be applied to the created view so that only the log entries for that particular process thread will be shown. This will cut back […]

Category: SmartInspect > Console 0 comments
7 votes

Add Delphi FMX Multiplattform functionality

Currently leaving SiMain.Log… statements in our library code prevents compiling with FMX projects outside of windows platforms. $IFDEF workarounds in all our code files are no way we can go. This must change for us to extend our subscription and base our future code on SmartInspect. Many thanks in advance.

Started Category: SmartInspect > Languages > Delphi 1 comment
Scroll to Top