Android - is passing dirty rectangle to View.invalidate() still necessary?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am using google maps in android. I have a created a polygon of points and am using it as a geofence to trigger some action.
I would like to take the polygon of points and convert them into a rectangle so that i can call invalidate only on the rectangle area. As we know android screen is compromised of rectangles and we can when we call invalidate() on a view we have the option to invalidate (redraw) just a rectangle area. this is more efficient then re-drawing the entire screen when only a part of it has changed. In the map i have i know that only . inside the geofence area has my view changes (im doing animation there actually).
so i a google polygon class and if i call polygon?.points it has a list of LatLng objects. i can use GoogleMap.projection
to get the matching screen coordinates on the phone of hte gps coordinates in the polygon.points list. But now i want to call:
postInvalidateOnAnimation and pass in the rectangle area coordinates that is "dirty" so it can redraw it. but then in the docs for invalidate method
i see the following note:
This method was deprecated in API level 28.
The switch to hardware accelerated rendering in API 14 reduced the importance of the dirty rectangle. In API 21 the given rectangle is ignored entirely in favor of an internally-calculated area instead. Because of this, clients are encouraged to just call invalidate().
does this only for api 28 and upwards or from 14 and upwards that passing a dirty rectangle is pointless ? if there is still a point to it how can i convert the polygon points (many points) to rectangle coordinates (4 points) ?

add a comment |
I am using google maps in android. I have a created a polygon of points and am using it as a geofence to trigger some action.
I would like to take the polygon of points and convert them into a rectangle so that i can call invalidate only on the rectangle area. As we know android screen is compromised of rectangles and we can when we call invalidate() on a view we have the option to invalidate (redraw) just a rectangle area. this is more efficient then re-drawing the entire screen when only a part of it has changed. In the map i have i know that only . inside the geofence area has my view changes (im doing animation there actually).
so i a google polygon class and if i call polygon?.points it has a list of LatLng objects. i can use GoogleMap.projection
to get the matching screen coordinates on the phone of hte gps coordinates in the polygon.points list. But now i want to call:
postInvalidateOnAnimation and pass in the rectangle area coordinates that is "dirty" so it can redraw it. but then in the docs for invalidate method
i see the following note:
This method was deprecated in API level 28.
The switch to hardware accelerated rendering in API 14 reduced the importance of the dirty rectangle. In API 21 the given rectangle is ignored entirely in favor of an internally-calculated area instead. Because of this, clients are encouraged to just call invalidate().
does this only for api 28 and upwards or from 14 and upwards that passing a dirty rectangle is pointless ? if there is still a point to it how can i convert the polygon points (many points) to rectangle coordinates (4 points) ?

add a comment |
I am using google maps in android. I have a created a polygon of points and am using it as a geofence to trigger some action.
I would like to take the polygon of points and convert them into a rectangle so that i can call invalidate only on the rectangle area. As we know android screen is compromised of rectangles and we can when we call invalidate() on a view we have the option to invalidate (redraw) just a rectangle area. this is more efficient then re-drawing the entire screen when only a part of it has changed. In the map i have i know that only . inside the geofence area has my view changes (im doing animation there actually).
so i a google polygon class and if i call polygon?.points it has a list of LatLng objects. i can use GoogleMap.projection
to get the matching screen coordinates on the phone of hte gps coordinates in the polygon.points list. But now i want to call:
postInvalidateOnAnimation and pass in the rectangle area coordinates that is "dirty" so it can redraw it. but then in the docs for invalidate method
i see the following note:
This method was deprecated in API level 28.
The switch to hardware accelerated rendering in API 14 reduced the importance of the dirty rectangle. In API 21 the given rectangle is ignored entirely in favor of an internally-calculated area instead. Because of this, clients are encouraged to just call invalidate().
does this only for api 28 and upwards or from 14 and upwards that passing a dirty rectangle is pointless ? if there is still a point to it how can i convert the polygon points (many points) to rectangle coordinates (4 points) ?

I am using google maps in android. I have a created a polygon of points and am using it as a geofence to trigger some action.
I would like to take the polygon of points and convert them into a rectangle so that i can call invalidate only on the rectangle area. As we know android screen is compromised of rectangles and we can when we call invalidate() on a view we have the option to invalidate (redraw) just a rectangle area. this is more efficient then re-drawing the entire screen when only a part of it has changed. In the map i have i know that only . inside the geofence area has my view changes (im doing animation there actually).
so i a google polygon class and if i call polygon?.points it has a list of LatLng objects. i can use GoogleMap.projection
to get the matching screen coordinates on the phone of hte gps coordinates in the polygon.points list. But now i want to call:
postInvalidateOnAnimation and pass in the rectangle area coordinates that is "dirty" so it can redraw it. but then in the docs for invalidate method
i see the following note:
This method was deprecated in API level 28.
The switch to hardware accelerated rendering in API 14 reduced the importance of the dirty rectangle. In API 21 the given rectangle is ignored entirely in favor of an internally-calculated area instead. Because of this, clients are encouraged to just call invalidate().
does this only for api 28 and upwards or from 14 and upwards that passing a dirty rectangle is pointless ? if there is still a point to it how can i convert the polygon points (many points) to rectangle coordinates (4 points) ?


asked Jan 3 at 6:06


j2emanuej2emanue
24k28146263
24k28146263
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54017108%2fandroid-is-passing-dirty-rectangle-to-view-invalidate-still-necessary%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54017108%2fandroid-is-passing-dirty-rectangle-to-view-invalidate-still-necessary%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown