Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] d.vect.chart GUI does not select multiple columns

Open Beginner friendly
#6,012 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
desktop

Research direction

The GUI for d.vect.chart is implemented in Python using wxPython; locate the module file (likely in the Python scripts or GUI directory) and find the event handler for the columns text entry box. The handler currently replaces the text when a column is selected from the pull down list; modify it to append the selected column to a comma-separated list. Done looks like the GUI allowing multiple column selections that accumulate with commas.

Written by the indexing model from the issue text.

Description

bug GUI macOS

Describe the bug

The GUI for d.vect.chart will not insert multiple column names for the columns argument.

It does insert multiple values for the colors argument.

It would nice if it could also insert multiple column names in the size_column argument because sometimes the chart size is a function of the sum or product of multiple columns.

To reproduce

  1. Click on the text entry box for the columns argument
  2. You are promoted to select a column from a pull down list
  3. Click the text entry box again, and you are again prompted to select a column from the pull down list
  4. The new column replaces the initially selected column instead of adding a second column preceded by a comma.

Expected behavior

Columns should be added to a comma separated list

System description

  • Operating System: Mac OS 15.5
  • GRASS GIS version: 8.5 (and earllier)
Dominant language
C
Stars
1.2k
Forks
447
Avg merge
2d 10h
Merged PRs (30d)
107

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OSGeo/grass

All issues in OSGeo/grass

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.