Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » Elevate Web Builder Technical Support » Support Forums » Elevate Web Builder General » View Thread |
Messages 41 to 50 of 73 total |
What's Coming in 2.05 |
Thu, Mar 31 2016 3:02 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Just a quick note on the progress with 2.05. I finally got a major problem solved that was causing some of the delay, and so things should be progressing to a finish in the next couple of weeks with the final code updates and doc changes/release notes on the breaking changes.
The problem has to do with how intra-form/database component references were handled. I don't like the way that Delphi does this, so I needed to come up with a way to allow for component references to appear/disappear without breaking any linkages between forms/databases. So, as a bonus, 2.05 will allow you to link up components on different forms, but without any of the negative aspects of this that can happen with Delphi in terms of not allowing one to close certain forms due to the links, etc. Tim Young Elevate Software www.elevatesoft.com |
Fri, Apr 1 2016 4:22 AM | Permanent Link |
Godfrey Ultimatesoft | Sounds good looking forward to it
|
Fri, Apr 1 2016 10:23 AM | Permanent Link |
Bruno Larochelle | "like!"
Tim Young [Elevate Software] wrote: So, as a bonus, 2.05 will allow you to link up components on different forms, Bruno Larochelle Logiciels Bitwise Software Edmonton, AB, Canada |
Tue, Apr 5 2016 5:25 PM | Permanent Link |
Trinione | << The problem has to do with how intra-form/database component references were handled. I don't like the way that Delphi does this, so I needed to come up with a way to allow for component references to appear/disappear without breaking any linkages between forms/databases. So, as a bonus, 2.05 will allow you to link up components on different forms, but without any of the negative aspects of this that can happen with Delphi in terms of not allowing one to close certain forms due to the links, etc. >>
Tim, Does this mean that it would no longer be necessary to (1) reselect dataset Events, (2) reselect dataset Colums (GetText/SetText), and (3) reselect Properties on related components? |
Tue, Apr 5 2016 6:34 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | << Does this mean that it would no longer be necessary to (1) reselect dataset Events, (2) reselect dataset Colums (GetText/SetText), and (3) reselect Properties on related components? >> What do you mean by "reselect" ? And, as far as events are concerned, they are *not* covered by what I've described, only component references such as the DataSet property for controls that can be bound to datasets. Tim Young Elevate Software www.elevatesoft.com |
Wed, Apr 6 2016 1:43 PM | Permanent Link |
Trinione | << What do you mean by "reselect" ? >>
<< And, as far as events are concerned, they are *not* covered by what I've described, only component references such as the DataSet property for controls that can be bound to datasets. >> Tim: By 'reselect' I mean having to double-click on say the GetText even for it to be 'connected' again. Same with any other Event on the DataSet itself. For example the AfterLoad and OnLoadError. Seems you answered by saying that are not covered. Is there any way to have EWB search the code and reset this automatically? Having to record, recall or remember each event per dataset is error prone as you can imagine. |
Wed, Apr 6 2016 1:43 PM | Permanent Link |
Trinione | << What do you mean by "reselect" ? >>
<< And, as far as events are concerned, they are *not* covered by what I've described, only component references such as the DataSet property for controls that can be bound to datasets. >> Tim: By 'reselect' I mean having to double-click on say the GetText even for it to be 'connected' again. Same with any other Event on the DataSet itself. For example the AfterLoad and OnLoadError. Seems you answered by saying that are not covered. Is there any way to have EWB search the code and reset this automatically? Having to record, recall or remember each event per dataset is error prone as you can imagine. |
Wed, Apr 6 2016 1:43 PM | Permanent Link |
Trinione | << What do you mean by "reselect" ? >>
<< And, as far as events are concerned, they are *not* covered by what I've described, only component references such as the DataSet property for controls that can be bound to datasets. >> Tim: By 'reselect' I mean having to double-click on say the GetText even for it to be 'connected' again. Same with any other Event on the DataSet itself. For example the AfterLoad and OnLoadError. Seems you answered by saying that are not covered. Is there any way to have EWB search the code and reset this automatically? Having to record, recall or remember each event per dataset is error prone as you can imagine. |
Wed, Apr 6 2016 1:43 PM | Permanent Link |
Trinione | I swear I hit 'Post' once.
|
Thu, Apr 7 2016 8:02 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | << By 'reselect' I mean having to double-click on say the GetText even for it to be 'connected' again. Same with any other Event on the DataSet itself. For example the AfterLoad and OnLoadError. Seems you answered by saying that are not covered. >>
In what scenario are you wanting this to automatically occur ? The description that I gave above was for component references across form instances, ala setting the DataSet property for a TEdit to be "Form2.MyDataSet" instead of only allowing "MyDataSet" from the current form instance. Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 5 of 8 | Next Page » |
Jump to Page: 1 2 3 4 5 6 7 8 |
This web page was last updated on Monday, April 29, 2024 at 05:23 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |