Great tutorials. I've learnt quite a lot. I should had seen your videos before I started trying to figure out the positioning of widgets by myself. In this video I've learnt a few things as well. BTW, I had issues with load_string in one of my projects and couldn't find out why. Terminal wasn't helpful much and I thought it must be because of the colors and markup. After seeing a few of your videos I thought the bug must be somewhere else. And it was! So, if anyone else has similar issue, if you want to use the new line ( ) in the load_string, it must be changed to \ . The second thing I figured out was, that if you write rgb in the common way without /255, it may work too, but it shows warnings then in the terminal. I guess I must have seen it somewhere because I thought it wasn't neccessary for some widgets. But it seems like it is always neccesary. I've got one question. Why is it neccessary to add the kivy version into the code? It works well even without it.
Hey, thank you for your great comments and your advice using new line characters! Regarding kiv.require, it checks the minimum version of kivy that must be used and will give you a warning if you're using a version that doesn't meet the minimum. If you leave out the kiv.require statement then your code will still work fine as long as you're using a kivy version that satisfies the minimum requirements. If you don't then your code might not work properly AND you won't get a warning. With the kiv.require statement you will get the warning so it's better to include it.
@@SCOBAS Cheers for that. I reckon it has no impact on apk file that I create, right? If the app works now without that note (in my tablet) I hope it will always work. Sure I've got no problems to add it into all files (from now on). I just wasn't sure if it's neccessary for any specific reason. Also, I mix vs code, pycharm, virtual env, normal env....Installing kivy wasn't easy either, OOP is harder than tkinter... I'm glad I've got something that works atm and I can use it to some extent:-) Every day something new...
Great tutorials. I've learnt quite a lot. I should had seen your videos before I started trying to figure out the positioning of widgets by myself. In this video I've learnt a few things as well. BTW, I had issues with load_string in one of my projects and couldn't find out why. Terminal wasn't helpful much and I thought it must be because of the colors and markup. After seeing a few of your videos I thought the bug must be somewhere else. And it was! So, if anyone else has similar issue, if you want to use the new line (
) in the load_string, it must be changed to \
. The second thing I figured out was, that if you write rgb in the common way without /255, it may work too, but it shows warnings then in the terminal. I guess I must have seen it somewhere because I thought it wasn't neccessary for some widgets. But it seems like it is always neccesary.
I've got one question. Why is it neccessary to add the kivy version into the code? It works well even without it.
Hey, thank you for your great comments and your advice using new line characters!
Regarding kiv.require, it checks the minimum version of kivy that must be used and will give you a warning if you're using a version that doesn't meet the minimum. If you leave out the kiv.require statement then your code will still work fine as long as you're using a kivy version that satisfies the minimum requirements. If you don't then your code might not work properly AND you won't get a warning. With the kiv.require statement you will get the warning so it's better to include it.
@@SCOBAS Cheers for that. I reckon it has no impact on apk file that I create, right? If the app works now without that note (in my tablet) I hope it will always work. Sure I've got no problems to add it into all files (from now on). I just wasn't sure if it's neccessary for any specific reason. Also, I mix vs code, pycharm, virtual env, normal env....Installing kivy wasn't easy either, OOP is harder than tkinter... I'm glad I've got something that works atm and I can use it to some extent:-) Every day something new...
@elevendarter112 oh yes, every day something new. So much to discover 😄