Ticket #418 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

Rendering composite line style for Scale Ranges bug

Reported by: skorpion Owned by: waltweltonlair
Priority: medium Milestone: 2.1
Component: Rendering Service Version: 2.0.0
Severity: critical Keywords:
Cc: External ID:

Description

I create new composite Line Style with condition in Scale Ranges (see Image1) On map (in AJAX viewer) I can see only one component (see Image2)

Attachments

Image1.PNG Download (38.7 KB) - added by skorpion 4 years ago.
Composite line style
Image2.png Download (16.7 KB) - added by skorpion 4 years ago.
Line in mapview
Map_1.2.png Download (98.2 KB) - added by gbecker 4 years ago.
map as it was in version 1.2
Map_2.0_RC3_1.png Download (99.5 KB) - added by gbecker 4 years ago.
map in version 2.0 RC3
Map_2.0_RC3_2.png Download (98.3 KB) - added by gbecker 4 years ago.
map in version 2.0 RC3

Change History

Changed 4 years ago by skorpion

Composite line style

Changed 4 years ago by skorpion

Line in mapview

Changed 4 years ago by gbecker

  • severity changed from major to critical

I found out that the style of the composite line changes when panning through the map and that labeling of the themed layer is broken in MGOS 2.0 RC3.

Changed 4 years ago by gbecker

map as it was in version 1.2

Changed 4 years ago by gbecker

map in version 2.0 RC3

Changed 4 years ago by gbecker

map in version 2.0 RC3

Changed 4 years ago by waltweltonlair

The problem shows up when you have a filter. The expression engine correctly evaluates the filter on the first pass through the features, but for subsequent passes it seems to always return false when evaluating the filter.

Changed 4 years ago by tomfukushima

  • milestone changed from 2.0 to 2.1

Changed 4 years ago by waltweltonlair

  • owner set to waltweltonlair

Changed 4 years ago by waltweltonlair

  • status changed from new to assigned

Changed 4 years ago by waltweltonlair

  • status changed from assigned to closed
  • resolution set to fixed

Turns out this got fixed as part of ticket #510.

Note: See TracTickets for help on using tickets.