Entries in apesuite (17)


Delphi XE2 Update 4 Warning

There have been reports of problems with Delphi XE2 Update 4 and our components.  At this time it is our recommendation that if you are doing Firemonkey development and in particular if you use our components, that you remain on Update 3 for the time being.

We currently are not sure about the source of the problem but will publish more information when we have it to share.


Apesuite Beta 4 Released

We have today released Apesuite Beta 4.  This release includes a ton of bug fixes and three new components for your cross platform development pleasure.

New Components

  • TControlCombo - A combo box that pops up an embedded control.  The control can be any Firemonkey TControl descendant including a panel of other controls.
  • TObjectExplorer - A tree that shows the nested parent relationships of a target Firemonkey object.  It is useful in conjunction with the TDesigner component or on it's own if you just need to understand your form a bit better.
  • TPropertyInspector - A runtime property inspector for any firemonkey object allowing you to view and update properties of objects at runtime.  This works with the TObjectExplorer to view properties of nested objects not usually visible in the designer.


  • We completely overhauled our unit naming in Beta 4 to better organize for the future.  To find out the details, please visit our blog post from earlier this week on the subject.

New Features

  • The Pagebar now can render in a horizontal (ribbon) style or vertical (tool window) style.

Notable Fixes and Known Issues

  • TCard components are once again working both at designtime and runtime.
  • Wrapmode bugs in TSVG have been fixed.  There is still a clipping issue to be figured out when an SVG is scaled to a very small size where some drawing elements are inadvertantly being clipped.
  • Some TPropertyInspector edits are appearing to be readonly on Windows.  The same fields work correctly on Mac.
  • Many other minor bugs were fixed..


Current customers of Apesuite should have already received a new source code notification by email. New customers will automatically receive the latest version.



Awesome stuff with TSVG

Dominique Willems just wrote an excellent blog post regarding some of the cool stuff you can do with the TSVG component found in the Apesuite package for Firemonkey.


Head on over and take a peek.  Impressive stuff.


Apesuite Refactoring

I just wanted to give you all a heads up about some refactoring going into Beta 4 that will effect some compatability with prior betas.

The amount of components included in the Apesuite package has been growing, including the number of utility units, rc files and other stuff we need to keep track of.  Because of this, we're making some changes to the namespacing of our files.  

The plus side of this change is that it will make locating the correct units much easier and allow us to logically manage the expansion of our component portfolio.  The down side is that this is a breaking change and you will have to change your uses clauses when you update to Beta 4.  I'm hoping that this is the last big across-the-board change that we will have to make and I'd rather do it now than later when we will effect more people and have more projects effected.

The first new namespace will be as follows:


This namespace will include any visual Firmemonkey controls.  Here you will find units such as:

  • Ape.Controls.Cards
  • Ape.Controls.Pagebar
  • Ape.Controls.SmartImage
  • Ape.Controls.SVG
  • Ape.Controls.Designer
  • etc...

There is also a new namespace to hold any cross-plaform non-visual components that interact at the platform layer.  These will be system integrated components and as such the namespace will be:


Currently the only component that falls into this category would be:

  • Ape.System.TrayIcon

Our final namespace holds all of our Utility units:


Thesse units will be classes, functions, and generic designtime tools that we use internally by our other components.  While we supply this code in the suite, generally it is expected that it is for our internal use.  There is nothing stopping you from also using these in your applications, but we make no guarantee to their effectiveness outside of how we use them and will not generally support them outisde of how they effect one of our other components, so use at your own risk.  Some examples here are:

  • Ape.Utility.Bitmaps
  • Ape.Utility.CrossPlatform
  • Ape.Utility.RTTI
  • Ape.Utility.SAX

We know that we've added a bit of wordiness to the unit names, but believe the tradeoff is worth it. We have reduced our previx from ApeSuite.* to Ape.* to help combat that however.

Let us know if you have any questions about this change.

We are expecting Beta 4 to go out in the next couple days and it will again include some new components for your enjoyment.  Be aware that as the size of Apesuite grows, so will the price of the package.  We will continue to offer the beta discount while we are in beta, but soon the retail price will be going up a bit.  Buy now if you haven't already if you want to secure the lowest price possible for these components.  


Apesuite Beta 3 Released

Just a quick note to let you know that the previously announced Beta 3 has been released.  


Please see this entry for details: