I'm not a Python programmer but just intuitively it seems like if i==0 will make the first block fall right after it's created. Shouldn't it be if i==25? Or does it work because the loop has time to generate all the other blocks before the first block has time to hit the second one?
this post was submitted on 20 Oct 2024
14 points (100.0% liked)
Python
6392 readers
43 users here now
Welcome to the Python community on the programming.dev Lemmy instance!
π Events
Past
November 2023
- PyCon Ireland 2023, 11-12th
- PyData Tel Aviv 2023 14th
October 2023
- PyConES Canarias 2023, 6-8th
- DjangoCon US 2023, 16-20th (!django π¬)
July 2023
- PyDelhi Meetup, 2nd
- PyCon Israel, 4-5th
- DFW Pythoneers, 6th
- Django Girls Abraka, 6-7th
- SciPy 2023 10-16th, Austin
- IndyPy, 11th
- Leipzig Python User Group, 11th
- Austin Python, 12th
- EuroPython 2023, 17-23rd
- Austin Python: Evening of Coding, 18th
- PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th
August 2023
- PyLadies Dublin, 15th
- EuroSciPy 2023, 14-18th
September 2023
- PyData Amsterdam, 14-16th
- PyCon UK, 22nd - 25th
π Python project:
- Python
- Documentation
- News & Blog
- Python Planet blog aggregator
π Python Community:
- #python IRC for general questions
- #python-dev IRC for CPython developers
- PySlackers Slack channel
- Python Discord server
- Python Weekly newsletters
- Mailing lists
- Forum
β¨ Python Ecosystem:
π Fediverse
Communities
- #python on Mastodon
- c/django on programming.dev
- c/pythorhead on lemmy.dbzer0.com
Projects
- PythΓΆrhead: a Python library for interacting with Lemmy
- Plemmy: a Python package for accessing the Lemmy API
- pylemmy pylemmy enables simple access to Lemmy's API with Python
- mastodon.py, a Python wrapper for the Mastodon API
Feeds
founded 1 year ago
MODERATORS
Good question - it's the latter: all the blocks are generated practically instantaneously, whereas it does take a noticeable amount of time for the first block to hit the next one.
if i==25 would only result in the last block falling down, the rest would remain standing.a
Oh that makes sense - apparently bpy.ops has a current context that the transform acts on. Instead could you move the transform call outside of the loop after establishing the first block as the context? That's how I would instinctively do it, to avoid checking i in every iteration when I know it can only be true once. Totally minor critique lol.
that makes sense! if I find the time, I'll update it. it needs to updated to a newer Blender version anyway....