Devart Forums

The XE2 designtime package dclodac160.bpl does rely on FMX and that is absolutely unnecessary. This dependency is going to be removed?

Hello,

Some designtime packages (like dclodac160) rely on FMX because our components can be used to create both VCL and FireMonkey applications. If we remove FMX dependency, you will not be able to use our visual components (such as TConnectDialog). The dclodac160 package is a designtime package and it is not included into your applications. Please explain why this dependency disturbs you.

AndreyZ wrote:Some designtime packages (like dclodac160) rely on FMX because our components can be used to create both VCL and FireMonkey applications. If we remove FMX dependency, you will not be able to use our visual components (such as TConnectDialog).

That is not true. The developer has and always had to add the OdacVcl unit explicitly to his project in order to see TConnectDialog or cursors. The same is true for FireMonkey projects and OdacFmx.

AndreyZ wrote:The dclodac160 package is a designtime package and it is not included into your applications. Please explain why this dependency disturbs you.

One reason is that FMX can be deselected in the XE2 installer. So we did on a machine as we have no plans for FMX applications in the foreseen future and all additional stuff slows down the IDE at some place. This will force us to rebuild the packages on our own.

Other reasons are that no one needs a FMX TConnectDialog to be shown in the IDE. The IDE is primary a VCL application and if a VCL version of a dialog/designtime editor exists for a non GUI component then the VCL dialog can be shown in the IDE.

Only one TConnectDialog is used right now in the IDE (either VCL or FMX), it seems to depend on the load order which one and so it happens that the FMX version is shown for a TOraSession in a VCL application. (Yesterday I got always the FMX TConnectDialog and today after ODAC re-install always the VCL version)

Furthermore (and if really necessary) making the FMX package optional should be possible.

Ok, we will investigate this question.

Are there any news on this topic?

According to the preliminary XE2 Update #4 release notes there are FMX interface changes in Update #4 and that could mean that the suffixes of the FMX packages will be bumped to 162. Well I guess you have as Technology Partner more reliable information, but if it turns out that the suffix gets bumped to 162 then version 8.1.4 is not compatible with Update #4 and users without source have to wait for your update before the can install Update #4. Of course changes related to the FMX dependency won't have any effect on 8.1.4, but maybe this helps you to understand the importance.

Hello,

We know about the swift release of Update#4, and we have already been testing our products on the betta-version. As soon as the official release comes off, we will release our products with the Update #4 support.

Where is the updated ODAC version?

Hello,

The new build with RadStudio XE2 Update 4 support will be released today or tomorrow

Hello,
I'm waiting fixup for RAD Studio XE2 Update4.
Do you think that today it will be release ?

Thank's.

Bye.

hello,

We are uploading all new ODAC builds to our site now. They will be available today. We will make announcements at our forum about the new builds.