We do not use instance ID in layer names, which will cause problems during container UI re-constructing

We do not use instance ID in layer names, which will cause problems during container UI re-constructing

Signed-off-by: goldenhawking <goldenhawking@163.com>

# Conflicts:
#	test_container/testcontainer.h

With the help of this feature, a function call without complete style para will use the default.

2. sloved a tiny problem that selection  box's coord will be mis-calculated during rotating.

We gives every geo_graphics_item an prop, which is a boolean variable. Items can be selected by mouse dragging.

2. sloved a mingw32 4.8.2 WIN32 definition problem

with -fPIC options can product code for dynamic linked library, whether the -fPIE is not good.
for this reason, as if the project qwidget_planetosm(DLL) and qplanetosm_viewer shares almost same files,
we should build DLL first, and then is the executable.

2. Support both string and qmap calls in widget

1.We export osm_frame_widget to DLL as a QWidget extension.Also, a designer plugin is introduced for UI desinger convient.
2.The grid plugin is improved for quickly mark insert, to demo how these 2 layers(grid and geomarker) communicate with each other.

using props_vis to get detailed prop showing status for specified items
using show_props to determing detailed props visibility for the giving items

disable UI list refresh during geomarker layer calls. the UI list refresh will significantly reduce performance

the c# app provides most function demos,
the MFC app demos antimation drawing effect.

Multiline can hold several lines in one top-level item. now, point, line, multiline, polygon, these geo types can hold WKT style geo elements in future.

Tab have their own icons, plugins' prop page tab-bar item should display their icons, not only text names.

2.sloved a geomarker graphics item click and dblclick mismatch. In old case, when mouse clicks, a dblclick message will be pumped.

2. individually update tableView instead of at one time.