Navigation:
ffDiaporama for Linux 6.10.0.0 freeware
New
Version
ffDiaporama for Linux Free Download - we do not host any ffDiaporama for Linux torrent files or links of ffDiaporama for Linux on rapidshare.com, depositfiles.com, megaupload.com etc. All ffDiaporama for Linux download links are direct ffDiaporama for Linux download from publisher site or their selected mirrors.
| 6.10.0.0 | Jan 31, 2025 | New Release | Less noisy file diffs: Before, file diffs were noisy because a small change in your solution caused a lot of changes in the files on disc. This was mostly due to Services, in particular the SimpleREST and RESTHost, regenerating IDs unnecessarily. For example, updating a RESTHost API definition where only the title changed, caused all the result type IDs to also be regenerated. Stopping a test run stops ASAP: Previously, if you clicked the stop button when running tests in the Test Explorer, the test would stop as soon as it was completed. This approach was problematic, specifically in cases where a test went into a long-running or unforeseen infinite loop. This was improved so that after clicking stop, only the currently running function inside the test is completed instead of the whole test itself. Solution history uses less physical disk space: Over time, uploading new versions of solutions resulted in an unreasonably large history folder on the physical disk, causing space issues in environments where Linx ran. Now, to reduce space usage, only the full history of the latest three versions is kept, and the rest of the solution's history is summarized Deleting a solution is permanent: When a solution is deleted, all traces of it are removed from the disk. This prevents outdated and unused files from being stored on disk, which over time leads to space issues. Various other GUI fixes, bugs and enhancements: Updated the certificate of the installers Designer: Removed Newtonsoft.Json library from the Linx designer Import Type editor now disables the Save button when data is entered TryCatch function now logs to Debug Output The Function result is logged to the Debug Output, irrespective of whether it is null or not Fixed an issue in the Debug Values pane where the Values editor changed an integer to a string Fixed an issue where the expression editor failed to test an expression due to missing assemblies Fixed an issue where the Designer crashed when a function was se |
| 6.9.5.0 | Oct 17, 2024 | New Release | Values Editor: Very wide values push the dropdown buttons out of view: The Values Editor pushed the property labels, editor button and dropdown arrow out of sight when the values were wider than the window. This issue has been fixed. Changing a setting value back to null in the Designer did not reflect the value in the UI: When you had a value in the textbox, cleared it, and then pressed Ctrl+0, the value was set to null but did not reflect in the Designer. This issue has been fixed. Find References does not list types used in function parameters: When a function had a parameter or result of a custom type, executing "Find References" in the Linx Designer would not list these occurrences. Now it does. Running tests causes an InvalidOperationException (Stack empty): Some processes in the Process Automation plugin service are run in different threads which, at times, caused an InvalidOperationException to occur when tests were run repeatedly. This was fixed. Copy-pasting a Function causes a "...type does not correspond..." validation: This issue was quite specific and occurred when copy-pasting a function whose result was a custom type. That type, in turn, contained a property whose type pointed to another custom type. Copy-pasting this function caused the Return's value to contain the incorrect type. URL highlighting in Debug logs: The Debug Logs did not always highlight URLs in full. This has been fixed. Return converts certain characters to Unicode: Certain characters were converted to Unicode before being returned from a function, e.g. > was converted to u003E. This was fixed. Changing debug parameter values before each run: In versions of Linx 6.8.4 and earlier, the single-threaded Debugger allowed you to specify the values for the function parameters before every debug run. A bug in later versions only allowed you to specify the parameter values on the first debug run. To change the parameter values after the first run, you had to restart t |
| 6.9.3.0 | Sep 4, 2024 | New Release | Values Editor: Very wide values push the dropdown buttons out of view: The Values Editor pushed the property labels, editor button and dropdown arrow out of sight when the values were wider than the window. This issue has been fixed. Changing a setting value back to null in the Designer did not reflect the value in the UI: When you had a value in the textbox, cleared it, and then pressed Ctrl+0, the value was set to null but did not reflect in the Designer. This issue has been fixed. Find References does not list types used in function parameters: When a function had a parameter or result of a custom type, executing "Find References" in the Linx Designer would not list these occurrences. Now it does. Running tests causes an InvalidOperationException (Stack empty): Some processes in the Process Automation plugin service are run in different threads which, at times, caused an InvalidOperationException to occur when tests were run repeatedly. This was fixed. Copy-pasting a Function causes a "...type does not correspond..." validation: This issue was quite specific and occurred when copy-pasting a function whose result was a custom type. That type, in turn, contained a property whose type pointed to another custom type. Copy-pasting this function caused the Return's value to contain the incorrect type. URL highlighting in Debug logs: The Debug Logs did not always highlight URLs in full. This has been fixed. Return converts certain characters to Unicode: Certain characters were converted to Unicode before being returned from a function, e.g. > was converted to u003E. This was fixed. Changing debug parameter values before each run: In versions of Linx 6.8.4 and earlier, the single-threaded Debugger allowed you to specify the values for the function parameters before every debug run. A bug in later versions only allowed you to specify the parameter values on the first debug run. To change the parameter values after the first run, you had to restart t |
