Macroquad: How do I define a border?

[Joe232]

In the Processing lang I am able to use stroke() to tell that future shapes will have a border around it.

I am using macroquad crate for my own project I am looking through the man pages but I am struggling to find if there is a way to draw borders around the 2D shape?

[dani.pardo]

You can specify a border using the _lines methods, i.e: draw_rectangle_lines(), draw_poly_lines().etc..

If you come from Processing though, I'm not sure if macroquad allows for keeping screen state on each frame. At least I've found that It will always clear the screen on every frame. Other than that, If you're into creative coding, you might be interested on checking out nannou https://nannou.cc/ for stuff like that.

[Joe232]

@dani.pardo

You can specify a border using the _lines methods, i.e: draw_rectangle_lines(), draw_poly_lines().etc..

Ah I see.

Macroquad: why do I see these blank dots when using draw_circle_lines() function?

[image] So I am using draw_circle_lines() function using the macroquad crate and for some reason it displays this ugly blank dots where you can see the background. Here is my code to draw this (only for the draw_circle_line() function) draw_circle_lines(screen_width()/2., screen_height()/2, 30, 20., RED);

In my other post it seems to be having some weird dots or something when I tried this, why is that happening though?

@dani.pardo

I'm not sure if macroquad allows for keeping screen state on each frame.

Sorry mate what do you mean by this?

[dani.pardo]

In Processing, each time the draw() function gets invoked, the screen is not cleared. In macroquad, each time you call next_frame(), the screen is cleared, which is not often the desired behaviour when doing creative coding.

Regarding the dots effect you are experiencing, I guess it's due to the algorythm macroquad uses in order to generate borders, I don't know whow you would prevent that tbh.

[Joe232]

@dani.pardo

In Processing, each time the draw() function gets invoked, the screen is not cleared. In macroquad, each time you call next_frame(), the screen is cleared, which is not often the desired behaviour when doing creative coding.

I see, that kinda sucks. I will probably check out Nannou.

@dani.pardo

Regarding the dots effect you are experiencing, I guess it's due to the algorythm macroquad uses in order to generate borders, I don't know whow you would prevent that tbh.

I see, thanks mate anyways