Bug 610 – QWidgetItemV2 not exposed to Python

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 610 - QWidgetItemV2 not exposed to Python

Summary:

QWidgetItemV2 not exposed to Python

Status:	CLOSED WONTFIX

Product:	PySide
Classification:	Unclassified
Component:	PySide
Version:	1.0.0 beta3
Platform:	All All

Importance:	P2 normal
Assigned To:	renato filho

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-01-13 14:36 EET by Patrick Hartling
Modified:	2011-01-21 15:44 EET (History)
CC List:	8 users (show)

See Also:

Attachments
Patch to expose QWidgetItemV2 to Python (1.66 KB, patch) 2011-01-13 14:36 EET, Patrick Hartling	Details
Add an attachment (proposed patch, testcase, etc.)

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

Description Patrick Hartling 2011-01-13 14:36:34 EET

Created attachment 219 [details]
Patch to expose QWidgetItemV2 to Python

When running PySide and Shiboken with debugging enabled, I saw a lot of
warnings about QWidgetItemV2 not being available. The attached patch exposes
this type to Python.

Comment 1 Matti Airas 2011-01-14 07:36:13 EET

Thanks for the patch! Prioritizing P2. I wonder is the class hidden on purpose,
though, because it's not present in Qt documentation, either?

Comment 2 Hugo Parente Lima 2011-01-18 17:48:19 EET

I also think we don't need to bind this class. Any non-documented Qt class is
considered private and should not be used.

PyQt also doesn't bind this class.

Anyway, do you really need this to have access to this class? if so, why?

Comment 3 Patrick Hartling 2011-01-18 18:12:25 EET

(In reply to comment #2)
> I also think we don't need to bind this class. Any non-documented Qt class is
> considered private and should not be used.
> 
> PyQt also doesn't bind this class.

That's fine.

> Anyway, do you really need this to have access to this class? if so, why?

I saw run-time warnings about it not being bound when running with
debug-enabled builds of Shiboken and PySide. I assumed that the warnings were
displayed for a reason. We do not need this class for anything we are doing.

Comment 4 Hugo Parente Lima 2011-01-18 18:28:39 EET

Don't worry about this runtime warnings, they appear when any internal Qt class
is returned by Qt, e.g.

// Class not exported by Qt
class QInternalClass : public QSomeQtInterface {};

and Qt code has:

QSomeInterface* getMyInterface() { return new QInternalClass; }

This happens a lot with e.g. QTextCodec, because Qt only exports the QTextCodec
interface but implements a lot of subclasses, one for each supported text
codec, so I'll mark the bug as wont fix, anyway thanks for trying to help us.

The warnings appear on debug builds to help us to find some bugs related to the
type discovery mechanism

Comment 5 renato filho 2011-01-21 15:44:50 EET

release beta4