diff options
| author | Tormod Volden <debian.tormod@gmail.com> | 2012-05-10 00:07:56 +0200 |
|---|---|---|
| committer | Tormod Volden <debian.tormod@gmail.com> | 2012-05-20 21:50:14 +0200 |
| commit | 1c71cf1ac48410a29b61c50330ee28306f0e7698 (patch) | |
| tree | af12f3c7ca14bb9af701eb2879d922b23c74b498 | |
| parent | e36ed34fd70fbd3b2e9e45c7189896e2db47a476 (diff) | |
fixup: duoview 5: rename bEnableActivate to allowEnabling
comment: Now that this function is so simple, and is only
used once, should we rather inline what is needed in the caller?
Or is there a possible future use for it?
| -rw-r--r-- | src/savage_vbe.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/src/savage_vbe.c b/src/savage_vbe.c index 2c8ecd0..5cca4cd 100644 --- a/src/savage_vbe.c +++ b/src/savage_vbe.c @@ -321,8 +321,8 @@ void SavageUpdateDevices(ScrnInfoPtr pScrn) /* Function to correct the DuoView flag in the case of a single display */ -int SavageCorrectDuoViewFlag(int iDevInfo, Bool bEnableActivate, - Bool bEnableDeactivate) +int SavageCorrectDuoViewFlag(int iDevInfo, Bool allowEnabling, + Bool allowDisabling) { /* TODO: limit this function to be used only if no multi view mode is * active ("real" DuoView) */ @@ -353,9 +353,9 @@ int SavageCorrectDuoViewFlag(int iDevInfo, Bool bEnableActivate, setDuoView = TRUE; /* action logic */ - if (setDuoView && bEnableActivate) + if (setDuoView && allowEnabling) iDevInfo |= DUO_ON; - if (!setDuoView && bEnableDeactivate) + if (!setDuoView && allowDisabling) iDevInfo &= ~DUO_ON; return iDevInfo; |