Skip to content

Conversation

@Sepp62
Copy link
Contributor

@Sepp62 Sepp62 commented Jun 13, 2019

Dont't know, if you really want to merge this code in such an early state. For my purpose, it is sufficient, I do not plan to make it more sophisticated (except bug fixing).

@cujomalainey cujomalainey self-assigned this Jun 14, 2019
Copy link
Owner

@cujomalainey cujomalainey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good, excellent first start. Let's add the Travis CI change, that way we can get a compile test done. As long as it compiles and doesn't contain debug code and is correct then I have no problem doing incremental merges 😃

@cujomalainey
Copy link
Owner

Oh also can you amend that commit so it mentions what it is changing so when people look through the git log they know what the change is without looking at the diff?

@Sepp62 Sepp62 changed the title First shot, not yet fully tested New profile Shifting/Shifter. Initial checkin. Jun 14, 2019
@cujomalainey
Copy link
Owner

Looks like you only changed the pull request, not the commit, no worries, I can change it after its submitted, we may have to deal with some merge conflicts after. Its not the easiest thing to change, if you think you are up for it you can read up on here otherwise I will fix it up after the PR lands :)

Copy link
Owner

@cujomalainey cujomalainey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bit math looks good, only a few changes left then this will be ready for merge :)

@cujomalainey
Copy link
Owner

also bit math looks good 👍

@cujomalainey
Copy link
Owner

You can fetch and merge the branch core/base-master and you will get the ProductInformationMsg and ManufacturersInformationMsg which you can use to replace the temp data buffers.

Copy link
Owner

@cujomalainey cujomalainey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good but it looks like you merged your copy of develop which had both lev and moxy in the branch, I want to keep them isolated still till I have time to fully flesh out the profile. If its easier for you I can merge this, rebase the commits so the proper merge happens and then force push the branch, then you will just have to force sync on your end. Up to you :) Otherwise the shifting stuff looks great :)

.DS_Store
.tags*
tags
examples/BikeSensorConverter/arduino_secrets.h
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Accidental add?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this was accidentally. Sorry.

@@ -0,0 +1,352 @@
/**********************************************
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if you meant to commit your project to the examples. If you want to commit this to the repo we should do it not on the shifting branch since it uses multiple profiles :) The project is looking good, you will have to tell me more about what it does.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This happened by mistake. Can you remove it from the pull request ? We can talk about adding it to the examples, when it is thoroughly tested.

@@ -0,0 +1 @@
#define SECRET_ANTNETWORK_KEY {0x00, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77}
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Accidental commit?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, accidental.

@@ -0,0 +1,206 @@
/**********************************************
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was no merge from the LEV branch so I am not sure how this got in here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pooh. Seems I need to work at my understanding for github...

@@ -0,0 +1,60 @@
/**********************************************
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there was no merge from the MOxy branch, accidental merge into develop?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, accidental. See above.

// setup shifting monitor
shift.createShiftingSystemStatusMsg(shiftCreateMsgHandler);
shift.createShiftingManufacturerInformationMsg(shiftCreateManufacturerInformationMsg);
shift.createShiftingProductInformationMsg(shiftCreateProductInformationMsg);
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good, I forgot to implement batterystatus which needs a TODO here :)

@Sepp62
Copy link
Contributor Author

Sepp62 commented Jun 22, 2019

Looking good but it looks like you merged your copy of develop which had both lev and moxy in the branch, I want to keep them isolated still till I have time to fully flesh out the profile. If its easier for you I can merge this, rebase the commits so the proper merge happens and then force push the branch, then you will just have to force sync on your end. Up to you :) Otherwise the shifting stuff looks great :)

Yes, would be great, if you could properly merge to the profile branches and throw the unwanted sources out. Thank. Next time, I will try to be more thorough.

@cujomalainey
Copy link
Owner

Ok sounds good, I'll merge this, then force push a rebased version. Your local copy will likely complain that you are out of sync and try and merge your local branch into my new branch, you don't want to do that since it will add all the bugs back. You will want to delete your local shifting branch and re-create it on top of my branch once I have pushed it. I will send you an email once that is done.

@cujomalainey cujomalainey merged commit 2a8b69e into cujomalainey:profiles/shifting/shifter Jun 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants