sCalc | : calling : A simple calculator application | Form library

Groups are used in the Replacement parameter. Optional. The replacement text and references to capture groups. If there is no match, Text is returned unmodified.

Don't assign or use the predefined classes/functions/keywords as variables.

Use the modified code below:

To get the column index of the last populated cell, try the following array formula (arbitrarily assuming your data lives in row A1:ZZ1):

=MAX(IF(A1:ZZ1<>"";COLUMN(A1:ZZ1)))

The following array formula does the same, just with an additional translation of the column index to the column's name:

=SUBSTITUTE(ADDRESS(1;MAX(IF(A1:ZZ1<>"";COLUMN(A1:ZZ1)));4);"1";"")

This is a combination of the following sources (Credits...):

• Dirk Reichel's answer on Find Last Row Cell in Spreadsheets (CALC, excel) with formula, based on the last entry (text / number)
• John Sun's post on OpenOfficeForums Thread "Derive Column Letter from Formula"

To dynamically get the value of the last populated cell in Row 1, just embed the first formula into a INDIRECT(ADDRESS(1, )) clause. ADDRESS(1, ) creates a cell reference, INDIRECT() gets the value based on that cell reference. So, the complete (first) formula would look like this:

=INDIRECT(ADDRESS(1;MAX(IF(A1:ZZ1<>"";COLUMN(A1:ZZ1)))))

Complete example:

This does it. There were a couple errors. First, in Python you start counting at 0, so you wanted to use astring[2] instead of astring[3]. Also you needed a value to be returned:

With the given interface there is no benefit to compiling with /clr at all. Make the native C++ code debuggable by right-clicking your main C# project > Properties > Debug tab > tick the "Enable native code debugging" checkbox. That enables both the managed and unmanaged debugging engines. You cannot single-step into the native code, a breakpoint on the Calc() function is required to effect a debug engine change. You might still favor a unit test written in native C++ if setting breakpoints is awkward.

The other thing you need to take care of is that you're building the C++ code with Debug settings enabled. You got that now, that's why the code seems to be half as slow. Only do a perf test with Release build settings so you're sure that the optimizer is enabled. Best thing to do is to include the native C++ project in the C# solution so you always build the right flavor. And you have to make sure that the correct DLL gets copied into the C# main project's build directory, usually done with a post-build event. That copy step must be different for the Debug and Release configurations.

Note that the [DllImport] declarations are not correct. The return type of NewCalc() must be IntPtr so it also works in 64-bit code. Perf-testing the 64-bit build of the C++ code is something else you want to try, it can boost perf if the Calc() function uses floating point math. Actually using /clr can be useful to make the interface better, you'll however have to learn how to write C++/CLI code and avoid building the native C++ code with /clr.

Instead of using position: fixed to split the screen, use a flexbox. When you add lines to the textarea pane, the other pane will stretch as well, and you'll have a single scrollbar:

Option 1: You can actually convert multiple documents with just one execution of Open/Libre Office.. without a loop. Just use a wildcard, eg:

The parameters need to be reversed. From https://ask.libreoffice.org/en/question/2641/convert-to-command-line-parameter/:

soffice --headless --convert-to : file_to_convert.xxx

Using the old windows command prompt: