Bug 7763 - Cannot access Gdk rectangles in perl Gtk3
Summary: Cannot access Gdk rectangles in perl Gtk3
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-10 17:56 CEST by Juergen Harms
Modified: 2012-10-16 09:09 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Demo program to illustrate the problem (617 bytes, application/x-perl)
2012-10-10 17:58 CEST, Juergen Harms
Details

Description Juergen Harms 2012-10-10 17:56:39 CEST
Description of problem:

Exploring the migration of an application from perl-Gtk2 to perl-Gtk3, I have a problem to access a Gdk::Rectangle obtained as return value from a call of the 
"get_iter_location method of Gtk3::Textview.

Although the return value looks like a valid hash with the expected keys (x, y, width, height), an access to the hash elements (for example the "x" key) fails with.

   Can't call method "x" on unblessed reference at ./win.pl line 23.

My impression is that the method is missing because there is no Gtk3::Gdk module (I had a similar problem with Pango::TabArray, but simply using Gtk2::Pango appears a valid workaround). In this case, I have not found a workaround.

Version-Release number of selected component (if applicable):
perl-Gtk3-0.8.0-1.mga3

How reproducible:
100%

Steps to Reproduce:
1. Run the small demo program joined as an attachment
2.
3.
Comment 1 Juergen Harms 2012-10-10 17:58:26 CEST
Created attachment 2937 [details]
Demo program to illustrate the problem
Comment 2 Juergen Harms 2012-10-16 09:07:33 CEST
I just realised that my example has a flaw (access to the x_rect rectangle hash). Sorry for the false alarm.
Juergen Harms 2012-10-16 09:09:07 CEST

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.