Hi, I have a question on transitionEffect with option 'resize', when i use
this effect on a TMS Layer, every time i make a zoom, two request for each
single tile have been launched. It is correct or a bug? You can test with
tms.html example adding transitionEffect: 'resize', on TMS Layer Options.
Hi,
See below.
Maxime Phaneuf wrote:
I've compared this to the GML Insert you send to TinyOWS in
http://dev4.mapgears.com/bdga/bdgaWFS-T.html and it looks alike.
This is the answer I received from TinyOWS:
?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
When using the resize option, two images are created for each tile.
The 'current' image is resized when zooming and the new image is
loaded in front of it, effectively providing greater (or lesser)
detail. I don't think it should be making any additional requests for
a zoom. Could be a
hi Marc
2009/7/29 Marc Jansen jan...@terrestris.de
Hi Valeria,
maybe the OpenLayerButtonGenerator could be of use for you:
http://www.terrestris.de/wp-media/downloads/OpenLayersButtonGenerator.tar.gz
see this thread some hours ago:
hi Marc
thanks for the information, but this code create new icons and this
icons must change it in the directory of openlayer can i send it to
openlayer some image path to change the originals icons or maybe with css?
RG
2009/7/29 Marc Jansen jan...@terrestris.de
Hi Valeria,
Hi,
if you use OpenLayers.Control.PanZoomPanel, you can style it entirely in
css. Looking at theme/default/style.css should be more or less self
explanatory. You will want to change background images you find in there.
Regards,
Andreas.
Valeria Muñoz wrote:
hi Marc
thanks for the
In case anyone else runs into this, I found out that after the map is
created, it sometimes doesn't set a height or width value in the map.size
property. Here's my fix which seems to work quite nicely:
map = new OpenLayers.Map('map', options);
if (isNaN(map.size.w) || isNaN(map.size.h)) {
soatley wrote:
In case anyone else runs into this, I found out that after the map is
created, it sometimes doesn't set a height or width value in the map.size
property. Here's my fix which seems to work quite nicely:
map = new OpenLayers.Map('map', options);
if (isNaN(map.size.w) ||
On 7/29/2009 at 11:57 AM, Andreas Hocevar ahoce...@opengeo.org wrote:
soatley wrote:
In case anyone else runs into this, I found out that after the map is
created, it sometimes doesn't set a height or width value in the map.size
property. Here's my fix which seems to work quite nicely:
Should have checked my CSS before posting that mesage.
Here is what I already have defined in for my map object:
#map
{
position: absolute;
width: 100%;
height: 100%;
top: 0px;
left: 0px;
}
Andreas Hocevar-2 wrote:
soatley wrote:
In case
Shawn Oatley wrote:
On 7/29/2009 at 11:57 AM, Andreas Hocevar ahoce...@opengeo.org wrote:
soatley wrote:
In case anyone else runs into this, I found out that after the map is
created, it sometimes doesn't set a height or width value in the map.size
property. Here's my fix
soatley wrote:
Should have checked my CSS before posting that mesage.
Here is what I already have defined in for my map object:
#map
{
position: absolute;
width: 100%;
height: 100%;
top: 0px;
left: 0px;
}
Add
html, body {
width: 100%,
Hi,
I'd like to know if there's a better (faster) way to restore a
modified feature's geometry other than using layer.refresh({'force':true});
I use a ModifyFeature control with a popup that as save and cancel
buttons. On save, it commits the changes (fine). On cancel, it should
Hi,
I need one example about turn on/off layer in openlayer with geoserver.
Regards,
Salas.
___
Dirección de Comunicaciones
Grupo Empresarial GEOCUBA
Este mensaje esta libre de virus.
Revisado por Kaspersky Antivirus
Well, in the end I would really like to avoid the use of
layer.refresh({'force':true}) if possible.
If you activate the DrawFeature control while modifying a feature
(instead of hitting cancel), the geometry of the current modified
feature still needs to be restored (didn't hit the save
I tried some very basic tests with and without the resize option and it does
seem to create a fair number of additional requests.
Here are my results...
With Resize:
Initial Load: 585 requests
+1 Zoom level: 999 requests (+414 for the zoom)
-1 Zoom level: 1096requests (+97 for the zoom)
Without
Hey,
Alexandre Dube wrote:
Well, in the end I would really like to avoid the use of
layer.refresh({'force':true}) if possible.
If you activate the DrawFeature control while modifying a feature
(instead of hitting cancel), the geometry of the current modified
feature still needs to be
17 matches
Mail list logo
