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,106
- Last Active
- Roles
- Administrator
Comments
-
Sorry, not allowed. While dimensioned matrixes are faster, they are rarely used in BASIC+. That is because the original dynamic array has to be linearly scanned anyway and there are ways to do that while also processing the array. Wanna walk a dyna…
-
It's a cool idea, but there are some considerations. You have to register your application's AUID and a COM object to handle the user interacting with the toast. That means you need an installation process of some kind that runs with elevated permis…
-
Glad it's working. You can get away without using MDISize if you don't ever set the MDICLIENT SIZE property after the frame is created.
-
CtrlId = @Window:".MDICLIENT" Handle = Get_Property(CtrlId, "HANDLE") Send_Message(@Window:".OLE_SUBCLASS", "OLE.Subclass", Handle, CtrlId)
-
I have a fix that comes with caveats. You have to use MDISize to set the size of the MDICLIENT and you have to subclass the MDICLIENT using the SRP Subclass Control. Those combined should prevent the resizing and flickering.
-
I've got an inquiry in with Rev to see if this is something I have to work around or unintended behavior on their end.
-
We've recreated this on our end. I'll keep you posted.
-
Are you using the MDISize property to set the client's size during the CREATE event?
-
Here's my first go at it.
-
I'm in contact with Revelation to see what I can do to make this work. I'll keep you posted.
-
Yes, you'll be able to have a procedure appear in any number of projects. I hear you. As a Visual Studio user, I'm used to doing easy side-by-sides as well. I'll be giving this some thought on how I might pull this off. No guarantees, but this idea…
-
Good timing as I am working on SRP Editor 4.0 as we speak. The Favorites panel is on my todo list. I've already discussed moving to a project-based panel with Don, and he's on board with the idea. Will that meet the need you're after? As for side-b…
-
Oh, sorry. My bad. The control itself is allowed to be invisible. I've had a long day. I was thinking you were trying to disable the Ribbon temporarily. I'll look into it. Even when it's not visible, the Ribbon is supposed to hide itself.
-
I'll take a look, but truth be told, you're in uncharted waters. The Ribbon has to override the entire form in order to work, so hiding it was not part of the plan.
-
@Opto_Will. I just added this feature. See above.
-
Don, the toolbox is created each time you open a form. It's a new window every time, with a unique window handle. So, you'd have to run that routine every time you open a form.
-
Try initializing the ribbon with at least one tab. Don't worry about the Form Designer positions. Once you elect to use the Ribbon control, WYSIWYG design support is pretty much gone. It all has to be done in code.
-
So, this is a Form Designer screenshot, correct? Are you saying the above code does not work when running the form? Do you have a screenshot of that?
-
I'm not sure I can answer without seeing any code. This is what we do in FrameWorks' CREATE event. Size = Get_Property(@Window:".OLE_FRAME_STATUS", "ORIG_SIZE") Left = "0" ; // Achor left to client left Top = -Size<4> ; // Use control's…
-
Man, the ideas you guys put in my head. If you download OCX version 4.2.5.5 and register it, it will resize the toolbox IF there is an SRP OLE control somewhere on the loaded form.
-
There is no convenient fix. I think I found a program years ago that can resize a window, but you have to run that program every time you open the Form Designer. It never felt worth it.
-
Use the Ribbon's LayoutChildControl method to tell it where to put the other controls in relation to the ribbon.
-
Not here. It's not exactly a 1-to-1 comparison anyway.
-
Hmm, this is even more informing. When you set the color in the DB Manager, it sets the background color directly into the SYSREPOSWINEXES records for all windows, not just the ones that are set the the Default color. This is why, when you open the …
-
Awesome. Then their OS installation is bad. Time to repair or upgrade.
-
The 64-bit version has code specific to DPI, but even though that is "extra stuff", note that in Windows, there are 32-bit and 64-bit versions of all kinds of DLLs. There are numerous ways 64-bit could fail while 32-bit does not. One way to check is…
-
Our installer installs these runtimes for you, by the way. So, if you've used our installer, it should have everything you need. I suspect this server is simply missing some dependencies, which can happen for a host of reasons. Upgrading out of an u…
-
The point I was making is that the SRP Editor is set to the system form color, which is done in the Form Designer by going to Properties->System Color->Default. The fact that it was set to LIGHT BLUE in the SYSREPOSWINEXES is telling. My guess…
-
SRP Table Search is not subclassed, but it does set the color of the form to white in the Form Designer. The SRP Editor, since it has a tab control, is subclassing the form, but it defers rendering of the background to OI. The background color of th…
-
Wish granted. If you download 4.2.4 from our products page, that installer will let you choose to not install either OCX.