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,233
- Last Active
- Roles
- Administrator
Comments
-
Relaying denied happens when you are considered an unauthorized user. While this is most commonly due to an incorrect username/password, it can also happen when your credentials are fine but the server has decided for any number of reasons that you …
-
Used "LT" instead of "LE", rookie mistake. It's a good thing you're a better tester than me. This one should do the trick.
-
Try this one.
-
Try starting the child window using Start_Window. During it's CREATE event, set the parent's ENABLED property to 0. During it's CLOSE event, set the parent's ENABLED property to 1. If ENABLED doesn't work, you can try calling the Win32 EnableWindow …
-
You can try qualifying the WM_PASTE$ WNDMSG event and doing nothing with it. Equ WM_PASTE$ to 0x0302
-
Try replacing the FindWindow line with: Handle = Get_Property("SRP_EDITOR", "HANDLE")
-
This OCX should fix it. (@DonBakke, jinx)
-
SRP Editor 3.3.1 can be downloaded here. The Find/Replace windows no longer do autocomplete. We agreed that it was causing more problems than solving them. The dropdown is still available, but you can now type whatever you want.
-
Hmmm, I can't recreate this in 9.4.1. I've seen strange rendering behaviors with controls inside group boxes, which are usually resolved by moving the group box in the tab order. Just checkboxes on a clean form though, I can't seem to cause this iss…
-
Are these check boxes inside a group box or tab control?
-
This is a bug in OI 10. For some reason, handles cannot be assigned directly into dynamic array fields. Doing so corrupts the handle. I believe this will be fixed in the next release of OI 10.
-
Yes, in the Ctrl+O dialog.
-
I can confirm that this method works. The SRP Editor relies on it heavily. I'd have to see code to diagnose the problem further.
-
Oversight on my part. Try this one.
-
Thanks for catching this. Fixed.
-
Try this one. This should also fix the scrolling issues you mentioned here.
-
It's not an SRP message. Without knowing what was happening when the error occurred, it's a guess as to the source.
-
I don't see the time bar messing up, but I noticed some minor scrolling issues, which I fixed in this build. If you can give me more information, I'll follow up and see what I can do.
-
So, I am a silly man. There is already a property for formatting the date, but forgot to document it. Shame on me. It's called DateHeaderFormat and it should work in the version you have. Also, you can do what you suggest in srp5. There is a thir…
-
Every element in the Layout property defines where that item will appear in the appointment. Merely deleting the start and end times doesn't change where the DESC item appears. See the Location element of the Layout property. I'll see what I can do…
-
Download this version and re-register the OCX. It has a new property called TimeBarAMPM. Set it to 0 to Netherlandize your timebar. :) Set_Property(@Window:".OLE_SCHEDULE", "OLE.TimeBarAMPM", 0)
-
Yes, I realized what you meant after I posted. I'm working on a new property that will toggle 24-hour notation. How do you typically render midnight? 0:00? 24:00? Or either way?
-
I should also add, the default view (SingleDay) is the most used and therefore the most robust. MultiDayHorz is also well vetted. No one ever uses SingleDayHorz, and it's admittedly buggy. I know, I know, I should have more pride in my work, but whe…
-
You want to experiment with the Layout property, which allows you to define where data elements appear, how they are rendered, and--most importantly to your cause--how date & time are formatted. The easiest way to get started is to read the Lay…
-
The answer is yes and yes. It is a bug, but views were also designed to be set-and-forget. If I can recreate the bug, I'll fix it to be sure.
-
This version should fix the crash. Thanks for the details.
-
Use TimeBlockList instead. EntityTimeBlocks is deprecated because it wasn't flexible enough. TimeBlockList has a slightly different format. I'll update the wiki to make it clear that EntityTimeBlocks is deprecated. Sorry about that.
-
I need more to go on. There might be a specific setup that leads to this, but as it stands, I can't get this to crash for me. You can email me your setup (no need to include actual appointments) or a simple RDK recreating the issue.
-
Not expected. Try this one.
-
I'm working on this now, so it'll work better in the next version.