Extremely Time-Costly Flaw

I do a bunch of tinkering and fidgeting with pieces on Roll20. I try and make things look pretty authentic, so I often wind up doing things like building a wall with multiple linked pieces instead of 1 stretched piece. Grouping in Roll20, however, has proven to be very counter intuitive. The first time you click on a grouped item, if you move your mouse, you'll also drag an INDIVIDUAL piece from within the group, which is counter-intuitive, as now my "grouped" item is no longer in its proper spot. Similarly, drawings grouped with snap-to-grid items do not move with their grid locked counterparts. For instance,if I want to fill a usually empty circle (say an emtpy well) with a colored circle (yay! now the well has water), and then group the items to move them over to where I want them on the map, the well will move slightly to adjust to the grid, but the circle will not. I manage to find work arounds and ad-hoc solutions, but I would love to see this addressed as each time something like this happens, it sets me back,

Yeah - I experience this as well. I've found two things to be extremely helpful. 1.) Group the objects. 2.) Click on "is Drawing" in the right-click menu This works most of the time. Also - be careful what item you are clicking on when moving a group. Try to click on the item in the group that is farthest back in layers. So - for your well issue, I'd make the water the bottom layer and try and carefully click on the CENTER of that layer to drag the group around. Alternately - you can build maps in GIMP or pyromancer.com and import them in. pyromancer.com isn't as nice (IMO) as the roll20 map maker. GIMP has a fairly steep learning curve (for old timers like me), but is extremely powerful.

Grouping the objects is what I'm talking about. Like I open the menu and actually group them. and then I make them both drawings. but I still pick up only one of said group if I don't double click or click and hold. I feel like it should be properly addressed. the code should be looked at. Not sure if its not just a latency in loading the code or what, but it is driving me nuts.