Raul wrote:

 // On 1/31/2017 9:57 AM, Uli Becker wrote:
 // > Error at runtime when a TCalendar (or TDateEditComboBox) control is used:
 // > Designtime works fine.
 //
 // Can't duplicate it here - setting it design or runtime to various dates
 // seems to work for me.
 // Raul

As Uli I get errors with TDateEditComboBox. When loading an existing form containing a
TDateEditComboBox an IDE exception (see picture 1).
The *.wbf part:
In der *.wbf:
           { "ClassName": "TDateEditComboBox",
              "Name": "edExpenditureDate",
              "Properties": {
                 // ...
                 "Text": "11\/26\/2016",               <<<<-------
                 "OnChange": "edExpenditureDateChange" } },

When creating a new project/new form a runtime error (picture 2, 3).
The *.wbf part here:
     "Controls": [
     { "ClassName": "TDateEditComboBox",
        "Name": "DateEditComboBox1",
        "Properties": {
        // ...
           "Text": "1.31.2017" } } ]      <<<<<---- format is fifferent as above
      }

My region settings are shown in (4).

Michael Dreher

Thanks for the tip about changing the interface, Uli. I was able to achieve the desired effect by editing the interface for TMenu and TMenuItem.

Uli Becker wrote:

> I can't seem to change the colour of TMenu from the default gray. The setting for Background...Fill...Color does not change the colour.

In 2.05 TMenu didn't have a published property "Background". If you wanted to change the color you had to change the TMenu interface..

On 2/2/2017 3:43 AM, Michael Dreher wrote:
> As Uli I get errors with TDateEditComboBox. When loading an existing form containing a
> TDateEditComboBox an IDE exception (see picture 1).
> The *.wbf part:
> In der *.wbf:
>             { "ClassName": "TDateEditComboBox",
>                "Name": "edExpenditureDate",
>                "Properties": {
>                   // ...
>                   "Text": "11\/26\/2016",               <<<<-------
>                   "OnChange": "edExpenditureDateChange" } },


This is the default format (M/d/yyyy) that EWB uses for format - i
wonder if IDE design time uses the OS (i.e. delphi) date parsing !?


> When creating a new project/new form a runtime error (picture 2, 3).
> The *.wbf part here:
>       "Controls": [
>       { "ClassName": "TDateEditComboBox",
>          "Name": "DateEditComboBox1",
>          "Properties": {
>          // ...
>             "Text": "1.31.2017" } } ]      <<<<<---- format is fifferent as above
>        }
>
> My region settings are shown in (4).

This is little more weird - if i'm reading your OS settings then your
format there is is Day.Month.Year for the short date but this one is
showing Month.Day.Year from what i see.

Looks like something in IDE design mode as my guess again.

For the new project - can you set the FormatSettings ShortDateFormat and
dateseparator and see if that gets rid of the error ?

for example in Form create you can do something like this this  :

procedure TForm1.FormMainCreate(Sender: TObject);
begin
   FormatSettings.DateSeparator = '.';
   FormatSettings.ShortDateFormat := 'd.M.yyyy'; //or try M.d.yyyy  also
end;



Raul

Uli,

<< Error at runtime when a TCalendar (or TDateEditComboBox) control is used:

Persistent load error (Persistent load error (Invalid date (1/30/2017))) line xxx

Designtime works fine. >>

I'm not seeing that here.  Did you change your format settings at all so that the date format isn't mm/dd/yyyy ?

Tim Young
Elevate Software
www.elevatesoft.com

Uli,

<< I didn't investigate that further - need much time to adjust all my custom interfaces. Tried to "merge" them with BeyondCompare, but there were to many hassles and errors. Thus I prefered to recreate them. >>

Just a heads-up, but there are some performance issues with the amount of auto-sized icons, captions, etc. in the existing control interfaces, so I'm having to go back through and modify all 260+ of them.

So, you're going to see almost every single one of them change between the first and second beta releases...

Tim Young
Elevate Software
www.elevatesoft.com

<< I can't seem to change the colour of TMenu from the default gray. The setting for Background...Fill...Color does not change the colour. >>

This is now fixed, you have to change the TMenu control interface so that it's Client element's Background.Fill is not clWhite, but rather clTransparent.

Tim Young
Elevate Software
www.elevatesoft.com

Walter,

<< TImage - Changing Opacity in design time, in IDE does not take effect.  But if you then change another property like Height - then both will change. >>

This is now fixed.  It was broken during the painting optimizations where I was weeding out as many extraneous repaint triggers as I could, and I got a little carried away.

Tim Young
Elevate Software
www.elevatesoft.com

Chris,

<< 2)   The TImage OnClick event doesn't appear to fire any more. >>

This is now fixed.

Tim Young
Elevate Software
www.elevatesoft.com

Raul,

<< Looks like something in IDE design mode as my guess again. >>

The design-time uses the same code as the run-time - the WebCore DateToStr() / StrToDate() functions, which are all coded to use the FormatSettings property settings.

What changed in 2.06 was this:

http://www.elevatesoft.com/incident?action=viewrep&category=ewb&release=2.05&incident=4443

and somehow it is interacting with the different FormatSettings to cause this issue.

I suspect the issue is that code is getting pulled in to the component library that is changing the global FormatSettings at design-time, and that is causing the issue with the different date format getting used to generate the Text property.  In general, we don't want the FormatSettings changed in the component library because of possible issues with date <--> string conversion during form loading.

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<
I'm not seeing that here.  Did you change your format settings at all so that the date format isn't mm/dd/yyyy>>

No. As I answered Raul's question: new project, no settings, just a form and a calendar control.

Uli