Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renderer.fill_rect now takes an Option<Rect>. #561

Merged
merged 1 commit into from
Nov 27, 2016

Conversation

Zoomulator
Copy link
Contributor

Native SDL2 behavior allows passing of null to fill the entire target.

Unless there's some reasoning not to allow this?

@Cobrand
Copy link
Member

Cobrand commented Nov 27, 2016

Luckily for us Into<Option<P>> has been implemented for P few stables ago, so this change shouldn't break anything, but we can never be too sure. It's not that important if it did break anything cause technically we are unstable, but it'd be nice to know ourselves if it breaks or not.

Technically I guess renderer.clear() does the same thing but if there are 2 functions I guess they are actually different ? Do you know the difference between clear() and fill_rect(None) ?

If you could confirm that this change doesn't break current usage of renderer.fill_rect(rect), I'll gladly merge this. Even if it does, we'll just break the API and bump to v0.26

@Zoomulator
Copy link
Contributor Author

The difference is that renderer.clear() ignores blend mode and can not fill with a transparent color, while doing the following does:

renderer.set_blend_mode( BlendMode::Blend );
renderer.set_draw_color( Color::RGBA(0,255,0,100) );
renderer.fill_rect( None );

There's no implicit conversion from Rect to Option<Rect> as far as I can tell. From::from(rect) works fine. Not sure if you meant Into<Option<P>> possibly would allow implicit conversion?

So I'd imagine this is indeed a breaking change.

@Zoomulator
Copy link
Contributor Author

Hold on, I got you now. I'll implement the fill_rect function taking an T: Into<Option<Rect>>. Should be implicit then.

@Cobrand
Copy link
Member

Cobrand commented Nov 27, 2016

Nah, I mean that few rust releases ago this PR has made its way into the language : rust-lang/rust#34828

See here

That means that you should not have to implement anything, it is already in the language. However I'd like to know if this really works or not right now with our code (it should be, but we can never be too sure)

@Cobrand
Copy link
Member

Cobrand commented Nov 27, 2016

Sorry technically you just have to change one line, which is

pub fn fill_rect(&mut self, rect: Option<Rect>) -> Result<(), String> {

into

pub fn fill_rect<T:Into<Option<Rect>>(&mut self, rect: T) -> Result<(), String> {
    let rect = rect.into()

edit: just realized that's exactly what you said, so this is useless

This should allow passing Rect, Some(Rect) or None to fill_rect.
Passing None to fill_rect fills the entire rendering target.
@Zoomulator Zoomulator force-pushed the renderer_fill_option_rect branch from d8bfd0f to 9974063 Compare November 27, 2016 13:42
@Zoomulator
Copy link
Contributor Author

Yep, that's exactly what I just realized. :) Thanks anyway for the clarification.
I've cleaned up the branch so there's only one commit,

@Cobrand Cobrand merged commit 53c8a40 into Rust-SDL2:master Nov 27, 2016
@Cobrand
Copy link
Member

Cobrand commented Nov 27, 2016

Cheers !

@Zoomulator Zoomulator deleted the renderer_fill_option_rect branch November 27, 2016 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants