Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Issues with transparency with psevents

Aperta
  • Qualcosa non va?
#8,775 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Esteban82 ci sta già lavorando.

Dal 8/8/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

feature request

I created an earthquake animation (similar to Animation 8) and wanted the events to appear with transparency. I noticed a few issues: currently, transparency is only supported during the coda phase, which only exists for events with finite duration.

What confuses me is that transparency behaves differently from other properties, such as size or color (see figure below). I’m wondering if there’s a deeper reason why transparency was implemented this way and I’m just not seeing it.

Image

I think I could make the modifications in the source file, but I might need some help.

Issues observed
  1. The -t option is not available for events.
  2. Transparency is hard-wired to 0 in the plateau, decay, and normal phases. See lines 839, 846, and 851.
  3. Two transparency values can be set with -Mtval1[+cval2]. It seems that the first value (val1) is only used in the previous phase (with a transition in the rise phase). For symbols, this makes little sense since their size is set to 0 at that point—perhaps it’s more relevant for text?
  4. Transparency works fine in the fade and coda phases.
Help needed

I believe I can implement the required changes, but right now I would appreciate:

  1. Any comments on how transparency is supposed to work—how Paul originally intended it.
  2. Confirmation that I can safely use the undocumented psevents -/ options to get the event functions at t = 0. See line 629.
Lingua principale
C
Stelle
984
Fork
413
Merge medio
22h 10m
PR unite (30g)
35

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di GenericMappingTools/gmt

Tutte le issue di GenericMappingTools/gmt

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.