-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Add functions for numeric layout properties #799
Conversation
@lbud Can you rebase this on |
void TileParser::parse() { | ||
parseStyleLayers(style->layers); | ||
void TileParser::parse(float z) { | ||
parseStyleLayers(style->layers, z); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can avoid needing to thread z
through by using tile.id.z
instead.
Trying to root out a few weird test failures here —
|
std::string name; | ||
util::ptr<StyleSource> style_source; | ||
std::string source_layer; | ||
FilterExpression filter; | ||
ClassProperties layout; | ||
StyleBucketRender render = std::false_type(); | ||
float min_zoom = -std::numeric_limits<float>::infinity(); | ||
float max_zoom = std::numeric_limits<float>::infinity(); | ||
VisibilityType visibility = VisibilityType::Visible; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this visibility
unused now that StyleBucket*
all have their own visibility
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jfirebaugh good point — there was some trickery here since layout properties became parsed differently; about to push a fix that removes all individual StyleBucket*
visibility
properties.
6d36f26
to
895d904
Compare
Refs mapbox/mapbox-gl-style-spec#238