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

change filament issue #1264

Merged
merged 2 commits into from
Dec 29, 2014
Merged

change filament issue #1264

merged 2 commits into from
Dec 29, 2014

Conversation

Wurstnase
Copy link
Contributor

make a more general solution

make a more general solution
@boelle
Copy link
Contributor

boelle commented Dec 29, 2014

what issue does this one fix? just so i can get that one closed

@Wurstnase
Copy link
Contributor Author

you work the hole day? ;)

Change Filament Disables X and Y Steppers Which Cuases Carriage Movement While Changing Filament #1038

msutas made a change which is realy close to my solution. I just go a little bit more general.

@boelle
Copy link
Contributor

boelle commented Dec 29, 2014

heheheh, no i'm without a job :-)

keeping this clean and moving on marlin just keeps me sane :-P

@boelle
Copy link
Contributor

boelle commented Dec 29, 2014

hmm... i never saw he submitted a pull request.... must have been sleeping :-)

@boelle
Copy link
Contributor

boelle commented Dec 29, 2014

ahh... found it, never merged thou as people are arguing back and forth....

@bkubicek
Copy link
Contributor

The pull request is fine from my side, but I would prefer if the bool is
named in a more clear way, so it makes sense when you read the variable
definitions.
e.g. "inactivityStepperDisableIngore" or similar.

Bernhard

On Mon, Dec 29, 2014 at 4:38 PM, Bo Herrmannsen notifications@github.com
wrote:

hmm... i never saw he submitted a pull request.... must have been sleeping
:-)


Reply to this email directly or view it on GitHub
/~https://github.com/ErikZalm/Marlin/pull/1264#issuecomment-68267384.

@boelle
Copy link
Contributor

boelle commented Dec 29, 2014

@Wurstnase would that be hard to implement? or should i merge now and wait for a new pull request?

more speaking name
bkubicek added a commit that referenced this pull request Dec 29, 2014
@bkubicek bkubicek merged commit 78167ce into MarlinFirmware:Development Dec 29, 2014
@bkubicek
Copy link
Contributor

thanks

@boelle
Copy link
Contributor

boelle commented Dec 29, 2014

:-) @bkubicek what about your latest comment?

@nophead
Copy link
Contributor

nophead commented Dec 29, 2014

Why use a global variable when it can be passed as a parameter with a
default as I suggested before?

Global flags to modify behaviour like this are terrible programming
practice.and they waste ram.

On 29 December 2014 at 15:42, Bo Herrmannsen notifications@github.com
wrote:

@Wurstnase /~https://github.com/Wurstnase would that be hard to
implement? or should i merge now and wait for a new pull request?

Reply to this email directly or view it on GitHub
/~https://github.com/ErikZalm/Marlin/pull/1264#issuecomment-68267735.

@bkubicek
Copy link
Contributor

@boelle he changed it Wurstnase@d1995ae
@nophead yes, thats why I proposed a default-argument for manage_inactivity. But I think this solves it for now, and can be improved later, as it fixes a bug...

@bkubicek
Copy link
Contributor

@nophead Sorry, I cannot find the reference where I propsed that this can be done by a default argument. Maybe I just thought about it. I faintly remembered telling that I will change in the next few days, it, but again, I don't find this message.

So, yes, the best way would be to have manage_inactivity(disablesteppers=true) {....}.

@Wurstnase
Copy link
Contributor Author

right! Just done it that way.

@bkubicek
Copy link
Contributor

@Wurstnase thanks, I think thats even better, and also what @nophead wants, probably.
Can you please do another pull request for "Expand Manage_inactivity"?

@Wurstnase
Copy link
Contributor Author

Sure.

bkubicek added a commit that referenced this pull request Dec 29, 2014
@bkubicek
Copy link
Contributor

thanks, i added a small change right now....

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.

4 participants