Exactness: initial commit.

(Commit message by TAsn):
Exactness is a pixel perfect test suite for elm/evas/edje.
Exactness lets you write tests, and then record a specific interaction
with them, while taking windowshots in the process. The tests can later
be played back (windowshots will be automatically taken) and the
pictures will be compared for differences (usage of fail_if is also
      supported).
There is a premade set of tests and recordings for all (most?) of the
elementary widgets in various scenarios.
Because of the nature of this test suite, it doesn't handle well any
tests with continued running animations/viedos (timing can never be 100%
      right). But you can use it to test widgets with transition
animations. Bottom line: just give it a go.

Read the README for more inforamtion.

I hope it'll be deployed on our servers soon, as we really need
automatic testing.

Signed-off-by: Aharon Hillel <a.hillel@partner.samsung.com>

SVN revision: 65961

AUTHORS

@@ -0,0 +1 @@
+Aharon Hillel <a.hillel@partner.samsung.com>

COPYING

@@ -0,0 +1,25 @@
+Copyright notice for exactness:
+
+Copyright (C) 2011 by various contributors (see AUTHORS)
+
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+   1. Redistributions of source code must retain the above copyright
+      notice, this list of conditions and the following disclaimer.
+   2. Redistributions in binary form must reproduce the above copyright 
+      notice, this list of conditions and the following disclaimer in the
+      documentation and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, 
+INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
+OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
+EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

INSTALL

@@ -0,0 +1,365 @@
+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
+2006, 2007, 2008, 2009 Free Software Foundation, Inc.
+
+   Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.  This file is offered as-is,
+without warranty of any kind.
+
+Basic Installation
+==================
+
+   Briefly, the shell commands `./configure; make; make install' should
+configure, build, and install this package.  The following
+more-detailed instructions are generic; see the `README' file for
+instructions specific to this package.  Some packages provide this
+`INSTALL' file but do not implement all of the features documented
+below.  The lack of an optional feature in a given package is not
+necessarily a bug.  More recommendations for GNU packages can be found
+in *note Makefile Conventions: (standards)Makefile Conventions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+   It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring.  Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'.  You need `configure.ac' if
+you want to change it or regenerate `configure' using a newer version
+of `autoconf'.
+
+   The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.
+
+     Running `configure' might take a while.  While running, it prints
+     some messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package, generally using the just-built uninstalled binaries.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.  When installing into a prefix owned by root, it is
+     recommended that the package be configured and built as a regular
+     user, and only the `make install' phase executed with root
+     privileges.
+
+  5. Optionally, type `make installcheck' to repeat any self-tests, but
+     this time using the binaries in their final installed location.
+     This target does not install anything.  Running this target as a
+     regular user, particularly if the prior `make install' required
+     root privileges, verifies that the installation completed
+     correctly.
+
+  6. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+  7. Often, you can also type `make uninstall' to remove the installed
+     files again.  In practice, not all packages have tested that
+     uninstallation works correctly, even though it is required by the
+     GNU Coding Standards.
+
+  8. Some packages, particularly those that use Automake, provide `make
+     distcheck', which can by used by developers to test that all other
+     targets like `make install' and `make uninstall' work correctly.
+     This target is generally not run by end users.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  Run `./configure --help'
+for details on some of the pertinent environment variables.
+
+   You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment.  Here
+is an example:
+
+     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+
+   *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you can use GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.  This
+is known as a "VPATH" build.
+
+   With a non-GNU `make', it is safer to compile the package for one
+architecture at a time in the source code directory.  After you have
+installed the package for one architecture, use `make distclean' before
+reconfiguring for another architecture.
+
+   On MacOS X 10.5 and later systems, you can create libraries and
+executables that work on multiple system types--known as "fat" or
+"universal" binaries--by specifying multiple `-arch' options to the
+compiler but only a single `-arch' option to the preprocessor.  Like
+this:
+
+     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+                 CPP="gcc -E" CXXCPP="g++ -E"
+
+   This is not guaranteed to produce working output in all cases, you
+may have to build one architecture at a time and combine the results
+using the `lipo' tool if you have problems.
+
+Installation Names
+==================
+
+   By default, `make install' installs the package's commands under
+`/usr/local/bin', include files under `/usr/local/include', etc.  You
+can specify an installation prefix other than `/usr/local' by giving
+`configure' the option `--prefix=PREFIX', where PREFIX must be an
+absolute file name.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+pass the option `--exec-prefix=PREFIX' to `configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.  In general, the
+default for these options is expressed in terms of `${prefix}', so that
+specifying just `--prefix' will affect all of the other directory
+specifications that were not explicitly provided.
+
+   The most portable way to affect installation locations is to pass the
+correct locations to `configure'; however, many packages provide one or
+both of the following shortcuts of passing variable assignments to the
+`make install' command line to change installation locations without
+having to reconfigure or recompile.
+
+   The first method involves providing an override variable for each
+affected directory.  For example, `make install
+prefix=/alternate/directory' will choose an alternate location for all
+directory configuration variables that were expressed in terms of
+`${prefix}'.  Any directories that were specified during `configure',
+but not in terms of `${prefix}', must each be overridden at install
+time for the entire installation to be relocated.  The approach of
+makefile variable overrides for each directory variable is required by
+the GNU Coding Standards, and ideally causes no recompilation.
+However, some platforms have known limitations with the semantics of
+shared libraries that end up requiring recompilation when using this
+method, particularly noticeable in packages that use GNU Libtool.
+
+   The second method involves providing the `DESTDIR' variable.  For
+example, `make install DESTDIR=/alternate/directory' will prepend
+`/alternate/directory' before all installation names.  The approach of
+`DESTDIR' overrides is not required by the GNU Coding Standards, and
+does not work on platforms that have drive letters.  On the other hand,
+it does better at avoiding recompilation issues, and works well even
+when some directory options were not specified in terms of `${prefix}'
+at `configure' time.
+
+Optional Features
+=================
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+   Some packages offer the ability to configure how verbose the
+execution of `make' will be.  For these packages, running `./configure
+--enable-silent-rules' sets the default to minimal output, which can be
+overridden with `make V=1'; while running `./configure
+--disable-silent-rules' sets the default to verbose, which can be
+overridden with `make V=0'.
+
+Particular systems
+==================
+
+   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU
+CC is not installed, it is recommended to use the following options in
+order to use an ANSI C compiler:
+
+     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
+
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
+
+   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its `<wchar.h>' header file.  The option `-nodtk' can be used as
+a workaround.  If GNU CC is not installed, it is therefore recommended
+to try
+
+     ./configure CC="cc"
+
+and if that doesn't work, try
+
+     ./configure CC="cc -nodtk"
+
+   On Solaris, don't put `/usr/ucb' early in your `PATH'.  This
+directory contains several dysfunctional programs; working variants of
+these programs are available in `/usr/bin'.  So, if you need `/usr/ucb'
+in your `PATH', put it _after_ `/usr/bin'.
+
+   On Haiku, software installed for all users goes in `/boot/common',
+not `/usr/local'.  It is recommended to use the following options:
+
+     ./configure --prefix=/boot/common
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on.  Usually, assuming the package is built to be run on the
+_same_ architectures, `configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+`--build=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+     CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+     OS
+     KERNEL-OS
+
+   See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+   If you are _building_ compiler tools for cross-compiling, you should
+use the option `--target=TYPE' to select the type of system they will
+produce code for.
+
+   If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+   If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+   Variables not defined in a site shell script can be set in the
+environment passed to `configure'.  However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost.  In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'.  For example:
+
+     ./configure CC=/usr/local2/bin/gcc
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+Unfortunately, this technique does not work for `CONFIG_SHELL' due to
+an Autoconf bug.  Until the bug is fixed you can use this workaround:
+
+     CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+`configure' Invocation
+======================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--help'
+`-h'
+     Print a summary of all of the options to `configure', and exit.
+
+`--help=short'
+`--help=recursive'
+     Print a summary of the options unique to this package's
+     `configure', and exit.  The `short' variant lists options used
+     only in the top level, while the `recursive' variant lists options
+     also present in any nested packages.
+
+`--version'
+`-V'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`--cache-file=FILE'
+     Enable the cache: use and save the results of the tests in FILE,
+     traditionally `config.cache'.  FILE defaults to `/dev/null' to
+     disable caching.
+
+`--config-cache'
+`-C'
+     Alias for `--cache-file=config.cache'.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`--prefix=DIR'
+     Use DIR as the installation prefix.  *note Installation Names::
+     for more details, including other options available for fine-tuning
+     the installation locations.
+
+`--no-create'
+`-n'
+     Run the configure checks, but stop before creating any output
+     files.
+
+`configure' also accepts some other, not widely useful, options.  Run
+`configure --help' for more details.
+

