Opened 16 years ago
Closed 15 years ago
#711 closed defect (worksforme)
Filtered Layer Still Show Tooltips and Selection
Reported by: | crispinatime | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | 2.1 |
Component: | Server | Version: | 2.0.2 |
Severity: | critical | Keywords: | |
Cc: | External ID: |
Description
Hi,
We have an application creating a dynamic filter on a layer - e.g. the original layer in the session has a filter of "1=0" and using drop-down lists is filtered and the map refreshed, works great!
However, all is good in the UI until a user hovers over or uses the selection tool over a feature that is not currently displayed (because it does not match the filter). The problem is that the feature is still selectable (refreshes with a blue highlight) and also displays the tooltip if you hover over the empty space where the object was filtered out.
This known example is using OLEDB points, on a MapGuide layout (no Fusion) on 2.0.2
Change History (4)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Hi Crispin,
Does the "1=0" filter work when it is set in the original LayerDefinition in the Library repository but not when the LayerDefinition is in the session repository?
Thanks, Trevor
comment:3 by , 16 years ago
All,
We have a 2.0.1 install on one of the dev machines - but I don't have access right now...
Trevor, the "1=0" filter is fine in the original definition in the library - and looks OK therfore in the first LayerDefinition display in the session (we don't update the layer definition before load, only after displaying the default map and the user selects a dropdown criteria). It is once we rewrite the LayerDefinition in the session, and refresh the map, the graphical layer display appears correct but the ability to get ghost selections and tooltips is manifested. I should be able to get some screen-shots if required.
The tooltip display code must be pretty clever if it can determine the particular filter *in the current session* and apply that as well as the location filter to the featurecource?!
comment:4 by , 15 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
As I cannot get this to replicate I am going to close. It may have been down to the "generous" default buffer around the tooltip hover that means you can be some-way off an existing feature and still get a tooltip showing (we reduce this buffer in our .templ files to avoid confusion)
Hi crispinatime, Thanks for taking the time to report this. Was this working in MGOS 2.0.1? Thanks, Tom