kpanelextension

Aaron J. Seigo aseigo at olympusproject.org
Thu May 23 20:34:06 BST 2002


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On May 23, 2002 01:10 pm, John Firebaugh wrote:
> On Thursday 23 May 2002 11:06, Aaron J. Seigo wrote:
> > it handled position and orientation, but not size (!) ... very strange.
>
> The idea is that it's the extension itself that decides the size, hence the
> sizeHint() method. Setting a size (like Small, Normal, Large, Custom, etc.)
> is appropriate only for the child panel extension. Other extensions may
> decide the size based on their position and the desktop size.

i understand what you are saying, however the panel can simply always default 
to its own custom size in the sizeHint. this is simply a way to send 
configuration changes regarding size to those panels that listen to such 
things. much in the same way that positionChange and alignmentChange can be 
optionally reimplemented.

> > attached is the patch again KPanelExtension. thoughts? ideas? magic wand
> > waving that will make this unecessary?
>
> It would probably be ok to break BC in this case,

well, i'll have to rethink this anyways since BC is not ok

> but I don't think that
> the change you are suggesting is appropriate. What leads you to want to do
> this?

specifically: getting size information from kicker's kcm to the individual 
extensions. when updating the Size, child panels just sit there since they 
are never informed of the size change. when the position or alignment is 
changed, the child panels immediately take up the new settings since they are 
notified of those changes via KPanelExtension.

i can't simply tie size changing to position or orientation changes, either, 
since those may not change when the size does.

position, alignment and size are all, IMO, common to panels. whether a panel 
uses Tiny / Small / Normal / Large or always Custom is irrelevant. this 
common parameter is not settable from the "outside", unlike every other 
parameter.

from the user's perspective, this is perplexing. why can't they change the 
size of a child panel from the kcm, but they can change the position, 
alignment, hiding, etc?
++
- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE87UQv1rcusafx20MRAg/lAJ93DlK8B0EyI0iIhfwN0YJhQimKRgCfUgl3
vxnOA7uJzAy5ZpLcKYwoKdc=
=9CCU
-----END PGP SIGNATURE-----





More information about the kde-core-devel mailing list