Makefile.am

@@ -0,0 +1,18 @@
+
+MAINTAINERCLEANFILES = \
+Makefile.in \
+aclocal.m4 \
+config.guess \
+config.h.in \
+config.sub \
+configure \
+install-sh \
+depcomp \
+libtool \
+missing
+
+EXTRA_DIST = README AUTHORS COPYING
+
+SUBDIRS = src
+
+ACLOCAL_AMFLAGS = -I m4

README

@@ -0,0 +1,103 @@
+exactness is a software package aimed to automate Elementary testing
+after updating elm code.
+The testing process is composed of running widget test,
+cycling through API functions, and screenshot are taken on each stage of test.
+(on user request with F2 key).
+
+Next, these screenshots are compared with screenshots of widget test
+done before the code update.
+When exactness detects difference in screenshot comparison,
+it means widget layout was changed.
+Unexpected layout changes may reveal that something is broken
+in the new implementation.
+
+Testing with exactness composed of the following stages:
+1. Test Recording.
+   Done once and exactness user most likely does not need to do this.
+   A set of pre-recorded tests already resides under 'data/recording' folder.
+
+   To record a test just issue the command:
+   exactness -r 
+
+   Example:
+   exactness -r test_hover
+
+   The record file will be produced in the current-working-directory as:
+   test_hover.rec
+
+   In case you tried to run exactness with specific TestName
+   and nothing happens, this means you misspelled the test name.
+   You may review test names as it appears in tsuite.c source file.
+
+   NOTE: omitting the test name causes recording all tests one after another.
+   Do this if you only mean it.
+   This rule applies to ALL proceeding stages as well.
+
+   As widget test run you may press F2 at any point to set a screenshot.
+   (screenshot procduced in 'play' stage, set timing of screenshot here)
+   However, don't do this while animation is ongoing
+   or you get inconsistent PNG output each time test played.
+
+   NOTE: You may change screenshot key from F2 to any other key
+         with TSUITE_SHOT_KEY env var.
+
+2. Test Initiation.
+   The final stage of testing process is based on PNG image comparison
+   of original screenshots with current screenshots produced after code change.
+
+   To start you need to produce original screenshot set before code change.
+   To do that just issue the command:
+   exactness -i TestName1 [TestName2 ...]
+
+   This command will play the test (TestName.rec file) and place PNG files
+   under 'orig' folders created in current-working-directory.
+   You need to do this just once.
+   Again, omitting the TestName will play and produce PNG files for all tests.
+
+   Example:
+   exactness -i test_hover
+   This will produce PNG files such orig/test_hover_1.png
+
+3. Test playing, producing current state PNG files.
+   After doing Test Initiation (2) and updating elementary code,
+   you may run tests for current state of elm:
+
+   exactness -p [-d DestDir] TestName1 [TestName2 ...]
+   Omitting DestDir param will cause exactness place all PNG files
+   under (default) folder named 'current'.
+   
+4. Comparing PNG files.
+   This is the final stage of testing in which we compare output
+   before code update and after the update.
+   Matching PNG files from 'orig' and 'current' folder are compared.
+   When all comparisons done you get final report of (N) files did not match.
+   In case difference was found, you may look at comp_*.png files in DestDir.
+
+   To run a comparison:
+   exactness -c [-d DestDir] TestName1 [TestName2 ...]
+   All comp_*.png files will reside in DestDir.
+   Omitting DestDir cause exactness to use default of 'current' folder name.
+
+   Optional:
+   You may also do play and compare in a single command:
+   exactness -p -c [-d DestDir] TestName1 [TestName2 ...]
+
+5. fail_if(expr) macro:
+   You may use fail_if(expr); macro to verify variable value on-the-fly.
+   For example, if your code contains:
+
+   char *p;
+   ...
+   fail_if(p == NULL);
+
+   In case (p == NULL), a "fail_TestName.txt" file is crated
+   current working directory with a comment specifying the expr/line failed.
+
+   fail_*.txt files are produced only for when expr fails when running.
+   When tests completed, the user gets notification message if any tests failed.
+   In such case, please review the fail_*.txt files.
+
+6. To view exactness help issue the command:
+   exactness --help
+   or
+   exactness -h

