Conversation
|
@Keyikedalube Yes i am able to understand what is happening here. But i don't know about Wreorder or what is it . |
|
Wreorder message is triggered when object member initialization is not in order with the class declaration. So in C++ you have class declaration in What we have in synfig is something like this:
Read this section Using Initialization Lists to Initialize Fields to better understand the topic |
|
It warns you because of this: |
|
@ice0 @Keyikedalube Thanks for putting this much effort for me. I will study these and then review and improve my changes . Thanks :) |
|
@rodolforg Okay, If i am not wrong, I dont have to made changes in .h file rather than i have to make them in .cpp file !! Thanks :) |
|
@rodolforg @ice0 @Keyikedalube highlight_active_bone(false) was getting declared after onion_skin and I shifted it to above show_grid(false) that must be giving the compile time error of Wreorder warnings Kindly look after my PR. Thanks :) |
|
You fixed the issue with this commit d099194 :) But your PR is dirty with other commits and an unneeded merge. You should only rebase when you wish to update your working branch, not merge. Also, rebasing is never really needed unless someone's PR was merged first && he modified the same file that you are working on. Upto project maintainers to decide what's next. |
|
@Keyikedalube Okay Thanks for the advice. Actually @AYESDIE Yesterday told me to rebase properly so that PRs will be approved quickly. But I did it with every branch I have, I was practicing git commands . Sorry :) |
|
@Keyikedalube Thanks a lot for giving me that much of hints. Without them I wouldn't be able to solve the issue. Thanks :) |
|
@Keyikedalube There were some issues that were there with the Appveyor CI (some key related issue) which were fixed later in master so the PRs needed a rebase for the checks to be passed. And I don't think there's need for 6 commits for a small change, so this one does need cleaning in my opinion. Rebasing and squasing commits will help (^_^) |
|
@Keyikedalube Actually I was confused about it too. Anyways Thank You :) |
|
@DhairyaBahl Happens to everyone :) @AYESDIE I remember rebasing and pushing updates would end up looking like this "user force-pushed ..." but his update says "merge" so he could have done it some other way. IDK how. And yes he needs to squash those commits together. But @DhairyaBahl there's more warning messages about |
|
It would also be nice if you give good name for your PR. For example "Fix gcc wreorder warning" or something like that. |
|
@Keyikedalube Actually I reverse merged the commits from synfig/master to my own dhairyabahl/master that's why it shows merged. I will now fix the other wreorder warnings. Thanks for support :) |
|
@Keyikedalube I tried to find out other wreorder issues under the workarea class but everything seems to be in proper position. Thanks :) |
|
@DhairyaBahl I guess you are building synfig without cleaning. That's why you are not seeing other -Wreorder messages. You must clean your previous build files and build from start again to see all the warning messages pop up on your console or IDE build log. The thing about the buildsystem is it is smart to not compile unmodified files all over again every time you build. When you modified the workarea file, make (or whatever build generator you used) compiled only that file. All the other cpp source files weren't needed to be compiled again. Saving you build time... |
different class |
|
@Keyikedalube Okay thanks for guidance. I will find those errors and rectify them ASAP. Thanks :) |
be1155f to
ecd77f5
Compare
|
@ice0 @Keyikedalube I have made changes for all the wreorder warnings that were shown in the console. Kindly look into my PR. Thanks :) |
|
@DhairyaBahl please fix indents. Synfig uses tabs instead of spaces. You can see difference on this tab: https://github.com/synfig/synfig/pull/1750/files |
|
@ice0 Ok. I am on it . Thanks 👍 |
03fab64 to
d29cfdb
Compare
|
@ice0 @Keyikedalube I rectified the unnecessary use of spaces and properly used tabs there. Can anyone tell me now how to convert 4 commits into 1 ?? Thanks :) |
DeepCode failed to analyze this pull requestSomething went wrong despite trying multiple times, sorry about that. |
d29cfdb to
0048b88
Compare
Fixing Wreorder warnings Update vectorizersettings.cpp Update state_bone.cpp
0048b88 to
a5f1b2d
Compare
|
Retry DeepCode |
Yes |
|
@DhairyaBahl But wait for ice0 to tell you when. Don't squash now. |
|
@Keyikedalube sorry, I already did that 😅 |
|
@DhairyaBahl Doesn't matter :) You can still squash even after making review changes. |
|
@Keyikedalube got it. Thanks :) |
|
@ice0 @Keyikedalube I just completed my 4 valid hacktoberfest PRs. what should I do next?? Take another issue ?? Thanks for help ;) |
|
@DhairyaBahl of course! Any help is appreciated! |
|
Merged. Thank you! |
|
@Keyikedalube @ice0 Please guide me what steps should I take if I want to get in GSOC with this organisation ?? @AYESDIE what should I do ?? I mean I saw ur name in the Ex-Gsocer ? Bro Kindly guide me !! Thanks :) |
|
Just continue to learn the code and make contributions. We haven't decided on ideas for next year, so maybe you can come up with your own idea. |
|
@ice0 I will keep contributing in this and will also read that linked documentation just keep guiding me like you are doing sir. Thanks 👍 Will Do My Best !! |
@DhairyaBahl I opened issues that are too easy to solve so new contributors like you can get familiar with synfig codebase. GSOC will be more problem solving rather than minor fixes here and there like mine. I would suggest you to take up issues that need creative problem solving. That way I guarantee you'll be ahead of the beginners curve :)
Up to you :) Me personally I do my own gtkmm project first. I do my learning there, apply documentation/tutorials knowledge I studied, and then come back here to solve issues that I'm familiar with ;) |
|
@Keyikedalube Thanks for the advice of solving more creative problems but don't you think its a little early to start my own project. Thanks a lot for the whole idea ;) |
Fix GCC Wreorder warning in the line 209. Do i have to change it elsewhere. Kindly guide
Thanks :)