Forum Replies Created
-
Posts
-
Because of the awful mess this forum system makes of the user’s contributions, I had to redo the change request in #69317
I have made this into a change request: #69315
Don’t remember exactly but I had to put a comment here:
procedure TsAlphaHints.OnCheckTimer(Sender: TObject); begin ... // Lasse Application.HintPause := Manager.FOldHintPause;Otherwise I could not change it.
Which shows, timing of hints needs a overhaul.
At the end ofprocedure TsShowTimer.Init(HintForm: TacCustomHintWindow; w, h: integer);there is a very suspicious:
Application.HintPause := 100;I was mistaken. I changed the value form 5000 to 10000, to get a longer reading period.
That means two timing value properties could be added: the time for a first hint to appear (HintPause), the time between hints if moving over controls (HintShortPause).
The Application hint values can be set but they would be nicer as properties of TsAlphaHints.As far as I can remember on my holiday, the 500 msec delay is the only timing that can be adjusted in TsHintManager. I have changed it to 1000. But that timing is not honored anymore, after the first time a hint is shown.
VCL has a lot of events implemented, but thre is no special properties for enabling/disabling them…
I’m not sure what you mean by that
<p zoompage-fontsize=”14″>The RefreshAcceptedDates procedure will be available in the v15.14
Behavior of the ChecksActive is not obvious. Do you suggest to enable/disable calling of the OnAcceptDate event by this property?Yes. It gives the best of both worlds: 1. By setting it False at design time, no initial OnAcceptDate events will occur. Then setting it to True, it will do an OnAcceptDate for every day in that month. Leaving it to True, the TsMonthCalendar functions as it is now. But if you want all dates rechecked, set the property to False and to True again.
No, this behavior is far from standard. Start an Explorer window and hoover over the top buttons. There is a delay of two seconds between the showing of the hints. In your implementation this is 0.1 second.
I get the AV almost every time.
However I’m not able now to reproduce it in a simple sample project.
The enclosed project shows what the setup is. It uses a ShowPopupForm but this was a ShowModal. In both cases things went wrong.
In this simple project I cannot reproduce it, unfortunately.I ran it in Delphi XE4 with debugging on and I received at least 10 in each configuration.
Very nice utility.
But I have no problems.
It makes no difference, 32 bit, 64 bit, with or without debugging: it’s always 10, sometimes starting off as 9.Even if setting OnAcceptDate to non-nil would force a recheck of all month dates, there’s still the need for a RecheckCalendar procedure, in cases where the dates acceptable have changed.
By the way, setting OnAcceptDate to non-nil in code, does not recheck the dates as you would expect.
I say that, because that would also be a feasible solution: having the OnAcceptDate being set to nil normally and only set it to a checking procedure when you need that. But then checks should be redone at that moment.On second thoughts, a better solution would be a published property ChecksActive. That would be True by default, but being published can also be initialized to False. When False, all dates are OK and no calls to OnAcceptDate are done. When set to True, it will call OnAcceptDate for all dates in the current month and keep on working like it is now.
The benefit of this over a ReloadCalendar procedure would be that it will prevent 30 checks at component load time (a possibly costly operation), that would not lead to anything sensible any way.
