# gravity

Published articles for gravity.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Geometry Nodes Physics

DevFeed: [Geometry Nodes Physics](<https://devfeed.tech/articles/geometry-nodes-physics-19185.md>)

Original publisher: [Read original article](<https://code.blender.org/2026/07/geometry-nodes-physics/>)

Author: Jacques Lucke

Published: 2026-07-30T14:52:49Z

Content type: article

Language: en

Sources: [Blender](<https://devfeed.tech/sources/blender.md>)

Topics: [Simulation](<https://devfeed.tech/topics/simulation.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [systems](<https://devfeed.tech/topics/systems.md>)

Tags: [blender](<https://devfeed.tech/tags/blender.md>), [collection](<https://devfeed.tech/tags/collection.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [features](<https://devfeed.tech/tags/features.md>), [general-development](<https://devfeed.tech/tags/general-development.md>), [geometry-nodes](<https://devfeed.tech/tags/geometry-nodes.md>), [gravity](<https://devfeed.tech/tags/gravity.md>), [lts](<https://devfeed.tech/tags/lts.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [node](<https://devfeed.tech/tags/node.md>), [physics](<https://devfeed.tech/tags/physics.md>), [procedural](<https://devfeed.tech/tags/procedural.md>), [systems](<https://devfeed.tech/tags/systems.md>), [vectors](<https://devfeed.tech/tags/vectors.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

This article describes Blender 5.2 LTS's new experimental hair and cloth dynamics system built with Geometry Nodes. It explains the declarative XPBD simulation framework, cloth and hair workflows, geometry bundles, and customizable effectors such as colliders, custom forces, and custom behavior closures.

### Source excerpt

Geometry Nodes Physics in Blender 5.2 LTS and beyond.

## Diagnosing Incorrect Results in a MongoDB Geospatial Radius Query

DevFeed: [Diagnosing Incorrect Results in a MongoDB Geospatial Radius Query](<https://devfeed.tech/articles/are-you-using-the-right-mongo-geospatial-query-19163.md>)

Original publisher: [Read original article](<https://artsy.github.io/blog/2023/02/10/mongo-geospatial-queries/>)

Published: 2023-02-10T00:00:00Z

Content type: article

Language: en

Sources: [Artsy](<https://devfeed.tech/sources/artsy.md>)

Topics: [MongoDB](<https://devfeed.tech/topics/mongodb.md>), [Rails](<https://devfeed.tech/topics/rails.md>), [API](<https://devfeed.tech/topics/api.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [code](<https://devfeed.tech/tags/code.md>), [data](<https://devfeed.tech/tags/data.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [geospatial](<https://devfeed.tech/tags/geospatial.md>), [gravity](<https://devfeed.tech/tags/gravity.md>), [json](<https://devfeed.tech/tags/json.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [rails](<https://devfeed.tech/tags/rails.md>)

### AI overview

This article investigates why a MongoDB geospatial query omitted a gallery from Los Angeles exhibition listings. By widening the radius and visualizing the results, it finds that points near the left and right edges of the circle were incorrectly omitted.

### Source excerpt

We recently got a report from one of our galleries in the Los Angeles area that they weren't showing up on our Los Angeles exhibition listings. I fielded the report and right away confirmed: when we asked our core API for /shows?near=<los angeles coordinates>, sure enough this gallery partner didn't make the cut. Turns out they are based in Santa Monica, a separate and neighboring municipality. They must not be within the 25km radius that we use by default for these sorts of queries. Case closed. Or so I thought. After some back and forth with our partner I decided to investigate more thoroughly, this time using some tricks of the trade from my other life outside of Artsy. Casting a wider net If there was something wrong with our 25km radius query, I wanted to start by casting a wider net and visualizing the results. I consulted our Rails application code to find the query logic in question, and then issued the same query directly to MongoDB. Something like the following query (simplified for clarity): // a $geoWithin $center query db.events.find({ coordinates: { $geoWithin: { $center: [[-118.24, 34.05], 25 / 111.32], }, }, }) In the query above we are asking MongoDB to give us all events within a 25km radius around the point 34.05°N, 118.24°W which we have designated as a central point within Los Angeles. For our purposes in this post we can consider "events" ~= "exhibitions" ~= "shows." We are not asking for the 25km radius directly, but rather converting it into an equivalent amount of geographic degrees by using a conversion factor of 1° ~= 111.32 kilometers, a factor which is true at enough the equator. I modified the above query to cast a 50km net in order to see if there were some edges cases that needed scrutiny. Taking the resulting JSON response, I fired up Placemark, my favorite new tool for wrangling geospatial data. (Incidentally I recommend reading Tom Macwright's recent reflection on creating Placemark as a bootstrapped indie developer.) All shows within

## Controlling TextView MinWidth

DevFeed: [Controlling TextView MinWidth](<https://devfeed.tech/articles/controlling-textview-minwidth-38652.md>)

Original publisher: [Read original article](<https://krossovochkin.com/posts/2021_09_14_controlling_textview_minwidth/>)

Published: 2021-09-14T00:00:00Z

Content type: tutorial

Language: en

Sources: [Vasya Drobushkov](<https://devfeed.tech/sources/vasya-drobushkov.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [constraintlayout](<https://devfeed.tech/topics/constraintlayout.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-layout](<https://devfeed.tech/tags/android-layout.md>), [background](<https://devfeed.tech/tags/background.md>), [constraintlayout](<https://devfeed.tech/tags/constraintlayout.md>), [gravity](<https://devfeed.tech/tags/gravity.md>), [layout](<https://devfeed.tech/tags/layout.md>), [properties](<https://devfeed.tech/tags/properties.md>), [textview](<https://devfeed.tech/tags/textview.md>), [xml](<https://devfeed.tech/tags/xml.md>)

### AI overview

A technical explanation of how Android TextView minimum-width APIs interact. Setting minWidth or minimumWidth alone may not reset a dimension declared in XML; both properties must be cleared, and a background can still impose a minimum width.

### Source excerpt

Introduction Sometimes we might need our TextView with wrap_content width to occupy more space than it will based on amount of characters it displays. For that we can set minimum width. Usually, we do that via XML like this: <?xml version="1.0" encoding="utf-8"?> <androidx.constraintlayout.widget.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android" xmlns:app="http://schemas.android.com/apk/res-auto" xmlns:tools="http://schemas.android.com/tools" android:layout_width="match_parent" android:layout_height="match_parent" tools:context=".MainActivity"> <TextView android:id="@+id/textView" android:layout_width="wrap_content" android:layout_height="wrap_content" android:background="@drawable/bg_text" android:gravity="center" android:minWidth="200dp" android:text="Hello World!" app:layout_constraintBottom_toBottomOf="parent" app:layout_constraintLeft_toLeftOf="parent" app:layout_constraintRight_toRightOf="parent" app:layout_constraintTop_toTopOf="parent" /> </androidx.constraintlayout.widget.ConstraintLayout> Having setup like this we ensure that our TextView will occupy a minimum of 200dp. Also, we can control minimum width programmatically via: TextView#setMinWidth. But controlling minimum width programmatically has one caveat that I'd like to describe below.