autogen.sh

@@ -0,0 +1,18 @@
+#!/bin/sh
+
+rm -rf autom4te.cache
+rm -f aclocal.m4 ltmain.sh
+rm -f config.cache
+
+touch README
+touch ABOUT-NLS
+
+echo "Running aclocal..." ; aclocal $ACLOCAL_FLAGS || exit 1
+echo "Running autoheader..." ; autoheader || exit 1
+echo "Running autoconf..." ; autoconf || exit 1
+echo "Running libtoolize..." ; (libtoolize --copy --automake || glibtoolize --automake) || exit 1
+echo "Running automake..." ; automake --add-missing --copy --gnu || exit 1
+
+if [ -z "$NOCONFIGURE" ]; then
+	./configure "$@"
+fi

configure.ac

@@ -0,0 +1,48 @@
+dnl Process this file with autoconf to produce a configure script.
+
+AC_INIT([exactness], [0.1.0], [enlightenment-devel@lists.sourceforge.net])
+AC_PREREQ([2.52])
+AC_CONFIG_SRCDIR([configure.ac])
+AC_CANONICAL_BUILD
+AC_CANONICAL_HOST
+AC_CANONICAL_TARGET
+
+AM_INIT_AUTOMAKE([1.6 dist-bzip2])
+AM_CONFIG_HEADER([config.h])
+
+AC_ISC_POSIX
+AC_PROG_CC
+AM_PROG_CC_STDC
+AC_HEADER_STDC
+AC_C_CONST
+
+PKG_PROG_PKG_CONFIG
+AC_PROG_LIBTOOL
+
+dnl Checking for __attribute__ support
+AC_MSG_CHECKING([for __attribute__])
+AC_CACHE_VAL([_cv_have___attribute__],
+  [
+    AC_TRY_COMPILE([#include <stdlib.h>],
+      [int func(int x); int foo(int x __attribute__ ((unused))) { exit(1); }],
+      [_cv_have___attribute__="yes"],
+      [_cv_have___attribute__="no"])
+  ])
+
+if test "x${_cv_have___attribute__}" = "xyes" ; then
+  AC_DEFINE([HAVE___ATTRIBUTE__], [1], [Define to 1 if your compiler has __attribute__])
+fi
+AC_MSG_RESULT([${_cv_have___attribute__}])
+
+PKG_CHECK_MODULES([EFL],
+  [
+   elementary >= 0.7.0
+  ])
+
+AC_OUTPUT([
+Makefile
+src/Makefile
+src/bin/Makefile
+src/lib/Makefile
+src/scripts/Makefile
+])

src/Makefile.am

@@ -0,0 +1,4 @@
+
+MAINTAINERCLEANFILES = Makefile.in
+
+SUBDIRS = bin lib scripts

src/bin/Makefile.am

@@ -0,0 +1,80 @@
+
+MAINTAINERCLEANFILES = Makefile.in
+
+AM_CPPFLAGS = \
+-I$(top_srcdir)/src/lib \
+-DPACKAGE_BIN_DIR=\"$(bindir)\" \
+-DPACKAGE_DATA_DIR=\"$(datadir)/$(PACKAGE)\" \
+-DLOCALE_DIR=\"$(datadir)/locale\" \
+@EFL_CFLAGS@
+
+bin_PROGRAMS = exactness_raw
+
+exactness_raw_SOURCES = \
+		    tsuite.c \
+		    ../lib/tsuite_file_data.c \
+		    test_3d.c \
+		    test_actionslider.c \
+		    test_focus2.c \
+		    test_panel.c \
+		    test_anchorblock.c \
+		    test_focus3.c \
+		    test_panes.c \
+		    test_anchorview.c \
+		    test_focus.c \
+		    test_photo.c \
+		    test_bg.c \
+		    test_gengrid.c \
+		    test_photocam.c \
+		    test_box.c \
+		    test_genlist.c \
+		    test_progressbar.c \
+		    test_bubble.c \
+		    test_radio.c \
+		    test_button.c \
+		    test_scaling.c \
+		    test_calendar.c \
+		    test_grid.c \
+		    test_segment_control.c \
+		    test_check.c \
+		    test_hover.c \
+		    test_separator.c \
+		    test_hoversel.c \
+		    test_slider.c \
+		    test_colorselector.c \
+		    test_conform.c \
+		    test_spinner.c \
+		    test_ctxpopup.c \
+		    test_index.c \
+		    test_table.c \
+		    test_cursor.c \
+		    test_inwin.c \
+		    test_thumb.c \
+		    test_diskselector.c \
+		    test_label.c \
+		    test_toggle.c \
+		    test_entry.c \
+		    test_toolbar.c \
+		    test_fileselector_button.c \
+		    test_tooltip.c \
+		    test_fileselector.c \
+		    test_list.c \
+		    test_fileselector_entry.c \
+		    test_map.c \
+		    test_weather.c \
+		    test_menu.c \
+		    test_win_inline.c \
+		    test_naviframe.c \
+		    test_win_state.c \
+		    test_notify.c \
+		    test_floating.c \
+		    test_scroller.c \
+		    test_pager.c
+
+
+
+exactness_raw_LDADD = @EFL_LIBS@
+
+EXTRA_DIST = \
+	     tsuite.h
+

src/bin/test_3d.c

@@ -0,0 +1,338 @@
+#include <Elementary.h>
+#include "tsuite.h"
+
+typedef struct _Point
+{
+   Evas_Coord x, y, z, u, v;
+} Point;
+
+typedef struct _Side
+{
+   Evas_Object *o;
+   Point pt[4];
+} Side;
+
+typedef struct _Cube
+{
+   Side side[6];
+} Cube;
+
+static Cube *cube;
+static double rotx = 0.0, roty = 0.0, rotz = 0.0;
+static double cxo = 0.0, cyo = 0.0, focv = 256.0, z0v = 0.0;
+#define POINT(n, p, xx, yy, zz, uu, vv) \
+   c->side[n].pt[p].x = xx; \
+   c->side[n].pt[p].y = yy; \
+   c->side[n].pt[p].z = zz; \
+   c->side[n].pt[p].u = uu; \
+   c->side[n].pt[p].v = vv
+
+static Cube *
+_cube_new(Evas *evas, Evas_Coord w, Evas_Coord h, Evas_Coord d)
+{
+   Cube *c;
+   int i;
+
+   w -= (w / 2);
+   h -= (h / 2);
+   d -= (d / 2);
+   c = calloc(1, sizeof(Cube));
+   for (i = 0; i < 6; i++)
+     {
+        Evas_Object *o;
+        char buf[PATH_MAX];
+        o = evas_object_image_add(evas);
+        c->side[i].o = o;
+        snprintf(buf, sizeof(buf), "%s/images/%s",
+                 elm_app_data_dir_get(), "twofish.jpg");
+        evas_object_image_file_set(o, buf, NULL);
+        evas_object_image_fill_set(o, 0, 0, 256, 256);
+        evas_object_resize(o, 256, 256);
+        evas_object_image_smooth_scale_set(o, 0);
+        evas_object_show(o);
+     }
+   POINT(0, 0, -w, -h, -d,   0,   0);
+   POINT(0, 1,  w, -h, -d, 256,   0);
+   POINT(0, 2,  w,  h, -d, 256, 256);
+   POINT(0, 3, -w,  h, -d,   0, 256);
+
+   POINT(1, 0,  w, -h, -d,   0,   0);
+   POINT(1, 1,  w, -h,  d, 256,   0);
+   POINT(1, 2,  w,  h,  d, 256, 256);
+   POINT(1, 3,  w,  h, -d,   0, 256);
+
+   POINT(2, 0,  w, -h,  d,   0,   0);
+   POINT(2, 1, -w, -h,  d, 256,   0);
+   POINT(2, 2, -w,  h,  d, 256, 256);
+   POINT(2, 3,  w,  h,  d,   0, 256);
+
+   POINT(3, 0, -w, -h,  d,   0,   0);
+   POINT(3, 1, -w, -h, -d, 256,   0);
+   POINT(3, 2, -w,  h, -d, 256, 256);
+   POINT(3, 3, -w,  h,  d,   0, 256);
+
+   POINT(4, 0, -w, -h,  d,   0,   0);
+   POINT(4, 1,  w, -h,  d, 256,   0);
+   POINT(4, 2,  w, -h, -d, 256, 256);
+   POINT(4, 3, -w, -h, -d,   0, 256);
+
+   POINT(5, 0, -w,  h, -d,   0,   0);
+   POINT(5, 1,  w,  h, -d, 256,   0);
+   POINT(5, 2,  w,  h,  d, 256, 256);
+   POINT(5, 3, -w,  h,  d,   0, 256);
+
+   return c;
+}
+
+static void
+_cube_pos(Cube *c,
+          Evas_Coord x, Evas_Coord y, Evas_Coord z,
+          double dx, double dy, double dz,
+          Evas_Coord cx, Evas_Coord cy, Evas_Coord foc, Evas_Coord z0)
+{
+   Evas_Map *m;
+   int i, j, order[6], sorted;
+   Evas_Coord mz[6];
+
+   m = evas_map_new(4);
+   evas_map_smooth_set(m, 0);
+
+   for (i = 0; i < 6; i++)
+     {
+        Evas_Coord tz[4];
+
+        for (j = 0; j < 4; j++)
+          {
+             evas_map_point_coord_set(m, j,
+                                      c->side[i].pt[j].x + x,
+                                      c->side[i].pt[j].y + y,
+                                      c->side[i].pt[j].z + z);
+             evas_map_point_image_uv_set(m, j,
+                                         c->side[i].pt[j].u,
+                                         c->side[i].pt[j].v);
+             evas_map_point_color_set(m, j, 255, 255, 255, 255);
+          }
+        evas_map_util_3d_rotate(m, dx, dy, dz, x, y, z);
+        evas_map_util_3d_lighting(m, -1000, -1000, -1000,
+                                  255, 255, 255,
+                                  20, 20, 20);
+        evas_map_util_3d_perspective(m, cx, cy, foc, z0);
+        if (evas_map_util_clockwise_get(m))
+          {
+             evas_object_map_enable_set(c->side[i].o, 1);
+             evas_object_map_set(c->side[i].o, m);
+             evas_object_show(c->side[i].o);
+          }
+        else
+           evas_object_hide(c->side[i].o);
+
+        order[i] = i;
+        for (j = 0; j < 4; j++)
+           evas_map_point_coord_get(m, j, NULL, NULL, &(tz[j]));
+        mz[i] = (tz[0] + tz[1] + tz[2] + tz[3]) / 4;
+     }
+   sorted = 0;
+   do
+     {
+        sorted = 1;
+        for (i = 0; i < 5; i++)
+          {
+             if (mz[order[i]] > mz[order[i + 1]])
+               {
+                  j = order[i];
+                  order[i] = order[i + 1];
+                  order[i + 1] = j;
+                  sorted = 0;
+               }
+          }
+     }
+   while (!sorted);
+
+   evas_object_raise(c->side[order[0]].o);
+   for (i = 1; i < 6; i++)
+      evas_object_stack_below(c->side[order[i]].o, c->side[order[i - 1]].o);
+   evas_map_free(m);
+}
+
+/*
+static void
+_cube_free(Cube *c)
+{
+   int i;
+
+   for (i = 0; i < 6; i++) evas_object_del(c->side[i].o);
+   free(c);
+}
+*/
+
+static void
+_cube_update(Evas_Object *win, Cube *c)
+{
+   Evas_Coord w, h;
+
+   evas_object_geometry_get(win, NULL, NULL, &w, &h);
+   _cube_pos(c,
+             (w / 2), (h / 2), 512,
+             rotx, roty, rotz,
+             (w / 2) + cxo, (h / 2) + cyo, z0v, focv);
+}
+
+void
+_ch_rot_x(void *data, Evas_Object *obj, void *event_info __UNUSED__)
+{
+   Evas_Object *win = data;
+   rotx = elm_slider_value_get(obj);
+   _cube_update(win, cube);
+}
+
+void
+_ch_rot_y(void *data, Evas_Object *obj, void *event_info __UNUSED__)
+{
+   Evas_Object *win = data;
+   roty = elm_slider_value_get(obj);
+   _cube_update(win, cube);
+}
+
+void
+_ch_rot_z(void *data, Evas_Object *obj, void *event_info __UNUSED__)
+{
+   Evas_Object *win = data;
+   rotz = elm_slider_value_get(obj);
+   _cube_update(win, cube);
+}
+
+void
+_ch_cx(void *data, Evas_Object *obj, void *event_info __UNUSED__)
+{
+   Evas_Object *win = data;
+   cxo = elm_slider_value_get(obj);
+   _cube_update(win, cube);
+}
+
+void
+_ch_cy(void *data, Evas_Object *obj, void *event_info __UNUSED__)
+{
+   Evas_Object *win = data;
+   cyo = elm_slider_value_get(obj);
+   _cube_update(win, cube);
+}
+
+void
+_ch_foc(void *data, Evas_Object *obj, void *event_info __UNUSED__)
+{
+   Evas_Object *win = data;
+   focv = elm_slider_value_get(obj);
+   _cube_update(win, cube);
+}
+
+void
+_ch_z0(void *data, Evas_Object *obj, void *event_info __UNUSED__)
+{
+   Evas_Object *win = data;
+   z0v = elm_slider_value_get(obj);
+   _cube_update(win, cube);
+}
+
+TEST_START(test_3d)
+{
+   Evas_Object *bg, *bx, *sl;
+
+   bg = elm_bg_add(win);
+   elm_win_resize_object_add(win, bg);
+   evas_object_size_hint_weight_set(bg, EVAS_HINT_EXPAND, EVAS_HINT_EXPAND);
+   evas_object_show(bg);
+
+   cube = _cube_new(evas_object_evas_get(win), 240, 240, 240);
+
+   bx = elm_box_add(win);
+   evas_object_layer_set(bx, 10);
+   evas_object_size_hint_weight_set(bx, EVAS_HINT_EXPAND, EVAS_HINT_EXPAND);
+   elm_win_resize_object_add(win, bx);
+   evas_object_show(bx);
+
+   sl = elm_slider_add(win);
+   elm_object_text_set(sl, "Rot X");
+   elm_slider_unit_format_set(sl, "%1.0f units");
+   elm_slider_span_size_set(sl, 360);
+   elm_slider_min_max_set(sl, 0, 360);
+   evas_object_size_hint_align_set(sl, EVAS_HINT_FILL, 0.5);
+   evas_object_size_hint_weight_set(sl, EVAS_HINT_EXPAND, EVAS_HINT_EXPAND);
+   elm_box_pack_end(bx, sl);
+   evas_object_smart_callback_add(sl, "changed", _ch_rot_x, win);
+   evas_object_show(sl);
+
+   sl = elm_slider_add(win);
+   elm_object_text_set(sl, "Rot Y");
+   elm_slider_unit_format_set(sl, "%1.0f units");
+   elm_slider_span_size_set(sl, 360);
+   elm_slider_min_max_set(sl, 0, 360);
+   evas_object_size_hint_align_set(sl, EVAS_HINT_FILL, 0.5);
+   evas_object_size_hint_weight_set(sl, EVAS_HINT_EXPAND, EVAS_HINT_EXPAND);
+   elm_box_pack_end(bx, sl);
+   evas_object_smart_callback_add(sl, "changed", _ch_rot_y, win);
+   evas_object_show(sl);
+
+   sl = elm_slider_add(win);
+   elm_object_text_set(sl, "Rot Z");
+   elm_slider_unit_format_set(sl, "%1.0f units");
+   elm_slider_span_size_set(sl, 360);
+   elm_slider_min_max_set(sl, 0, 360);
+   evas_object_size_hint_align_set(sl, EVAS_HINT_FILL, 0.5);
+   evas_object_size_hint_weight_set(sl, EVAS_HINT_EXPAND, EVAS_HINT_EXPAND);
+   elm_box_pack_end(bx, sl);
+   evas_object_smart_callback_add(sl, "changed", _ch_rot_z, win);
+   evas_object_show(sl);
+
+   sl = elm_slider_add(win);
+   elm_object_text_set(sl, "CX Off");
+   elm_slider_unit_format_set(sl, "%1.0f units");
+   elm_slider_span_size_set(sl, 360);
+   elm_slider_min_max_set(sl, -320, 320);
+   elm_slider_value_set(sl, cxo);
+   evas_object_size_hint_align_set(sl, EVAS_HINT_FILL, 0.5);
+   evas_object_size_hint_weight_set(sl, EVAS_HINT_EXPAND, EVAS_HINT_EXPAND);
+   elm_box_pack_end(bx, sl);
+   evas_object_smart_callback_add(sl, "changed", _ch_cx, win);
+   evas_object_show(sl);
+
+   sl = elm_slider_add(win);
+   elm_object_text_set(sl, "CY Off");
+   elm_slider_unit_format_set(sl, "%1.0f units");
+   elm_slider_span_size_set(sl, 360);
+   elm_slider_min_max_set(sl, -320, 320);
+   elm_slider_value_set(sl, cyo);
+   evas_object_size_hint_align_set(sl, EVAS_HINT_FILL, 0.5);
+   evas_object_size_hint_weight_set(sl, EVAS_HINT_EXPAND, EVAS_HINT_EXPAND);
+   elm_box_pack_end(bx, sl);
+   evas_object_smart_callback_add(sl, "changed", _ch_cy, win);
+   evas_object_show(sl);
+
+   sl = elm_slider_add(win);
+   elm_object_text_set(sl, "Foc");
+   elm_slider_unit_format_set(sl, "%1.0f units");
+   elm_slider_span_size_set(sl, 360);
+   elm_slider_min_max_set(sl, 1, 2000);
+   elm_slider_value_set(sl, focv);
+   evas_object_size_hint_align_set(sl, EVAS_HINT_FILL, 0.5);
+   evas_object_size_hint_weight_set(sl, EVAS_HINT_EXPAND, EVAS_HINT_EXPAND);
+   elm_box_pack_end(bx, sl);
+   evas_object_smart_callback_add(sl, "changed", _ch_foc, win);
+   evas_object_show(sl);
+
+   sl = elm_slider_add(win);
+   elm_object_text_set(sl, "Z0");
+   elm_slider_unit_format_set(sl, "%1.0f units");
+   elm_slider_span_size_set(sl, 360);
+   elm_slider_min_max_set(sl, -2000, 2000);
+   elm_slider_value_set(sl, z0v);
+   evas_object_size_hint_align_set(sl, EVAS_HINT_FILL, 0.5);
+   evas_object_size_hint_weight_set(sl, EVAS_HINT_EXPAND, EVAS_HINT_EXPAND);
+   elm_box_pack_end(bx, sl);
+   evas_object_smart_callback_add(sl, "changed", _ch_z0, win);
+   evas_object_show(sl);
+
+   evas_object_resize(win, 480, 480);
+   _cube_update(win, cube);
+   evas_object_show(win);
+}
+TEST_END

src/bin/test_actionslider.c

@@ -0,0 +1,175 @@
+#include <Elementary.h>
+#include "tsuite.h"
+
+static void _pos_selected_cb(void *data __UNUSED__, Evas_Object *obj, void *event_info)
+{
+   printf("Selection: %s\n", (char *)event_info);
+   printf("Label selected: %s\n", elm_actionslider_selected_label_get(obj));
+}
+
+static void
+_position_change_magnetic_cb(void *data __UNUSED__, Evas_Object * obj, void *event_info)
+{
+   if (!strcmp((char *)event_info, "left"))
+     elm_actionslider_magnet_pos_set(obj, ELM_ACTIONSLIDER_LEFT);
+   else if (!strcmp((char *)event_info, "right"))
+     elm_actionslider_magnet_pos_set(obj, ELM_ACTIONSLIDER_RIGHT);
+}
+
+static void
+_magnet_enable_disable_cb(void *data __UNUSED__, Evas_Object *obj, void *event_info)
+{
+   if (!strcmp((char *)event_info, "left"))
+      elm_actionslider_magnet_pos_set(obj, ELM_ACTIONSLIDER_CENTER);
+   else if (!strcmp((char *)event_info, "right"))
+      elm_actionslider_magnet_pos_set(obj, ELM_ACTIONSLIDER_NONE);
+}
+
+enum _api_state
+{
+   API_STATE_LAST
+};
+typedef enum _api_state api_state;
+
+static void
+set_api_state(api_data *api)
+{
+   switch(api->state)
+     { /* Put all api-changes under switch */
+      case API_STATE_LAST:
+         break;
+      default:
+         return;
+     }
+}
+
+static void
+_api_bt_clicked(void *data, Evas_Object *obj __UNUSED__, void *event_info __UNUSED__)
+{  /* Will add here a SWITCH command containing code to modify test-object */
+   /* in accordance a->state value. */
+   api_data *a = data;
+   char str[128];
+
+   printf("clicked event on API Button: api_state=<%d>\n", a->state);
+   a->state++;
+   set_api_state(a);
+   sprintf(str, "Next API function (%u)", a->state);
+   elm_object_text_set(a->bt, str);
+   elm_object_disabled_set(a->bt, a->state == API_STATE_LAST);
+}
+
+TEST_START(test_actionslider)
+{
+   Evas_Object *bg, *bx, *as;
+
+   bg = elm_bg_add(win);
+   elm_win_resize_object_add(win, bg);
+   evas_object_size_hint_weight_set(bg, EVAS_HINT_EXPAND, 0);
+   evas_object_show(bg);
+
+   bx = elm_box_add(win);
+   evas_object_size_hint_weight_set(bx, EVAS_HINT_EXPAND, 0);
+   elm_win_resize_object_add(win, bx);
+   evas_object_show(bx);
+
+   api->bt = elm_button_add(win);
+   elm_object_text_set(api->bt, "Next API function");
+   evas_object_smart_callback_add(api->bt, "clicked", _api_bt_clicked, (void *) api);
+   elm_box_pack_end(bx, api->bt);
+   elm_object_disabled_set(api->bt, api->state == API_STATE_LAST);
+   evas_object_show(api->bt);
+
+   as = elm_actionslider_add(win);
+   evas_object_size_hint_weight_set(as, EVAS_HINT_EXPAND, 0);
+   evas_object_size_hint_align_set(as, EVAS_HINT_FILL, 0);
+   elm_actionslider_indicator_pos_set(as, ELM_ACTIONSLIDER_RIGHT);
+   elm_actionslider_magnet_pos_set(as, ELM_ACTIONSLIDER_RIGHT);
+   elm_object_part_text_set(as, "left", "Snooze");
+   elm_object_part_text_set(as, "center", NULL);
+   elm_object_part_text_set(as, "right", "Stop");
+   elm_actionslider_enabled_pos_set(as, ELM_ACTIONSLIDER_LEFT |
+                                    ELM_ACTIONSLIDER_RIGHT);
+   evas_object_smart_callback_add(as, "pos_changed",
+                                  _position_change_magnetic_cb, NULL);
+   evas_object_smart_callback_add(as, "selected", _pos_selected_cb, NULL);
+   evas_object_show(as);
+   elm_box_pack_end(bx, as);
+
+   as = elm_actionslider_add(win);
+   evas_object_size_hint_weight_set(as, EVAS_HINT_EXPAND, 0);
+   evas_object_size_hint_align_set(as, EVAS_HINT_FILL, 0);
+   elm_actionslider_indicator_pos_set(as, ELM_ACTIONSLIDER_CENTER);
+   elm_actionslider_magnet_pos_set(as, ELM_ACTIONSLIDER_CENTER);
+   elm_object_part_text_set(as, "left", "Snooze");
+   elm_object_part_text_set(as, "center", NULL);
+   elm_object_part_text_set(as, "right", "Stop");
+   elm_actionslider_enabled_pos_set(as, ELM_ACTIONSLIDER_LEFT |
+                                    ELM_ACTIONSLIDER_RIGHT);
+   evas_object_smart_callback_add(as, "selected", _pos_selected_cb, NULL);
+   evas_object_show(as);
+   elm_box_pack_end(bx, as);
+
+   as = elm_actionslider_add(win);
+   elm_object_style_set(as, "bar");
+   evas_object_size_hint_weight_set(as, EVAS_HINT_EXPAND, 0);
+   evas_object_size_hint_align_set(as, EVAS_HINT_FILL, 0);
+   elm_actionslider_indicator_pos_set(as, ELM_ACTIONSLIDER_LEFT);
+   elm_actionslider_magnet_pos_set(as, ELM_ACTIONSLIDER_CENTER|
+                                   ELM_ACTIONSLIDER_RIGHT);
+   elm_actionslider_enabled_pos_set(as, ELM_ACTIONSLIDER_CENTER |
+                                    ELM_ACTIONSLIDER_RIGHT);
+   elm_object_part_text_set(as, "left", NULL);
+   elm_object_part_text_set(as, "center", "Accept");
+   elm_object_part_text_set(as, "right", "Reject");
+   evas_object_smart_callback_add(as, "selected", _pos_selected_cb, NULL);
+   evas_object_show(as);
+   elm_box_pack_end(bx, as);
+
+   as = elm_actionslider_add(win);
+   elm_object_style_set(as, "bar");
+   evas_object_size_hint_weight_set(as, EVAS_HINT_EXPAND, 0);
+   evas_object_size_hint_align_set(as, EVAS_HINT_FILL, 0);
+   elm_actionslider_indicator_pos_set(as, ELM_ACTIONSLIDER_LEFT);
+   elm_actionslider_magnet_pos_set(as, ELM_ACTIONSLIDER_LEFT);
+   elm_object_part_text_set(as, "left", NULL);
+   elm_object_part_text_set(as, "center", "Accept");
+   elm_object_part_text_set(as, "right", "Reject");
+   elm_object_text_set(as, "Go");
+   evas_object_smart_callback_add(as, "pos_changed",
+                                  _position_change_magnetic_cb, NULL);
+   evas_object_smart_callback_add(as, "selected", _pos_selected_cb, NULL);
+   evas_object_show(as);
+   elm_box_pack_end(bx, as);
+
+
+   as = elm_actionslider_add(win);
+   evas_object_size_hint_weight_set(as, EVAS_HINT_EXPAND, 0);
+   evas_object_size_hint_align_set(as, EVAS_HINT_FILL, 0);
+   elm_actionslider_indicator_pos_set(as, ELM_ACTIONSLIDER_LEFT);
+   elm_actionslider_magnet_pos_set(as, ELM_ACTIONSLIDER_ALL);
+   elm_object_part_text_set(as, "left", "Left");
+   elm_object_part_text_set(as, "center", "Center");
+   elm_object_part_text_set(as, "right", "Right");
+   elm_object_text_set(as, "Go");
+   evas_object_smart_callback_add(as, "selected", _pos_selected_cb, NULL);
+   evas_object_show(as);
+   elm_box_pack_end(bx, as);
+
+   as = elm_actionslider_add(win);
+   evas_object_size_hint_weight_set(as, EVAS_HINT_EXPAND, 0);
+   evas_object_size_hint_align_set(as, EVAS_HINT_FILL, 0);
+   elm_actionslider_indicator_pos_set(as, ELM_ACTIONSLIDER_CENTER);
+   elm_actionslider_magnet_pos_set(as, ELM_ACTIONSLIDER_CENTER);
+   elm_object_part_text_set(as, "left", "Enable");
+   elm_object_part_text_set(as, "center", "Magnet");
+   elm_object_part_text_set(as, "right", "Disable");
+   evas_object_smart_callback_add(as, "pos_changed",
+                                  _magnet_enable_disable_cb, NULL);
+   evas_object_smart_callback_add(as, "selected", _pos_selected_cb, NULL);
+   evas_object_show(as);
+   elm_box_pack_end(bx, as);
+
+   evas_object_resize(win, 320, 400);
+   evas_object_show(win);
+}
+TEST_END

src/bin/test_anchorblock.c

@@ -0,0 +1,275 @@
+#include <Elementary.h>
+#include "tsuite.h"
+
+static void
+_print_clicked(void *data __UNUSED__, Evas_Object *obj __UNUSED__, void *event_info __UNUSED__)
+{
+   printf("bubble clicked\n");
+}
+
+static void
+my_anchorblock_bt(void *data, Evas_Object *obj __UNUSED__, void *event_info __UNUSED__)
+{
+   Evas_Object *av = data;
+   elm_anchorblock_hover_end(av);
+}
+
+static void
+my_anchorblock_anchor(void *data, Evas_Object *obj, void *event_info)
+{
+   Evas_Object *av = data;
+   Elm_Entry_Anchorblock_Info *ei = event_info;
+   Evas_Object *bt, *bx;
+
+   bt = elm_button_add(obj);
+   elm_object_text_set(bt, ei->name);
+   elm_hover_content_set(ei->hover, "middle", bt);
+   evas_object_show(bt);
+
+   // hints as to where we probably should put hover contents (buttons etc.).
+   if (ei->hover_top)
+     {
+	bx = elm_box_add(obj);
+	bt = elm_button_add(obj);
+	elm_object_text_set(bt, "Top 1");
+	elm_box_pack_end(bx, bt);
+	evas_object_smart_callback_add(bt, "clicked", my_anchorblock_bt, av);
+	evas_object_show(bt);
+	bt = elm_button_add(obj);
+	elm_object_text_set(bt, "Top 2");
+	elm_box_pack_end(bx, bt);
+	evas_object_smart_callback_add(bt, "clicked", my_anchorblock_bt, av);
+	evas_object_show(bt);
+	bt = elm_button_add(obj);
+	elm_object_text_set(bt, "Top 3");
+	elm_box_pack_end(bx, bt);
+	evas_object_smart_callback_add(bt, "clicked", my_anchorblock_bt, av);
+	evas_object_show(bt);
+	elm_hover_content_set(ei->hover, "top", bx);
+	evas_object_show(bx);
+     }
+   if (ei->hover_bottom)
+     {
+	bt = elm_button_add(obj);
+	elm_object_text_set(bt, "Bot");