Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
vala
vala
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 701
    • Issues 701
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 39
    • Merge Requests 39
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GNOME
  • valavala
  • Issues
  • #84

Closed
Open
Opened Apr 09, 2010 by bugzilla-migration@bugzilla-migrationReporter

Type-ify notify connects

Submitted by Fabian Deutsch

Link to original bug (#615262)

Description

Currently I can connect to property changes by using

obj["prop_name"].connect( ... );

The problem with this syntax is, that I can connect to signals that do not exist or were deprecated and vanished.

A solution would be to change the syntax, so a syntax check can be performed, two possibilities:

obj.prop.connect( ... )

obj.notify.prop.connect( ... )

Blocking

  • Bug 620177
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/vala#84