Re: course in the making
Posted: Fri Aug 30, 2019 2:01 am
Hi @Pratikm78
Yes its going well. If all goes to plan, it will be ready sometime in October
Yes its going well. If all goes to plan, it will be ready sometime in October
Page 2 of 2
Re: course in the making
Posted: Tue Oct 08, 2019 6:05 pm
That's great to looking forward to seeing your course this month. What is the name of course when you release it on udemy?
Re: course in the making
Posted: Wed Oct 09, 2019 1:11 am
I would like to see how arduino address make menuconfig. It would be interesting to see how Arduino can make changes to these settings.
Re: course in the making
Posted: Sat Nov 16, 2019 9:47 am
Its here! 
Head over to http://learnesp32.com and enjoy
I decided to try it without Udemy.
Once you sign up you'll be able to see the first few videos free!
Let me know if you have any questions or comments
Head over to http://learnesp32.com and enjoy
I decided to try it without Udemy.
Once you sign up you'll be able to see the first few videos free!
Let me know if you have any questions or comments
Re: course in the making
Posted: Sat Nov 16, 2019 3:47 pm
Thanks for the update!
Concerning your VSCode install video. I would like to share something with you that I use to help with all the command line stuff.
You can still do the command line stuff like you showed, but this will add icon buttons to just to click on.
If you look at the bottom of the image your will notice the new buttons to click on.
You can even get to menuconfig as well
You will need to add the following 2 extensions first.
#1) vscode-icons-team.vscode-icons
#2) seunlanlege.action-buttons
After this, you need to alter the settings.json file to add "actionButtons". This is what mine looks like.
A couple of notes.
#1) When you open a project folder for teh first time, the first thing is click "view", then "Terminal" you will get a popup asking for access make sure to click allow, then you will not have to do that anymore.
#2) Concerning menuconfig, if your terminal window is to small it will give a warning saying "Your display is too small to run Menuconfig!. All you need to do is click on the separation line in the terminal with your mouse and slide it up to make that window larger like in my image, then click on menuconfig again and it will open it.
#3) if you make any changes to settings.json, like say you want to change the com port or add a new command, first save it, then click the tiny red refresh icon for it to accept changes.
Lastly, I have this in my c_cpp_properties.json file.
"${env:IDF_PATH}/components/**",
This kept me from entering all the many "${IDF_PATH}/components/bla.bla.bla" folders to it.
Concerning your VSCode install video. I would like to share something with you that I use to help with all the command line stuff.
You can still do the command line stuff like you showed, but this will add icon buttons to just to click on.
If you look at the bottom of the image your will notice the new buttons to click on.
- 1.jpg (148.3 KiB) Viewed 5744 times
You can even get to menuconfig as well
- 2.jpg (163.22 KiB) Viewed 5744 times
You will need to add the following 2 extensions first.
#1) vscode-icons-team.vscode-icons
#2) seunlanlege.action-buttons
After this, you need to alter the settings.json file to add "actionButtons". This is what mine looks like.
A couple of notes.
#1) When you open a project folder for teh first time, the first thing is click "view", then "Terminal" you will get a popup asking for access make sure to click allow, then you will not have to do that anymore.
#2) Concerning menuconfig, if your terminal window is to small it will give a warning saying "Your display is too small to run Menuconfig!. All you need to do is click on the separation line in the terminal with your mouse and slide it up to make that window larger like in my image, then click on menuconfig again and it will open it.
#3) if you make any changes to settings.json, like say you want to change the com port or add a new command, first save it, then click the tiny red refresh icon for it to accept changes.
Code: Select all
{
"terminal.integrated.shell.windows": "C:\\Program Files\\Git\\bin\\bash.exe",
"actionButtons": {
"defaultColor": "#ff0034", // Can also use string color names.
"commands": [
{
"name": "MenuConfig",
"color": "lime",
"command": "idf.py menuconfig",
},
{
"name": "Build",
"color": "orange",
"command": "idf.py build size",
},
{
"name": "Flash",
"color": "lime",
"command": "idf.py -p COM6 -b 1152000 flash",
},
{
"name": "Monitor",
"color": "orange",
"command": "idf.py -p COM6{ monitor",
},
{
"name": "Clean",
"color": "lime",
"command": "idf.py clean",
},
{
"name": "Full Clean",
"color": "orange",
"command": "idf.py fullclean",
},
]
},
"files.associations": {
"*.md": "markdown",
"*.mdx": "tdx",
"stdio.h": "c"
}
}
Lastly, I have this in my c_cpp_properties.json file.
"${env:IDF_PATH}/components/**",
This kept me from entering all the many "${IDF_PATH}/components/bla.bla.bla" folders to it.
Re: course in the making
Posted: Sat Nov 16, 2019 9:00 pm
That's an awesome tip!
It would be perfect if this didn't require extensions as dependencies though but none the less. thank you for your feedback
It would be perfect if this didn't require extensions as dependencies though but none the less. thank you for your feedback