to the 15000px limit.
Thanks. Eric
2008/7/25, Alexandre Dube [EMAIL PROTECTED]:
Hi everybody,
I use Firefox ( big fan ).
Of what I understand, each time I zoom in or out a map that has a
vector layer, the left and top values of the rederer's viewbox are
reseted to 0.
I have a WFS
Hi,
I posted this message to the users list but got no reply.
I don't know if anybody noticed this yet : when you use a Layer.Text and
you keep clicking on the same marker, the popup gets bigger and
bigger. Even the example it does that :
PM, Alexandre Dube [EMAIL PROTECTED] wrote:
So it seems to me that the problem doesn't really related to the 15000
px limit. In this scenario:
- go out of range
- pan and zoom without going beyond the 15000 px limit
- go in range (the features should be visible as the limit was crossed
. This to be check,
which i cant do at the moment. Regards. Eric
2008/7/28, Alexandre Dube [EMAIL PROTECTED]:
Hi Eric,
The location is correct. It is ok to have a 15000px limit and that
works perfectly.
To fix the bug, I think when the code checks the resolution, if it's
the same
Hi Everybody,
Is it ok if the Scale control registers a moveend event instead of a
zoomend ? To recalculate the scale after panning doesn't look very useful to
me. What do you think ?
--
Alexandre Dubé
Mapgears
www.mapgears.com
___
Dev
Ok, I'll just have to wait for the next release then :) ( I wasn't sure
if the trunk was actually as the next release would be. )
Thanks,
Alexandre
Christopher Schmidt wrote:
On Fri, Sep 05, 2008 at 07:37:57AM -0400, Alexandre Dube wrote:
Hi devs,
I use OpenLayers 2.6 and I have
Hi devs,
I noticed a new strange behavior with OpenLayers 2.7-rc1 using
WFSDescribeFeatureType format.
Here's the request I'm using :
var sUrl = olWFSRoads.getFullRequestString({
REQUEST: DescribeFeatureType,
SERVICE: WFS,
TYPENAME:
Alexandre Dube wrote:
Hi devs,
I noticed a new strange behavior with OpenLayers 2.7-rc1 using
WFSDescribeFeatureType format.
Here's the request I'm using :
var sUrl = olWFSRoads.getFullRequestString({
REQUEST: DescribeFeatureType,
SERVICE: WFS
Hi dev,
Anything new about vector labels ?
--
Alexandre Dubé
Mapgears
www.mapgears.com
___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev
I tried this small patch but unfortunately the problem persist. Is there
a new patch for this issue ( feature stays on screen when zooming with
mouse over it with cluster strategy ) ?
If not, I would like to disable the wheel zoom. How can I do that ?
Alexandre
Tim Schaub wrote:
Hey-
Eric
Hi devs,
I got a problem using the cluster strategy. At first, it didn't
seemed to work at all. I always got the same number of feature with or
without the cluster strategy applied. After a few search, I found out
the problem was at line 143 : *var* resolution =
it work properly. Well, in the
end I don't understand what I'm doing wrong. Sorry.
Alexandre
Tim Schaub wrote:
Hey-
Alexandre Dube wrote:
Hi Eric,
Ok, I understand what you mean. But I already set specific scales to
the vector layer that are supposed to give the same
I get the same behavior as Ivan's on my application which has very
similar resolution settings on map an vector layer.
Because a layer's features are not destroyed when it goes out of range
(inRange) or becomes invisible (visibility), the cluster strategy still
clusters those existing
Eric Lemoine wrote:
Alexandre,
Could you apply the patches attached to #1831 et #1834 and report back?
Thanks,
http://trac.openlayers.org/ticket/1831
http://trac.openlayers.org/ticket/1834
--
Eric
Problem solved for me. No events ( like clustering) are triggered by
the layer on
Hi devs,
http://trac.openlayers.org/ticket/1902 is an unassigned ticket with a
patch implementing new features to the Strategy.Save.
Comments are welcomed,
Regards,
--
Alexandre Dubé
Mapgears
www.mapgears.com
___
Dev mailing list
Hi devs,
Some examples on sandboxes don't work because
http://dev.openlayers.org/proxy/ doesn't exist. Could that be fixed ?
--
Alexandre Dubé
Mapgears
www.mapgears.com
___
Dev mailing list
Dev@openlayers.org
Hi devs,
http://trac.openlayers.org/ticket/1905 is an unassigned ticket implementing a
new feature : Strategy.OptionsByZoom
See live examples of use :
(working) http://dev4.mapgears.com/bdga/options-by-zoom-bdga.html
(missing different data sources)
Hi devs,
I would like to propose some changes about the SelectFeature control.
First, I'll introduce what I want to do : I want to change the color
of a feature while the mouse is over it without selecting it. I managed
to do this by building a customized control similar to the
with more details.
Alexandre
Alexandre Dube wrote:
Hi devs,
I would like to propose some changes about the SelectFeature control.
First, I'll introduce what I want to do : I want to change the color
of a feature while the mouse is over it without selecting it. I managed
to do
.
Alexandre Dube and I will be meeting on #openlayers at 16:30 GMT, Tues
Jan 20 (next week) to talk about dividing up responsibilities for making
patches and getting this in the trunk.
Somehow I missed this meeting taking place on IRC. Can you sum up the
results of it? Perhaps post
again (for unselection). With your stack
of intents logic, the feature isn't redrawn as a result of the second
click; instead it should be redrawn with the hover control's render
intent, shouldn't it?
Eric
2009/1/23, Alexandre Dube ad...@mapgears.com:
Hi devs,
Eric was right
would just remove it and
avoid the above problem. What do you think ?
Alexandre
Alexandre Dube wrote:
Hi Eric,
You're right. So instead of removing the last renderIntent from the
stack, we need to remove the last renderIntent of the current SelectFeature.
SFC = SelectFeature Control
+1.613.520.2600x8179
On 26-Jan-09, at 10:13 AM, Alexandre Dube wrote:
Hi devs,
My only problem remaining : should the layer keep its selectedFeature
array ? If so, on selection, it's easy to know if a feature is already
selected. As soon as one control adds it to its own array, it checks
fear that an
not the proper intent will be removed. Am I wrong?
It does, because having the same renderIntent == having the same style
applied. The only issue remaining is : does the layer need to keep its
selectedFeatures array ?
Alexandre
Cheers,
Eric
2009/1/26, Alexandre Dube ad
Alexandre Dube wrote:
Hi,
Here's an other possibility :
SFA : selectedFeature Array
RI : renderIntent
RIA : renderIntent Array
Let's say we forget about the controls to have their own SFA. Only
the layer has its own SFA.
on featureselect
if feature is not in SFA
Hi,
Could you explain a little more what you're trying to accomplish ?
There might be other ways to do what you want.
Regards,
Alexandre
toni hernández wrote:
Hi,
I've been a couple of days looking at the code and trying to add a
mousemove function inside the SelectFeature control.
I
Hi Devs,
http://trac.openlayers.org/ticket/1882
The way I see this control now the more I think it should have been done
an other way.
Currently :
- It uses feature+keyboard+box handlers for selection/unselection
- It has its own array of selected features
- It directly changes the
Hi devs,
I brought several weeks ago some possible modification ideas that the
SelectFeature control could have, including :
- having its own selectedFeatures array with the corresponding events
that are currently in the layer
- the feature renderIntent could be a stack of strings ( an
Lemoine wrote:
On Thu, Mar 5, 2009 at 5:09 PM, Alexandre Dube ad...@mapgears.com wrote:
Sorry, I should have written :
Control #1, select on click, color: blue
Control #2, highlight on hover, color: yellow, highlightOnly
The problem is that control #2 :
highlight a feature even
Thanks Eric,
I'll have to try that in the following days. I'll let you know if I
have comments.
Regards,
Alexandre
Eric Lemoine wrote:
On Fri, Mar 13, 2009 at 4:28 PM, Eric Lemoine eric@gmail.com wrote:
I like it. See the attached eric-to-alexandre patch ;-)
Alexandre, I
Hi Eric,
This is sweet. It accomplish everything we need to have two or more
SelectFeatures controls at the same time, on the same layer. And the
new highlight events make it possible to have temporary things
happening at the same time, like displaying a popup on hover.
Great work Eric.
Hi,
I just sent (finally) a new patch for ticket 1882 (1) (DeleteFeature
control) and set the status to review.
(1) http://trac.openlayers.org/ticket/1882
Regards,
--
Alexandre Dubé
Mapgears
www.mapgears.com
___
Dev mailing list
the Save strategy or
protocol.commit...)
Since I'm using featureserver and Protocol.MapFish (which is not part
of the OpenLayers project) I can't figure how I could avoid to delete
'manually' the features, i.e. not in the control itself.
Any hint would be appreciated,
Alexandre
Alexandre
a
do the same kind of automatism as the new 'controls' property ?
Regards,
Alexandre
Any hint would be appreciated,
Alexandre
Alexandre Dube wrote:
Hi,
I just sent (finally) a new patch for ticket 1882 (1) (DeleteFeature
control) and set the status to review.
(1) http
Hi,
First, that question is more suitable for the 'users' mailing list.
See below for more.
abir rezgui wrote:
Hi there!
I want to display the content of a shapefile using mapserver with
openlayers. I did it successfully in cases where the layer's type is
POLYGON but I still don't
Eric Lemoine wrote:
so, to get to the delete control you've been working on, I see more
value, in terms of flexibility, in adding control composition to the
control base class.
I also agree. Originally, the control had a Feature handler instead of
a SelectFeature control. Looking at
).
Any hint would be greatly appreciated,
Alexandre
P.S. Also, I believe it's ok to have my 'user' functions, like
confirmDelete directly inside the control since the control is
completely custom-made (i.e. not using events).
Alexandre Dube wrote:
Eric Lemoine wrote:
so, to get
Oh and by the way, here's what I did for the Control (attached). Is it
ok (too much, i.e. about the use of hasOwnProperty functions) ?
Thanks,
Alexandre
Alexandre Dube wrote:
Eric Lemoine wrote:
so, to get to the delete control you've been working on, I see more
value, in terms
Hi,
I'm going to work on my example today. See below.
Eric Lemoine wrote:
why not using the regular
var i, len, control;
for(i = 0, len = controls.length; i len; i++) {
control = controls[i];
}
?
Right. I just wondered if it could have been possible to have a {}
instead of
Hi,
jessisena wrote:
Finally I 've solved the problem triggering an event (from save.js) of the
layer which was the listener...
Anyway, exists some way to do what I was asking for? Which is the way to
receive in a specific layer the success or fail event declared in Save.js ?
I'd like
Eric Lemoine wrote:
Alexandre
I now understand one of your problems, you need to give the handler a
reference to the control, but the control does not exist yet since
you're actually creating it. Giving the handler a fake control, of the
form {map: map} (where map is the map instance) should do
Hi,
jessisena wrote:
Hi,
Anybody knows if is possible to have two differents controls Draw feature,
with the same kind of handler (for example point), and everyone with their
own style?
That is, if I can have two controls that draw points with different styles,
in the same layer.
Thanks
Hi,
Eric Lemoine wrote:
I still agree with automatic controls and handlers activation/deactivation.
Attached an new patch with the simple changes needed. Is it ok ? If it
is, I'll open a ticket.
Ok to me.
Thanks Alexandre,
http://trac.openlayers.org/ticket/2196
currently
Hi,
One of my coworker had some trouble using the WMSGetFeatureInfo
control. The response always said Missing FORMAT property. Here's
what he found on this :
Section 7.3.1 of the WMS 1.1.1 specification says:
Because the WMS protocol is stateless, the GetFeatureInfo request
indicates to
Hi,
I have a very odd behavior with the SelectFeature control in IE +
keyboard handler using the KEY_ESC to unselect all features.I use a
customized DeleteFeature control, who is responsible to set the feature
state to delete and redrawing it. It has it's own SelectFeature
control for
Hi,
I tried an other key (instead of 'esc') and the problem went away. So
it really looks like a 'esc' key problem in IE. Can anyone comments
about this, please ?
Alexandre
Alexandre Dube wrote:
Hi,
I have a very odd behavior with the SelectFeature control in IE +
keyboard handler
://dev4g.mapgears.com/openlayers/ie-highlight-bug/examples/select-feature-esc.html
(2) http://trac.openlayers.org/ticket/2214
Alexandre Dube wrote:
Hi,
I tried an other key (instead of 'esc') and the problem went away. So
it really looks like a 'esc' key problem in IE. Can anyone comments
about
.
An other weird behavior : if you use shift+esc, all features get drawn
back to default normally...
Comments would be welcomed, please.
Alexandre
Alexandre Dube wrote:
Hi,
I made an example out of the select-feature.html example. I only
added a keyboard handler to the SelectFeature
Hi Ivan,
Here's my thoughts on that topic :
Like you said, I also did something similar. I had 4 different data
sources that were normalized and had to use 4 Vector layers with
moveend events to automatically switch from one to an other.
What I though to be 'a bad idea' was to have 4 layers
Alexandre Dube wrote:
Hi,
I made an example out of the select-feature.html example. I only
added a keyboard handler to the SelectFeature control and it still do
the problem. See the example (1).
I opened a ticket for this (2). Currently unassigned and without a patch.
Alexandre
Hi Ivan,
Do you have an example showing when this can happen ? I've been playing
with the SelectFeature control and can't figure how you can have the
same feature added 2 times to the layer.selectedFeatures array, unless
you do it manually.
Regards,
Alexandre
Ivan Grcic wrote:
If we do
Hi,
Kushy wrote:
What if I need to put on this layer just some of them? Can I filter them in
some way? I tried writing featureserver.cgi/punti?id=100, thinking it
would have displayed the POI with id=100, but it doesn't work.
For single selection, try : featureserver.cgi/punti/100.gml
.
On 2009-12-11 15:10, Alexandre Dube wrote:
Hi devs,
=== short version ===
* Is there any plan to support multiple feature selection in the
ModifyFeature control ?
* If not, would that make sense to support it ? (Clicking features
beyond the first one would enable the editing for those
Right. The only thing left useful with the SelectFeature control is to
store the selected features in the layer's selectedFeature's array. So,
users would have to do that manually and as they please from there
on... Sounds logical.
Thanks Andreas for the pointers,
Alexandre
Andreas
Hi,
I want to be able to save a OpenLayers.Style object or hash to a
vector feature. Currently, in code, feature.style exists but you must
define a hash or else it doesn't work.
My problem is that I want to be able to draw features to be used as
labels (floating text on the map). To be
Andreas, Eric, Cédric,
Thanks to all of you for your support. Your answers are very clear
and well detailed. I'll make the changes according to what you proposed
and come back if I have any more questions.
Thanks again,
Alexandre
Andreas Hocevar wrote:
Hi,
Alexandre Dube wrote
Rohala,
I replied to your message from Nabble because I didn't see it in my
OpenLayers-Dev Mailing-List mailbox. I guess it's because of the big
image attached to it. I'll copy it here for convenience. See below.
BTW, your problem is more suitable for the users mailing list.
Regards,
.
Thanks again,
Alex
On Thu, Feb 4, 2010 at 3:34 PM, Alexandre Dube ad...@mapgears.com
mailto:ad...@mapgears.com wrote:
Alex,
I just looked at the SelectFeature control code and I think you
could try this solution :
Change you Marker layer for a Vector one (you can
images.
Thanks in advance!
Best regards,
Alex
On Thu, Feb 4, 2010 at 8:26 PM, Alexandre Dube ad...@mapgears.com
mailto:ad...@mapgears.com wrote:
Alex,
Take a look at this example [1]. Vector features can be used
with a SelectFeature control to open popups. You only
Hi,
I opened a small ticket [1] including a fix for the only lang file not
in utf-8. There's a bug when using this file in IE6 while using a meta
http-equiv=Content-Type content=text/html; charset=utf-8 tag.
Regards,
[1] http://trac.openlayers.org/ticket/2472
--
Alexandre Dubé
Mapgears
Hi,
There are some discussion currently going on to integrate that kind of
tool as a GeoExt.ux widget. See the GeoExt-dev mailing list.
Regards,
Alexandre
Marc Jansen wrote:
Hi mortac,
see http://www.mail-archive.com/us...@openlayers.org/msg05213.html
That is old, beta, OL 2.7 and
Hi,
GeoExt has this kind of tool, see some examples at :
http://www.geoext.org/examples.html#advanced-printing-with-a-form
Regards,
Alexandre
yellow wrote:
HI Guys Gals,
I would like to know if there is a method or piece of code that allows us to
print certain segments of the map.
Is
Hi,
CampToCamp worked on such a widget in GeoExt.ux. Currently in a sandbox :
http://dev.geoext.org/sandbox/cmoullet/ux/RoutingPanel/examples/RoutingPanelExample.html
See also :
http://pgrouting.postlbs.org/
Regards,
Alexandre
yellow wrote:
Hi,
I would like to know if it is possible to
Hi,
I'm not sure what's wrong with what you're doing, but maybe a quick look
at this example [1] might help. I would use 'highlightOnly': true only
and register events instead of overwriting the native callback methods
used when hovering.
Hope this helps,
Alexandre
Joe,
You can't. You can only use it with Vector features. If you're planing
to use WMS only, you can use the GetFeatureInfo control triggering
requests when the mouse stops for a brief moment and display a div with
the name of the feature hovered.
Here's an other solution (still using WFS to
65 matches
Mail list logo