Skip to content

Commit

Permalink
Fix spelling
Browse files Browse the repository at this point in the history
  • Loading branch information
nyalldawson committed Mar 24, 2021
1 parent bc4e84a commit 9747e1b
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/providers/wms/qgswmstsettingswidget.cpp
Expand Up @@ -184,7 +184,7 @@ void QgsWmstSettingsWidget::syncToLayer( QgsMapLayer *layer )
mStaticWmstStackedWidget->setCurrentIndex( 0 ); mStaticWmstStackedWidget->setCurrentIndex( 0 );
// why do we hide this widget? well, the second page of the stacked widget is considerably higher // why do we hide this widget? well, the second page of the stacked widget is considerably higher
// then the first and we don't want to show a whole bunch of empty vertical space which Qt will give // then the first and we don't want to show a whole bunch of empty vertical space which Qt will give
// in order to accomodate the vertical height of the non-visible second page! // in order to accommodate the vertical height of the non-visible second page!
mStaticStackedWidgetFrame->hide(); mStaticStackedWidgetFrame->hide();
} }
else else
Expand Down Expand Up @@ -270,7 +270,7 @@ void QgsWmstSettingsWidget::temporalPropertiesChange()
mStaticWmstStackedWidget->setCurrentIndex( 0 ); mStaticWmstStackedWidget->setCurrentIndex( 0 );
// why do we hide this widget? well, the second page of the stacked widget is considerably higher // why do we hide this widget? well, the second page of the stacked widget is considerably higher
// then the first and we don't want to show a whole bunch of empty vertical space which Qt will give // then the first and we don't want to show a whole bunch of empty vertical space which Qt will give
// in order to accomodate the vertical height of the non-visible second page! // in order to accommodate the vertical height of the non-visible second page!
mStaticStackedWidgetFrame->hide(); mStaticStackedWidgetFrame->hide();
} }
else else
Expand Down

0 comments on commit 9747e1b

Please sign in to comment.