Welcome to the SRP Forum! Please refer to the SRP Forum FAQ post if you have any questions regarding how the forum works.
KevinFournier
About
- Username
- KevinFournier
- Joined
- Visits
- 2,163
- Last Active
- Roles
- Administrator
Comments
-
A web browser isn't very useful for editing text. Regarding my suggestion. When you said it would be weird to see the text is two places, I think you misunderstood me. I was suggesting you do not show the notes in their entirety (or possibly at all…
-
I think the SRP Tree Control will be worse. It is even more limited on how it displays information, and it's editing capabilities are very limited in scope. When it comes to free-form text, the best control is an EditBox. I'd use your table above, …
-
I see. So, part of the problem is that you have really huge rows, which makes it scroll oddly. Going with multiple rows is going to be a trade-off. It will scroll better, but then you'll lose the convenience of multlilined cells. If you go the route…
-
If you install our free SRP Utilities, there is a stored procedure called SRP_String. It has a feature called GetHeight that will measure the height needed to fit a string based on the font being used.
-
The table is not designed to scroll that way. It scrolls row by row. This is to account for the potential for very large data sets.
-
That's the runtime for the version of C++ I used. Very odd that it wasn't already on the machine since it dates back to Visual Studio 2013. The only OS I've come across that usually is missing it is Server 2008.
-
Yes, there are always errors, but that's usually at the lower level. The main thing you want to look at are the DLLs immediately beneath SRPControls64.ocx. That error is suggesting that our OCX uses a particular method that doesn't exist in the ver…
-
I want to let you know that I have not dropped the ball on this. My silence is an indication of the many days I've put into tracking this issue down, yet it is proving wildly elusive. There seems to some conflict between the table's use of the Win64…
-
It is probably missing needed dependencies, which is odd since Windows 10 Pro should have everything needed. You might need to use Dependency Walker to see if there are DLLs it needs that are unavailable on this machine.
-
Currently, that feature doesn't do anything. The third-party control up which the Ribbon control is built, assumes there is a lot more framework in place. One possibility is to fire an event when the user clicks that option, allowing you--the devel…
-
You need to put "q" and "a" into the same cell. The cell containing "a" is hidden by the merging. The CellMerge property extends the target cell (e.g. cell 1;2) to cover up the cells requested (e.g, 7 columns and 2 rows). It does not merge data beca…
-
I see. There should be a DLL_SRP_USER32 record in the SYSPROCS table with the DLL stubs we defined for the SRP_Registry module. You could use that to create new stubs that will allows you to pass raw binary data to the APIs. But it will require you …
-
We have this feature in use in several applications, so this crashing is truly unexpected. I will need your table setup code to see what might be at play here.
-
No. Only strings are supported right now. Supporting binary will require additional DLL stubs. The registry is also not the ideal place to store data these days. Microsoft asks developers to simply store files into the user's app data directory.
-
The SRP Ribbon Control is hardwired to be at the top of the form. This is because, in addition to displaying buttons and tabs, the ribbon also takes over the form's title bar and edges to provide a more advanced look and feel. We've typically use t…
-
The SRP SplitterBar Control is only really useful when you want to let the user resize controls on a single form. Since your side bar is it's own window, I don't think the splitter will be useful. If the title is still appearing after unchecking it…
-
I'm looking into this. We've discovered a similar issue in OI 9 with EditTable buttons. They aren't responding to left clicks but are responding to right clicks. I'll get back to you with a fix as soon as I can.
-
There was a bug in the algorithm that determines what physical columns map to what abstract columns. 4.1.3 RC1 fixes it.
-
My guess is that changes in OI 10 do not let us destroy the window using the WinAPI, which is RemoveForm is trying to do. I recommend trying the following steps: * Set the form's VISIBLE property to 0 * Call RemoveForm with the Destroy paramete…
-
The short answer is no, we haven't experienced this, but we don't have any OI 10 systems in development at the moment using SRP Panel. Just so I get a clear picture. You are creating a whole form dynamically and using SetForm to embed it into the P…
-
I'll add that @DanielStieber's method will force OI 10 to behave like OI 9 in that it will cause Windows to scale the entire application automatically using bitmap scaling. So, it won't be as sharp, but all our controls will scale with the rest of t…
-
I guess that makes sense. Changing DPI to 100% will just make everything else smaller so it looks correctly proportioned. The reason OI 9.x looks bigger is because OI 9.x is not DPI aware, so Windows just scales everything up. But OI 10 is DPI aware…
-
My guess is setting the DPI to 100% instead of 200% will fix the problem, but then everything will look minuscule on your Surface.
-
SRP Controls are not DPI aware, so that will be an issue. There is no ETA on DPI awareness since it would require a major refactoring of all our controls.
-
Everything you need to make http calls is in the HttpClient class. Like all the newest C# features, everything is Async. So, if you aren't familiar with the async/await syntax, I highly recommend you get good with it. Everything in C# is using it n…
-
I will need more information. The following code: Set_Property(Ctrl, "OLE.Dimension", 5) NumRows = 140 Data = "" For i = 1 to NumRows Data<1, i> = "Row ":i Next i Set_Property(Ctrl, "OLE.ARRAY", Data) For i = 1 to NumRows step …
-
You were right. There was an overflow error that we never caught (since we always use RowsToRecords). It is fixed in 4.1.2 RC12.
-
Is the goal here to make every two rows behave as one logical record? If so, the table is designed to automate that scenario. The rule of thumb is this: if you are putting logical records into the table, you should always set the RowsToRecords prope…
-
I see. Been there myself a time or too. I would have loved it if we could have used periods. At any rate, it prompted me to improve the documentation, so the discussion was valuable. Thanks.
-
Not exactly. The SpinButton property adds the spin buttons to the control, but if you set SpinButton only, then there is no automation. You must also set SpinRange if you want automation. Otherwise, you'll get the OnSpinClick event.