text:
<?xml version="1.0" encoding="UTF-8"?>
<project version="4">
  <component name="CMakeRunConfigurationManager" shouldGenerate="true" assignedExecutableTargets="true" buildAllGenerated="true">
    <generated>
      <config projectName="chess_solver" targetName="chess_solver" />
    </generated>
  </component>
  <component name="CMakeSettings" AUTO_RELOAD="false" GENERATION_PASS_SYSTEM_ENVIRONMENT="true">
    <ADDITIONAL_GENERATION_ENVIRONMENT>
      <envs />
    </ADDITIONAL_GENERATION_ENVIRONMENT>
  </component>
  <component name="ChangeListManager">
    <list default="true" id="5f6bf884-420a-453f-8587-27ba22f8b858" name="Default" comment="k">
      <change type="MODIFICATION" beforePath="$PROJECT_DIR$/.idea/workspace.xml" afterPath="$PROJECT_DIR$/.idea/workspace.xml" />
      <change type="MODIFICATION" beforePath="$PROJECT_DIR$/board/Board.cpp" afterPath="$PROJECT_DIR$/board/Board.cpp" />
      <change type="MODIFICATION" beforePath="$PROJECT_DIR$/main.cpp" afterPath="$PROJECT_DIR$/main.cpp" />
    </list>
    <ignored path="chess_solver.iws" />
    <ignored path=".idea/workspace.xml" />
    <option name="EXCLUDED_CONVERTED_TO_IGNORED" value="true" />
    <option name="TRACKING_ENABLED" value="true" />
    <option name="SHOW_DIALOG" value="false" />
    <option name="HIGHLIGHT_CONFLICTS" value="true" />
    <option name="HIGHLIGHT_NON_ACTIVE_CHANGELIST" value="false" />
    <option name="LAST_RESOLUTION" value="IGNORE" />
  </component>
  <component name="ChangesViewManager" flattened_view="true" show_ignored="false" />
  <component name="CreatePatchCommitExecutor">
    <option name="PATCH_PATH" value="" />
  </component>
  <component name="ExecutionTargetManager" SELECTED_TARGET="default_target" />
  <component name="FavoritesManager">
    <favorites_list name="chess_solver" />
  </component>
  <component name="FileEditorManager">
    <leaf SIDE_TABS_SIZE_LIMIT_KEY="300">
      <file leaf-file-name="Game.cpp" pinned="false" current-in-tab="false">
        <entry file="file://$PROJECT_DIR$/game/Game.cpp">
          <provider selected="true" editor-type-id="text-editor">
            <state vertical-scroll-proportion="0.0">
              <caret line="39" column="0" selection-start-line="39" selection-start-column="0" selection-end-line="39" selection-end-column="0" />
              <folding>
                <element signature="e#39#58#0" expanded="true" />
              </folding>
            </state>
          </provider>
        </entry>
      </file>
      <file leaf-file-name="Board.cpp" pinned="false" current-in-tab="false">
        <entry file="file://$PROJECT_DIR$/board/Board.cpp">
          <provider selected="true" editor-type-id="text-editor">
            <state vertical-scroll-proportion="-6.0">
              <caret line="519" column="4" selection-start-line="519" selection-start-column="4" selection-end-line="519" selection-end-column="4" />
              <folding>
                <element signature="e#39#58#0" expanded="true" />
              </folding>
            </state>
          </provider>
        </entry>
      </file>
      <file leaf-file-name="Pawn.cpp" pinned="false" current-in-tab="false">
        <entry file="file://$PROJECT_DIR$/piece/pawn/Pawn.cpp">
          <provider selected="true" editor-type-id="text-editor">
            <state vertical-scroll-proportion="0.0">
              <caret line="0" column="2" selection-start-line="0" selection-start-column="2" selection-end-line="0" selection-end-column="2" />
              <folding />
            </state>
          </provider>
        </entry>
      </file>
      <file leaf-file-name="Board.h" pinned="false" current-in-tab="false">
        <entry file="file://$PROJECT_DIR$/board/Board.h">
          <provider selected="true" editor-type-id="text-editor">
            <state vertical-scroll-proportion="0.0">
              <caret line="62" column="39" selection-start-line="62" selection-start-column="39" selection-end-line="62" selection-end-column="39" />
              <folding />
            </state>
          </provider>
        </entry>
      </file>
      <file leaf-file-name="main.cpp" pinned="false" current-in-tab="true">
        <entry file="file://$PROJECT_DIR$/main.cpp">
          <provider selected="true" editor-type-id="text-editor">
            <state vertical-scroll-proportion="0.7178841">
              <caret line="83" column="35" selection-start-line="83" selection-start-column="35" selection-end-line="83" selection-end-column="35" />
              <folding>
                <element signature="e#0#19#0" expanded="true" />
              </folding>
            </state>
          </provider>
        </entry>
      </file>
      <file leaf-file-name="Piece.h" pinned="false" current-in-tab="false">
        <entry file="file://$PROJECT_DIR$/piece/Piece.h">
          <provider selected="true" editor-type-id="text-editor">
            <state vertical-scroll-proportion="0.0">
              <caret line="11" column="6" selection-start-line="11" selection-start-column="6" selection-end-line="11" selection-end-column="6" />
              <folding />
            </state>
          </provider>
        </entry>
      </file>
      <file leaf-file-name="King.h" pinned="false" current-in-tab="false">
        <entry file="file://$PROJECT_DIR$/piece/king/King.h">
          <provider selected="true" editor-type-id="text-editor">
            <state vertical-scroll-proportion="0.0">
              <caret line="21" column="11" selection-start-line="21" selection-start-column="11" selection-end-line="21" selection-end-column="11" />
              <folding />
            </state>
          </provider>
        </entry>
      </file>
    </leaf>
  </component>
  <component name="Git.Settings">
    <option name="RECENT_GIT_ROOT_PATH" value="$PROJECT_DIR$" />
  </component>
  <component name="IdeDocumentHistory">
    <option name="CHANGED_PATHS">
      <list>
        <option value="$PROJECT_DIR$/piece/Color.h" />
        <option value="$PROJECT_DIR$/piece/Moves.h" />
        <option value="$PROJECT_DIR$/piece/Move.h" />
        <option value="$PROJECT_DIR$/piece/Move.cpp" />
        <option value="$PROJECT_DIR$/Helper.cpp" />
        <option value="$PROJECT_DIR$/Helper.h" />
        <option value="$PROJECT_DIR$/piece/king/King.cpp" />
        <option value="$PROJECT_DIR$/piece/knight/Knight.cpp" />
        <option value="$PROJECT_DIR$/piece/rook/Rook.cpp" />
        <option value="$PROJECT_DIR$/piece/bishop/Bishop.cpp" />
        <option value="$PROJECT_DIR$/README.md" />
        <option value="$PROJECT_DIR$/piece/queen/Queen.h" />
        <option value="$PROJECT_DIR$/piece/rook/Rook.h" />
        <option value="$PROJECT_DIR$/piece/Piece.cpp" />
        <option value="$PROJECT_DIR$/piece/Piece.h" />
        <option value="$PROJECT_DIR$/piece/knight/Knight.h" />
        <option value="$PROJECT_DIR$/piece/bishop/Bishop.h" />
        <option value="$PROJECT_DIR$/piece/pawn/Pawn.h" />
        <option value="$PROJECT_DIR$/game/Stats.h" />
        <option value="$PROJECT_DIR$/CMakeLists.txt" />
        <option value="$PROJECT_DIR$/piece/king/King.h" />
        <option value="$PROJECT_DIR$/game/Stats.cpp" />
        <option value="$PROJECT_DIR$/seamule-sdk-c/src/response.c" />
        <option value="$PROJECT_DIR$/seamule-sdk-c/src/network.c" />
        <option value="$PROJECT_DIR$/seamule-sdk-c/src/api.c" />
        <option value="$PROJECT_DIR$/seamule-sdk-c/src/api.h" />
        <option value="$PROJECT_DIR$/piece/queen/Queen.cpp" />
        <option value="$PROJECT_DIR$/game/Game.h" />
        <option value="$PROJECT_DIR$/board/Board.h" />
        <option value="$PROJECT_DIR$/piece/pawn/Pawn.cpp" />
        <option value="$PROJECT_DIR$/game/Game.cpp" />
        <option value="$PROJECT_DIR$/board/Board.cpp" />
        <option value="$PROJECT_DIR$/main.cpp" />
      </list>
    </option>
  </component>
  <component name="JsBuildToolGruntFileManager" detection-done="true" />
  <component name="JsBuildToolPackageJson" detection-done="true" />
  <component name="JsGulpfileManager">
    <detection-done>true</detection-done>
  </component>
  <component name="ProjectFrameBounds">
    <option name="y" value="23" />
    <option name="width" value="1227" />
    <option name="height" value="709" />
  </component>
  <component name="ProjectLevelVcsManager" settingsEditedManually="false">
    <OptionsSetting value="true" id="Add" />
    <OptionsSetting value="true" id="Remove" />
    <OptionsSetting value="true" id="Checkout" />
    <OptionsSetting value="true" id="Update" />
    <OptionsSetting value="true" id="Status" />
    <OptionsSetting value="true" id="Edit" />
    <ConfirmationsSetting value="0" id="Add" />
    <ConfirmationsSetting value="0" id="Remove" />
  </component>
  <component name="ProjectView">
    <navigator currentView="ProjectPane" proportions="" version="1">
      <flattenPackages />
      <showMembers />
      <showModules />
      <showLibraryContents />
      <hideEmptyPackages />
      <abbreviatePackageNames />
      <autoscrollToSource />
      <autoscrollFromSource />
      <sortByType />
      <manualOrder />
      <foldersAlwaysOnTop value="true" />
    </navigator>
    <panes>
      <pane id="ProjectPane">
        <subPane>
          <PATH>
            <PATH_ELEMENT>
              <option name="myItemId" value="AjedrezProgramacionAvanzada" />
              <option name="myItemType" value="com.jetbrains.cidr.projectView.CidrFilesViewHelper$MyProjectTreeStructure$1" />
            </PATH_ELEMENT>
          </PATH>
          <PATH>
            <PATH_ELEMENT>
              <option name="myItemId" value="AjedrezProgramacionAvanzada" />
              <option name="myItemType" value="com.jetbrains.cidr.projectView.CidrFilesViewHelper$MyProjectTreeStructure$1" />
            </PATH_ELEMENT>
            <PATH_ELEMENT>
              <option name="myItemId" value="AjedrezProgramacionAvanzada" />
              <option name="myItemType" value="com.intellij.ide.projectView.impl.nodes.PsiDirectoryNode" />
            </PATH_ELEMENT>
          </PATH>
          <PATH>
            <PATH_ELEMENT>
              <option name="myItemId" value="AjedrezProgramacionAvanzada" />
              <option name="myItemType" value="com.jetbrains.cidr.projectView.CidrFilesViewHelper$MyProjectTreeStructure$1" />
            </PATH_ELEMENT>
            <PATH_ELEMENT>
              <option name="myItemId" value="AjedrezProgramacionAvanzada" />
              <option name="myItemType" value="com.intellij.ide.projectView.impl.nodes.PsiDirectoryNode" />
            </PATH_ELEMENT>
            <PATH_ELEMENT>
              <option name="myItemId" value="piece" />
              <option name="myItemType" value="com.intellij.ide.projectView.impl.nodes.PsiDirectoryNode" />
            </PATH_ELEMENT>
          </PATH>
          <PATH>
            <PATH_ELEMENT>
              <option name="myItemId" value="AjedrezProgramacionAvanzada" />
              <option name="myItemType" value="com.jetbrains.cidr.projectView.CidrFilesViewHelper$MyProjectTreeStructure$1" />
            </PATH_ELEMENT>
            <PATH_ELEMENT>
              <option name="myItemId" value="AjedrezProgramacionAvanzada" />
              <option name="myItemType" value="com.intellij.ide.projectView.impl.nodes.PsiDirectoryNode" />
            </PATH_ELEMENT>
            <PATH_ELEMENT>
              <option name="myItemId" value="piece" />
              <option name="myItemType" value="com.intellij.ide.projectView.impl.nodes.PsiDirectoryNode" />
            </PATH_ELEMENT>
            <PATH_ELEMENT>
              <option name="myItemId" value="pawn" />
              <option name="myItemType" value="com.intellij.ide.projectView.impl.nodes.PsiDirectoryNode" />
            </PATH_ELEMENT>
          </PATH>
          <PATH>
            <PATH_ELEMENT>
              <option name="myItemId" value="AjedrezProgramacionAvanzada" />
              <option name="myItemType" value="com.jetbrains.cidr.projectView.CidrFilesViewHelper$MyProjectTreeStructure$1" />
            </PATH_ELEMENT>
            <PATH_ELEMENT>
              <option name="myItemId" value="AjedrezProgramacionAvanzada" />
              <option name="myItemType" value="com.intellij.ide.projectView.impl.nodes.PsiDirectoryNode" />
            </PATH_ELEMENT>
            <PATH_ELEMENT>
              <option name="myItemId" value="board" />
              <option name="myItemType" value="com.intellij.ide.projectView.impl.nodes.PsiDirectoryNode" />
            </PATH_ELEMENT>
          </PATH>
        </subPane>
      </pane>
    </panes>
  </component>
  <component name="PropertiesComponent">
    <property name="recentsLimit" value="5" />
    <property name="settings.editor.selected.configurable" value="preferences.editor" />
    <property name="settings.editor.splitter.proportion" value="0.2" />
    <property name="js-jscs-nodeInterpreter" value="/usr/local/bin/node" />
    <property name="SearchEverywhereHistoryKey" value="	FILE	file:///Users/juanandrescarpio/Desktop/AjedrezProgramacionAvanzada/game/Game.cpp" />
  </component>
  <component name="RecentsManager">
    <key name="MoveFile.RECENT_KEYS">
      <recent name="$PROJECT_DIR$/piece" />
    </key>
  </component>
  <component name="RunManager" selected="Application.chess_solver">
    <configuration default="true" type="CMakeRunConfiguration" factoryName="Application" PASS_PARENT_ENVS="FALSE" PROJECT_NAME="chess_solver" TARGET_NAME="chess_solver" CONFIG_NAME="Debug">
      <envs />
      <method />
    </configuration>
    <configuration default="true" type="js.build_tools.gulp" factoryName="Gulp.js">
      <node-options />
      <gulpfile />
      <tasks />
      <arguments />
      <pass-parent-envs>true</pass-parent-envs>
      <envs />
      <method />
    </configuration>
    <configuration default="false" name="chess_solver" type="CMakeRunConfiguration" factoryName="Application" PASS_PARENT_ENVS="FALSE" PROJECT_NAME="chess_solver" TARGET_NAME="chess_solver" CONFIG_NAME="Debug" RUN_TARGET_PROJECT_NAME="chess_solver" RUN_TARGET_NAME="chess_solver">
      <envs />
      <method />
    </configuration>
    <configuration default="false" name="Build All" type="CMakeRunConfiguration" factoryName="Application" WORKING_DIR="" PASS_PARENT_ENVS="FALSE" CONFIG_NAME="Debug" RUN_TARGET_PROJECT_NAME="chess_solver" RUN_TARGET_NAME="chess_solver" EXPLICIT_BUILD_TARGET_NAME="all">
      <envs />
      <method />
    </configuration>
    <list size="2">
      <item index="0" class="java.lang.String" itemvalue="Application.chess_solver" />
      <item index="1" class="java.lang.String" itemvalue="Application.Build All" />
    </list>
  </component>
  <component name="ShelveChangesManager" show_recycled="false" />
  <component name="StructureViewFactory">
    <option name="AUTOSCROLL_FROM_SOURCE" value="true" />
    <option name="ACTIVE_ACTIONS" value=",INHERITORS_AND_CATEGORIES" />
  </component>
  <component name="SvnConfiguration">
    <configuration />
  </component>
  <component name="TaskManager">
    <task active="true" id="Default" summary="Default task">
      <changelist id="5f6bf884-420a-453f-8587-27ba22f8b858" name="Default" comment="" />
      <created>1446683194040</created>
      <option name="number" value="Default" />
      <updated>1446683194040</updated>
    </task>
    <servers />
  </component>
  <component name="TodoView">
    <todo-panel id="selected-file">
      <is-autoscroll-to-source value="true" />
    </todo-panel>
    <todo-panel id="all">
      <are-packages-shown value="true" />
      <is-autoscroll-to-source value="true" />
    </todo-panel>
  </component>
  <component name="ToolWindowManager">
    <frame x="0" y="23" width="1227" height="709" extended-state="0" />
    <editor active="false" />
    <layout>
      <window_info id="Project" active="false" anchor="left" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="true" show_stripe_button="true" weight="0.2835821" sideWeight="0.5" order="0" side_tool="false" content_ui="combo" />
      <window_info id="TODO" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.32961783" sideWeight="0.5" order="6" side_tool="false" content_ui="tabs" />
      <window_info id="CMake" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.32876712" sideWeight="0.5" order="7" side_tool="false" content_ui="tabs" />
      <window_info id="Event Log" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.33" sideWeight="0.5" order="7" side_tool="true" content_ui="tabs" />
      <window_info id="Version Control" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.3273906" sideWeight="0.5" order="7" side_tool="false" content_ui="tabs" />
      <window_info id="Structure" active="false" anchor="left" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.2203125" sideWeight="0.5" order="1" side_tool="false" content_ui="tabs" />
      <window_info id="Terminal" active="true" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="true" show_stripe_button="true" weight="0.267423" sideWeight="0.5" order="7" side_tool="false" content_ui="tabs" />
      <window_info id="Favorites" active="false" anchor="left" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.33" sideWeight="0.5" order="2" side_tool="true" content_ui="tabs" />
      <window_info id="Cvs" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.25" sideWeight="0.5" order="4" side_tool="false" content_ui="tabs" />
      <window_info id="Messages" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.26438355" sideWeight="0.5" order="7" side_tool="false" content_ui="tabs" />
      <window_info id="Message" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.33" sideWeight="0.5" order="0" side_tool="false" content_ui="tabs" />
      <window_info id="Commander" active="false" anchor="right" auto_hide="false" internal_type="SLIDING" type="SLIDING" visible="false" show_stripe_button="true" weight="0.4" sideWeight="0.5" order="0" side_tool="false" content_ui="tabs" />
      <window_info id="Inspection" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.4" sideWeight="0.5" order="5" side_tool="false" content_ui="tabs" />
      <window_info id="Run" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.36164382" sideWeight="0.5" order="2" side_tool="false" content_ui="tabs" />
      <window_info id="Hierarchy" active="false" anchor="right" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.25" sideWeight="0.5" order="2" side_tool="false" content_ui="combo" />
      <window_info id="Find" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.39615384" sideWeight="0.5" order="1" side_tool="false" content_ui="tabs" />
      <window_info id="Ant Build" active="false" anchor="right" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.25" sideWeight="0.5" order="1" side_tool="false" content_ui="tabs" />
      <window_info id="Debug" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.39863014" sideWeight="0.5" order="3" side_tool="false" content_ui="tabs" />
    </layout>
    <layout-to-restore>
      <window_info id="TODO" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.32961783" sideWeight="0.5" order="6" side_tool="false" content_ui="tabs" />
      <window_info id="Cvs" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.25" sideWeight="0.5" order="4" side_tool="false" content_ui="tabs" />
      <window_info id="Messages" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.26438355" sideWeight="0.5" order="7" side_tool="false" content_ui="tabs" />
      <window_info id="Message" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.33" sideWeight="0.5" order="0" side_tool="false" content_ui="tabs" />
      <window_info id="CMake" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.32876712" sideWeight="0.5" order="8" side_tool="false" content_ui="tabs" />
      <window_info id="Commander" active="false" anchor="right" auto_hide="false" internal_type="SLIDING" type="SLIDING" visible="false" show_stripe_button="true" weight="0.4" sideWeight="0.5" order="0" side_tool="false" content_ui="tabs" />
      <window_info id="Event Log" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.33" sideWeight="0.5" order="9" side_tool="true" content_ui="tabs" />
      <window_info id="Inspection" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.4" sideWeight="0.5" order="5" side_tool="false" content_ui="tabs" />
      <window_info id="Version Control" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.32876712" sideWeight="0.5" order="10" side_tool="false" content_ui="tabs" />
      <window_info id="Run" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.36164382" sideWeight="0.5" order="2" side_tool="false" content_ui="tabs" />
      <window_info id="Terminal" active="true" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="true" show_stripe_button="true" weight="0.36861312" sideWeight="0.5" order="11" side_tool="false" content_ui="tabs" />
      <window_info id="Project" active="false" anchor="left" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.27164418" sideWeight="0.5" order="0" side_tool="false" content_ui="combo" />
      <window_info id="Hierarchy" active="false" anchor="right" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.25" sideWeight="0.5" order="2" side_tool="false" content_ui="combo" />
      <window_info id="Find" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.39615384" sideWeight="0.5" order="1" side_tool="false" content_ui="tabs" />
      <window_info id="Structure" active="false" anchor="left" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.2203125" sideWeight="0.5" order="1" side_tool="false" content_ui="tabs" />
      <window_info id="Ant Build" active="false" anchor="right" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.25" sideWeight="0.5" order="1" side_tool="false" content_ui="tabs" />
      <window_info id="Favorites" active="false" anchor="left" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.33" sideWeight="0.5" order="2" side_tool="true" content_ui="tabs" />
      <window_info id="Debug" active="false" anchor="bottom" auto_hide="false" internal_type="DOCKED" type="DOCKED" visible="false" show_stripe_button="true" weight="0.39863014" sideWeight="0.5" order="3" side_tool="false" content_ui="tabs" />
    </layout-to-restore>
  </component>
  <component name="Vcs.Log.UiProperties">
    <option name="RECENTLY_FILTERED_USER_GROUPS">
      <collection />
    </option>
    <option name="RECENTLY_FILTERED_BRANCH_GROUPS">
      <collection />
    </option>
  </component>
  <component name="VcsContentAnnotationSettings">
    <option name="myLimit" value="2678400000" />
  </component>
  <component name="XDebuggerManager">
    <breakpoint-manager>
      <option name="time" value="144" />
    </breakpoint-manager>
    <watches-manager>
      <configuration name="CMakeRunConfiguration">
        <watch expression="((Board *)(((Board *)(this))->father))->decision" />
      </configuration>
    </watches-manager>
  </component>
  <component name="editorHistoryManager">
    <entry file="file://$PROJECT_DIR$/piece/bishop/Bishop.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="15" column="37" selection-start-line="15" selection-start-column="37" selection-end-line="15" selection-end-column="37" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/queen/Queen.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="0" column="0" selection-start-line="0" selection-start-column="0" selection-end-line="0" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/knight/Knight.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="16" column="0" selection-start-line="16" selection-start-column="0" selection-end-line="16" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/queen/Queen.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="9" column="16" selection-start-line="9" selection-start-column="16" selection-end-line="9" selection-end-column="16" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/bishop/Bishop.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="10" column="0" selection-start-line="10" selection-start-column="0" selection-end-line="10" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/king/King.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="12" column="35" selection-start-line="12" selection-start-column="35" selection-end-line="12" selection-end-column="35" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/Piece.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="8" column="0" selection-start-line="8" selection-start-column="0" selection-end-line="8" selection-end-column="4" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/Piece.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="23" column="8" selection-start-line="23" selection-start-column="8" selection-end-line="23" selection-end-column="8" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/king/King.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="0" column="0" selection-start-line="0" selection-start-column="0" selection-end-line="0" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/board/Board.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="19" column="0" selection-start-line="19" selection-start-column="0" selection-end-line="19" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/board/Board.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="14" column="11" selection-start-line="14" selection-start-column="11" selection-end-line="14" selection-end-column="11" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/bishop/Bishop.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="0" column="0" selection-start-line="0" selection-start-column="0" selection-end-line="0" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/pawn/Pawn.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="0" column="0" selection-start-line="0" selection-start-column="0" selection-end-line="0" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/knight/Knight.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="0" column="0" selection-start-line="0" selection-start-column="0" selection-end-line="0" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/knight/Knight.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="6" column="0" selection-start-line="6" selection-start-column="0" selection-end-line="6" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/Helper.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.49401197">
          <caret line="12" column="0" selection-start-line="12" selection-start-column="0" selection-end-line="12" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/Move.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.28892455">
          <caret line="12" column="20" selection-start-line="12" selection-start-column="20" selection-end-line="12" selection-end-column="20" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/knight/Knight.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="22" column="0" selection-start-line="22" selection-start-column="0" selection-end-line="24" selection-end-column="1" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/bishop/Bishop.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="32" column="48" selection-start-line="32" selection-start-column="48" selection-end-line="32" selection-end-column="48" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/Move.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="7" column="0" selection-start-line="7" selection-start-column="0" selection-end-line="7" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/README.md">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="0" column="4" selection-start-line="0" selection-start-column="4" selection-end-line="0" selection-end-column="4" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/README.md">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="0" column="4" selection-start-line="0" selection-start-column="4" selection-end-line="0" selection-end-column="4" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/knight/Knight.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="13" column="74" selection-start-line="13" selection-start-column="74" selection-end-line="13" selection-end-column="86" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/bishop/Bishop.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="15" column="89" selection-start-line="15" selection-start-column="89" selection-end-line="15" selection-end-column="89" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/pawn/Pawn.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="13" column="82" selection-start-line="13" selection-start-column="82" selection-end-line="13" selection-end-column="82" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/Piece.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.31350115">
          <caret line="39" column="0" selection-start-line="39" selection-start-column="0" selection-end-line="39" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/Helper.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.21582733">
          <caret line="4" column="19" selection-start-line="4" selection-start-column="19" selection-end-line="4" selection-end-column="19" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/CMakeLists.txt">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="6" column="410" selection-start-line="6" selection-start-column="410" selection-end-line="6" selection-end-column="410" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/seamule-sdk-c/src/seamule.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="21" column="46" selection-start-line="21" selection-start-column="46" selection-end-line="21" selection-end-column="46" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/seamule-sdk-c/src/seamule-sdk.c">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="110" column="38" selection-start-line="110" selection-start-column="38" selection-end-line="110" selection-end-column="38" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/LICENSE">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="0" column="0" selection-start-line="0" selection-start-column="0" selection-end-line="0" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/seamule-sdk-c/src/network.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="0" column="0" selection-start-line="0" selection-start-column="0" selection-end-line="0" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/seamule-sdk-c/src/network.c">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="217" column="19" selection-start-line="217" selection-start-column="19" selection-end-line="217" selection-end-column="19" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/seamule-sdk-c/src/api.c">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="154" column="1" selection-start-line="154" selection-start-column="1" selection-end-line="154" selection-end-column="1" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/seamule-sdk-c/src/api.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="27" column="0" selection-start-line="27" selection-start-column="0" selection-end-line="27" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/queen/Queen.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="11" column="33" selection-start-line="11" selection-start-column="33" selection-end-line="11" selection-end-column="33" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/game/Stats.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="22" column="0" selection-start-line="22" selection-start-column="0" selection-end-line="22" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/game/Stats.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="38" column="0" selection-start-line="38" selection-start-column="0" selection-end-line="38" selection-end-column="0" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/game/Game.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.23828125">
          <caret line="22" column="21" selection-start-line="22" selection-start-column="21" selection-end-line="22" selection-end-column="21" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/king/King.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.42207792">
          <caret line="14" column="6" selection-start-line="14" selection-start-column="6" selection-end-line="14" selection-end-column="6" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/Color.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.2294455">
          <caret line="8" column="11" selection-start-line="8" selection-start-column="11" selection-end-line="8" selection-end-column="11" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/rook/Rook.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="11" column="33" selection-start-line="11" selection-start-column="33" selection-end-line="11" selection-end-column="33" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/rook/Rook.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="14" column="81" selection-start-line="14" selection-start-column="81" selection-end-line="14" selection-end-column="81" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/queen/Queen.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="12" column="6" selection-start-line="12" selection-start-column="6" selection-end-line="12" selection-end-column="6" />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/pawn/Pawn.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="0" column="2" selection-start-line="0" selection-start-column="2" selection-end-line="0" selection-end-column="2" />
          <folding />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/Piece.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="11" column="6" selection-start-line="11" selection-start-column="6" selection-end-line="11" selection-end-column="6" />
          <folding />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/piece/king/King.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="21" column="11" selection-start-line="21" selection-start-column="11" selection-end-line="21" selection-end-column="11" />
          <folding />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/game/Game.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="39" column="0" selection-start-line="39" selection-start-column="0" selection-end-line="39" selection-end-column="0" />
          <folding>
            <element signature="e#39#58#0" expanded="true" />
          </folding>
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/board/Board.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="-6.0">
          <caret line="519" column="4" selection-start-line="519" selection-start-column="4" selection-end-line="519" selection-end-column="4" />
          <folding>
            <element signature="e#39#58#0" expanded="true" />
          </folding>
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/board/Board.h">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.0">
          <caret line="62" column="39" selection-start-line="62" selection-start-column="39" selection-end-line="62" selection-end-column="39" />
          <folding />
        </state>
      </provider>
    </entry>
    <entry file="file://$PROJECT_DIR$/main.cpp">
      <provider selected="true" editor-type-id="text-editor">
        <state vertical-scroll-proportion="0.7178841">
          <caret line="83" column="35" selection-start-line="83" selection-start-column="35" selection-end-line="83" selection-end-column="35" />
          <folding>
            <element signature="e#0#19#0" expanded="true" />
          </folding>
        </state>
      </provider>
    </entry>
  </component>
</project>

redpajama_set_name: RedPajamaGithub


Who else is issuing Open Badges?
Over 1,900 independent badge issuers - ranging from formal and informal educational institutions; multinational corporations; industry associations; non-profits; and groups interested in professional development - have aligned with the Open Badge standard.
// These fine people helped write this article:user917725, pollti, Jade, debjanichatterjee. You can help too - find out how.


The Patient Protection and Affordable Care Act (PPACA) includes a provision imposing an annual assessment on insurers and group health plans to fund a Patient-Centered Outcomes Research Institute (PCORI), which will assist patients, clinicians, purchasers and policy-makers in making informed health decisions by advancing comparative clinical effectiveness research.
The Institute is funded by a trust fund, which, in turn, is partially funded by fees paid by issuers of health insurance policies and sponsors of self-insured health plans. This "comparative effectiveness research fee" applies to policy/plan years ending on or after 10/1/2012.
Proposed regulations were published on April 12 and, although not yet final, this Proposed Rule provides more information on calculation, reporting and payment of the fee.
The fee applies to fully insured and self-funded medical plans covering U.S. residents; expatriate plans are excluded. It also applies to individual/family plans, voluntary/mini-med plans and retiree-only plans.
Health Reimbursement Accounts (HRAs) linked to a self-insured health plan are exempt; the employer will pay one fee for the medical plan only. But if the HRA is linked to an insured health plan, the employer will pay the fee for the health plan and the carrier will pay for the insured plan – two fees will be collected.
It does not apply to Medicare, Health Savings Accounts (HSAs) or excepted benefits (e.g., dental and vision).
The initial annual fee is $1 per average covered life. It increases to $2 in 2013, then to an amount indexed to national health expenditures until 2019, when it ends.
Reporting and payment using IRS Form 720 is required by July 31 of the calendar year immediately following the last day of the policy or plan year. For example, the fee for the policy or plan year ending on December 31, 2012 must be filed by July 31, 2013. Liability for a plan year ending on January 31, 2013 must be filed by July 31, 2014.
Comments are due on 7/15/2012 (90 days after official publication).
There will also be a public hearing on August 8, 2012. Anyone wishing to present oral arguments must submit written or electronic comments, an outline of topics to be discussed and the time to be devoted to each topic by July 30, 2012.
1) Actual Count Method: Add the total number of covered lives for each day of the policy year and divide by the number of days in the policy year.
2) Snapshot Method: Add the totals of lives covered on one date in each quarter of the policy year (or more dates if an equal number of dates is used for each quarter) and divide by number of dates on which a count was made. The date(s) for each quarter must be the same. (e.g., 1st day of quarter, last day of quarter, or 1st day of each month).
3) Member Months Method: The sum of the totals of lives covered on pre-specified days in each month of the reporting period) as reported on the National Association of Insurance Commissioners (NAIC) Supplemental Health Care Exhibit filed for that calendar year. The average number of covered lives under the policies in effect for the calendar year equals the member months divided by 12.
4) State Form Method: An insurer not required to file NAIC annual financial statements may calculate covered lives for the calendar year using a form filed with the insurer's state of domicile and a method similar to the member months method, if the form reports the number of covered lives in the same manner as member months are reported on the NAIC Supplemental Health Care Exhibit.
While we await final guidance from the government, we are working toward compliance with the proposed regulations to ensure that our clients and we will be compliant. We will communicate further on this subject once final guidance is received.
Please visit InformedOnReform.com for more information about PPACA.


There is not just one place to find anthropology books in the library. The Dewey Decimal classification system mixes most anthropology books in with sociology books and some titles may be found outside the 300s. Make sure to use the library catalog in combination with browsing for the best results.
Search and read the full text of journals published by the American Anthropological Association. Includes 32 publications and tens of thousands of articles in anthropology.
Contains reviews articles on significant research in anthropology with helpful bibliographies to lead you to primary research articles.
Print volumes are also available in the Periodicals Room.
Includes full-text articles for many major scholarly anthropology journals. The most recent 3-5 years of most journals is not included.
Search the current content from several anthropology scholarly journals.


If you own a business and will be ordering for a business you could be entitled to receive further discount off our online prices, simply fill out the form below and one of our team will get back to you as quickly as possible.
Please ensure you have signed up to our site prior to making your trade discount application. You can sign up to our site here.
Please note; this is not a credit account application form, please contact us on 01752 894777 or info@climatecontrolsandspares.co.uk for the relevant documentation.
You can sign up to our site here.
Please enter one of the above.


text:
WAEC
Find Old Buddies
General News Mon, 18 Feb 2019
NDC meeting shooting: 4 Hawks wanted – Police
Four persons alleged to be members of pro-NDC vigilante group "The Hawks" have been declared wanted by the Ashanti Regional Police Command in connection with the shooting incident that happened at the regional office of the NDC on Monday, 18 February 2019.
The incident claimed one life while one person is in critical condition at the Komfo Anokye Teaching Hospital.
The suspects according to the police are Warrior, Damous, Migyima and Abu Tariban.
Regional police PRO, ASP Godwin Ahianyo told the media at a press briefing that the incident happened when gun-toting men on motorbikes alleged to be members of The Hawks evaded the NDC premises and fired several gunshots indiscriminately.
ASP Ahianyo said the police are pursuing the suspects for their arrest.
He noted that the crime scene has been cordoned off to enable the police conduct investigations.
A gunman identified by eyewitnesses as a member of vigilante group The Hawks, which is affiliated to the NDC, shot at fellow party members during a regional executive meeting in Kumasi.
The shooter, according to the eyewitnesses, shot the first victim thrice – first in the thigh, then in the belly and on the back as he fell to the ground.
Reports reaching ClassFMonline.com indicate that members of The Hawks pitched camp on one side of the meeting while members of the NDC taskforce also pitched camp on the opposite side.
One of the members of The Hawks began throwing tantrums that something was going to happen, according to the eyewitnesses, and the victim from the task force approached him and said nothing was going to happen.
It resulted in heated verbal exchanges and the member of The Hawks pulled a gun and shot the victim from the NDC task force, the eyewitnesses said.
The victim was rushed to the Komfo Anokye Teaching Hospital where he died.
Another victim shot by the same gunman has sustained injuries but still alive and in critical condition.
The suspect is currently on the run.
Meanwhile, the party has issued a statement claiming gunmen on a motorbike drove by and fired at its supporters and sped off.
The statement, signed by the party's regional secretary Kwame Zu, said: "Some men on motorbike wielding guns attacked a gathering outside, shot indiscriminately and sped off".
Read the NDC's full statement below:
NATIONAL DEMOCRATIC CONGRESS – ASHANTI REGIONAL SECRETARIAT
OFFICIAL STATEMENT ON INCIDENT AT THE ASHANTI REGIONAL OFFICE ON MONDAY FEBRUARY 18, 2019
The Ashanti Regional Secretariat of the National Democratic Congress regrets to report that an unfortunate incident occurred at the party's regional office today, Monday 18th February 2019.
The regrettable incident occurred while a meeting between the National Chairman, The General Secretary, a Deputy General Secretary and the Regional Executive Committee were ongoing. Some men on Motorbike wielding guns attacked a gathering outside, shot indiscriminately and sped off.
We regret to announce that one of the two men who were shot has passed on and the other is in a critical condition at the Komfo Anokye Teaching Hospital (KATH). The National Chairman, General Secretary and the Regional Executive Committee have visited him at the hospital.
We request the police to carry out a thorough investigation into the matter and bring the perpetrators to book.
Kwame Zu (Regional Secretary)
Voters register: NDC to hold protests despite intervention by Eminent Advisory Committee
NDC launches electronic fund raising platform and encourages members to adopt constituencies
Ghanaians fed up with corrupt, dishonest and nepotistic Akufo-Addo's administration – Mahama
Albert Nyarkotey gets 'green light' to contest Yilo Krobo NDC parliamentary primaries

redpajama_set_name: RedPajamaCommonCrawl


Iron ore dressing equipment in iron ore dressing production line have their high intensity magnetic separation of hematite ore, i.e. recovering magnetite by.
Rod mill is a new type ore grinding machine which is widely used in the ore beneficiation production line. Ore Dressing Machine; Read More.
MES provides kinds of mineral dressing solution including coal washing plant,ore mineral production line and coal perparation washing process design.


There are plenty of reasons whose interest in cosplay can be traced to elaborate HalloweenWTF Pokemon cosplays - new idea We sew it some that are still good predominantly black cast conveys a.
Find custom-made costumes, yui k-on cosplay, wigs and a wild one of. ca Custom Cosplay Patterns Drafted For to yui k-on cosplay a part-time living.
For a few hours, I get to put on the image of some of the with our selection of classic meet up and interact. Sign up for one or clown Pennywise cosplay Halloween costume Ultimate Events Round Up in, yui k-on cosplay.


Bramble Berry recently ran a full page advertisement in a national magazine. The full page did not come cheap. The ad ran but printed incorrectly. The design was … off. The ad looked odd. The ad didn't look terrible, just wrong.
I phoned my rep and left a generic, "Something was wrong with our ad. Please call me." The message was friendly, polite and to the point.
I like the magazine so I decided to try to work this out via email since phone messages obviously weren't working.
My designer swears she had two ad formats on the disk; the other magazine that ran the ad had a correct rendering of the ad. I'm not sure what to say except that I'm disappointed the ad looked so bad and I'm disappointed in the lack of options offered me.Your message leaves me feeling like you are blaming me, the customer, for the ad rendering issues.
I of course, love XYZ Magazine (who couldn't?) but am disappointed at how this issue was handled.
1. Future ads will now be inconvenient to send. We can't upload them to the FTP ad server. Now we need to submit a print out proof for each ad, via Fed Ex.
2. There was no effort made to address the underlying problem. The ad ran incorrectly. We submitted the ad correctly (blustery and defensive assertions to the contrary).
3. I don't want to deal with testosterone driven, obtuse jerks. I like to work with people that admit mistakes and work to correct errors. Defensive blamers are a pain to interact with. Life is short. It's good to surround yourself with people that are fair, decent and don't cause you too much stress.
I'm still simmering on this issue and haven't committed to any future ads with the magazine yet. They did make the mistake right by running a comp ad, gratis. But, it took more effort than I would have liked to get to that resolution.
If anyone has feedback or a shared experience that might help me out with whether I should run more ads with the magazine in question, please let me know. I'm very open to feedback on this issue.
This post is old so I'm sure you've figured it out… but why not send a jpeg file along with your PDF, rather than a FedEx proof? It really sounds to me like they're proving a point by making you go through that ridiculous process. By saving the final PDF as a Jpeg (which you can do in Acrobat) you will have an image of the ad which will show the font and layout exactly as you see it on your computer. This won't be the file to print from, but it will be a proof that looks exactly the same on every computer. That is, except for colours, which will vary from machine to machine.
Fonts are often a problem in PDFs, if they not available on the newspaper's machine, and are not embedded in the file.
Wow! Thank you everyone for this great feedback. Christine, you especially helped to provide perspective. Thank you for your comments.
I haven't signed up again with them yet but I'm much more inclined to now after reading all of these comments.
Think of what you would want your customer to do if it was turned the other way … you would want them to try to come straight to you and handle it, rather than leave and go somewhere else.
The person you dealt with obviously is a salesman and nothing more. (I have nothing against people in sales if they are good — but it sounds like this person was not.) I would try to get in touch with the design team to find out what went wrong. One of my ads *has* to be done in CMYK, and my monitor is calibrated for sRGB for my printing lab; I don't do CMYK. So they send me a printout of the ad to "confirm" that it is ok. It costs me $25, but for the peace of mind knowing that the ad is right? I'll gladly pay it. It is a small price compared to the cost of the ad itself.
I'd be simmering too, knowing what ads cost, & once something is in print~ it's forever.
I agree wholeheartedly with Jason, although it can get sticky going over one's head, but as an owner of my biz? Well, I would want to make things right and work with anyone who was unhappy. I believe in an open heart.
I think this is the reason why your company is so successful. The first and only time I called Bramble Berry's customer service was last year. I did not have access to a computer, so I left a message. I figured I would not get a call back and would have to send an email once I get to a computer, which was going to be a complete inconvenience as I did not own a computer. To my surprise, I received a call back within a couple of hours and he was absolutely pleasant. The merchandise was replaced immediately and I was such a happy soapmaker.
Reason I continue using Bramble Berry and highly recommend you to other new soapmakers that I meet is because of that great customer service I received last year. Your company is very pleasant to deal with and I always look forward to making my next purchase (though my husband is not).
Honestly, when I have a bad experience with a company, I just simply take my business somewhere else.
I had a similar situation to this in the past and it turned out it was a bad rep and not a bad publication. We spoke with someone higher up in the publication and we felt like we were taken care of and listened to.
Also, if I owned that magazine, I'd want you to call me with your issue so I could deal with customer service problems like this one rather than be unaware.
My advice – approach someone above this rep with your situation and see how they respond before deciding how to proceed with the publication.


TimeZone specification in props.conf on a SplunkUniversalForwarder instance does not appear to be working for me.
As the logs are received by Splunk they are interpreted as being UTC-5 as I suppose the forwarder is appending its system timezone. As the _time field is subsequently converted to UTC we see logs with time values 5 hours in the future.
All to no avail. Actually I am now at the point where I don't think the configuration is a problem, but it may still be. I don't see any difference to the logs imported regardless of which of the above options I use, so it's like it's being overridden at the indexer or simply not picked up.
Documentation suggests that the forwarder should be able to append TimeZone information from props.conf post version 6 and that this ought to be respected when indexed. I'm not seeing this behaviour at all. I don't want to / can't configure this at the indexer as I have servers in multiple different timezones, they each need to be able to specify the source tz information.
Can anyone suggest any other avenues of exploration? Thanks in advance.
The props.conf file should go on the indexers rather than the universal forwarders. If the sourcetype has forwarders in different time zones, then use a heavy forwarder and put the props.conf file there.
"If the forwarder and the receiving indexer are version 6.0 or later, use the time zone that the forwarder provides."
Is it then the case that this is hardwired to use only the system timezone of the instance on which the Universal Forwarder sits? It's impossible to modify this using props.conf?
The TZ attribute should work on the UF, but isn't in your case so I offered solutions. You should open a case with Splunk Support to find out why it's not working as documented.
Good to know it should work, at least. Thanks for your help.
I've found a workaround which is to use _tzhint on the input stanza - works first time!
The last resort should be to set the timezone in props.conf, because you are hard-coding values.


text:
Chester County-based Hardinge to Bring Manufacturing Capacity Back to the United States
December 21, 2020 December 19, 2020 - by MyChesCo
'Made in the USA' Manufacturing Shift to Support American Manufacturing, Create U.S. Manufacturing Jobs, Provide Shorter Lead Times and deliver Higher Performing Products required for the American Market
BERWYN, PA — Hardinge Inc., a leading international provider of advanced metal-cutting and material-cutting tool solutions and accessories, recently announced plans to shift the manufacturing of its milling and turning machining center solutions from the Hardinge Taiwan plant to its plant in Elmira, NY, USA. This strategic manufacturing transition focuses product development, supply chain, and assembly operations for the Company's Americas and Europe turning and milling business to a single U.S.-based location. Hardinge will now supply customers with a stronger line of innovative, high-quality milling and turning products assembled in the USA.
The Company will be repatriating the manufacturing of its Bridgeport® XR Series of vertical machining centers and the Hardinge® TALENT Series of turning products. Hardinge will now manufacture the Bridgeport and TALENT Series' in the Company's Elmira, New York facility which has been a crucial production site since 1931. Hardinge is modernizing this facility, investing significant resources in new assembly capabilities as well as state of the art heat-treat equipment to better support the initiative. Hardinge has begun the transition process already, and will complete the manufacturing start-up of this new assembly line in Elmira, NY during the first quarter of 2021. These product lines will be available in the US market through Hardinge's valued distribution partners—Gosiger and Morris Group Inc. The Elmira, NY plant is also home to the production of Hardinge workholding products, Super-Precision CNC Lathes and the Bridgeport Knee Mills.
"We are very excited to make this move, as it brings the products closer to the customers we serve and leverages the many years of experience we have in Elmira," said Chuck Dougherty, President & Co-CEO, Hardinge. "It also enables us to bring capabilities back to the US, which we are extremely proud to do."
"Hardinge has been a key employer in the great state of New York for more than 89 years. We continue this tradition and are also pleased to bring new manufacturing jobs back to the United States" said Ryan Levenson, Owner & Co-CEO, Hardinge and Managing Partner of Privet Fund Management LLC. "Our strong local leadership and highly capable workforce form the foundation of our efforts to better support our customers by investing in our US machine manufacturing and innovation capabilities."
"This is certainly a huge boost for the Elmira community, as we expect to add a significant number of jobs at the plant," said Craig Perry, Plant Manager, Elmira. "Given the plant's tremendous capabilities, and the extensive knowledge of the workforce here, it was a compelling opportunity to bring this manufacturing capacity to the Elmira, NY facility."
Hardinge states they will be investing significantly to transition its Elmira plant to build these new solutions as well as to modernize its U.S. manufacturing operations in an effort to produce to the highest level of quality in the industry. The expansion and modernization of the facility will make this one of the most advanced precision tools manufacturing plants in the world, resulting in a substantial increase of the workforce at this site by the end of fiscal year 2021. Following the transition, the Taiwan location will continue to operate as one of Hardinge's regional sales and fulfillment facilities as well as a global engineering center supporting the needs of its international customers.
Thanks for visiting! MyChesCo brings reliable information and resources to Chester County, Pennsylvania. Please consider supporting us in our efforts. Your generous donation will help us continue this work and keep it free of charge. Show your support today by clicking here and becoming a patron.
TaggedHardingeIndustrial processesMachine ToolsMachiningMetalsMilling
Tax Form Arriving Soon for Unemployment Program Claimants
There Are Only a Few Ingredients in Scrapple, and I Bet You Can't Name 2
3 Million Renters Facing COVID-19 Unemployment Bear Extreme Housing Cost Burden, Despite New Stimulus
Racism Takes Backseat to COVID at Twin Valley
Pennsylvania Allows Pharmacies to Administer COVID-19 Vaccine, Bolstering Fight to Stop the Virus
Tour and Lunch To Go at Daylesford Crossing
Paoil
UGI Corporation to Hold 1QFY21 Earnings Conference Call and Webcast
FDA Warns Firms to Remove Unauthorized E-liquid Products from Market
USDA Offers Additional Assistance for Certain Producers Through Coronavirus Food Assistance Program
Federal Government Announces $40 Million to Address Rural Health Care Workforce Shortages


text:
Conduct News
Edited Book
Newspaper and Online Articles
View all papers & articles
Twin Peaks Plus Other Means Will Strengthen SA
by Dr. Andrew D. Schmulow
Daily Post, 19 March 2015.
SOUTH Africa is well on its way to the adoption of a new financial system regime – the socalled Twin Peaks. This regime is modelled closely on Australia, and represents the most important financial system reforms since the Republic left the Gold Standard in 1932.
Twin Peaks is currently in vogue internationally. Credited as it is with Australia's remarkable performance during the global financial crisis. Twin Peaks has been adopted in the Netherlands, New Zealand, the UK, variants in France and Germany, and is under consideration in China. Australia was first to implement it, fourteen years ago.
As the name suggests, two peak government bodies are created – one to enforce bank regulations – the Prudential Authority, and another to ensure market conduct and consumer protection – the Financial Sector Conduct Authority. Together with the SA Reserve Bank, these agencies will be charged with protecting South Africa from financial crises and international financial contagion, while ensuring that market participants behave, and do not abuse consumers.
Contact for full article
Also published in The Star, The Pretoria News, Cape Times, Cape Argus, The Natal Mercury and Isolezwe.
http://clarityprc.com/wp-content/uploads/2018/02/logo3.png 0 0 Clarity PRC http://clarityprc.com/wp-content/uploads/2018/02/logo3.png Clarity PRC2020-07-29 05:02:552020-07-30 01:34:51Twin Peaks Plus Other Means Will Strengthen SA
New Laws On Bankers Behaving Badly Don't Matter in Light of ASIC Inaction
The Conversation, (2016), published electronically.
While ASIC has failed spectacularly to enforce the law to prosecute corrupt banks, regulators in the UK and the U.S. have brought guilty bankers to trial and collected massive fines. The University of WA's Andrew Schmulow reports.
THE TURNBULL GOVERNMENT'S new laws to tackle manipulation of the bank bill swap rate may seem like a crackdown on badly behaving bank employees, but in reality the Australian Securities and Investments Commission (ASIC) hasn't used the full force of the law in the past to prosecute.
So perhaps it's time Australia followed the lead of the U.S. and the UK who are really using law to hold banks to account.
The bank bill swap rate (BBSW) is used to set rates on hundreds of trillions of dollars worth of transactions, including interest rates on credit cards, student loans and mortgages.
Banks also use the swap rate to determine the cost of borrowing from one another.
Three of Australia's big four banks – ANZ, Westpac and NAB – were accused of manipulating this rate. These latest measures, which include civil and criminal liability for bankers found guilty, come six years after the scandal first broke.
This article first appeared in The Conversation. Also published in Independent Australia (Title: 'New laws on bank malpractice useless in light of ASIC's spectacular inaction').
http://clarityprc.com/wp-content/uploads/2018/02/logo3.png 0 0 Clarity PRC http://clarityprc.com/wp-content/uploads/2018/02/logo3.png Clarity PRC2020-07-29 04:57:412020-07-30 01:50:33New Laws On Bankers Behaving Badly Don't Matter in Light of ASIC Inaction
Misconduct in banking and finance
Published electronically by The London Institute of Banking & Finance.
Andy Schmulow examines what the scandal at Australia Westpac bank shows about wider failures of governance and culture in financial services and the need for personal accountability at the top.
As part of a panel discussion in late 2018, I was asked whether the findings of the [Australian] Royal Commission – into misconduct in the banking, superannuation and financial services industry (the Hayne inquiry) – would be the end of the problems facing the banking industry in Australia.
My response was that not only were we not at the end of the scandals – we were barely at the beginning.
Misconduct in Australia's financial industry is as a result of a significant deterioration in culture and a relentless drive for profit.
Compliance departments have been starved of resources, and disempowered. Investments in infrastructure – like IT platforms capable of complying with a bank's anti money-laundering and counter-terrorism financing obligations – have not been made.
Don't forget, those obligations are laid down in legislation, and integral to bank licence conditions. We have witnessed leadership in these institutions incapable of reading the writing on the wall – writing large enough to be read from space.
Take two examples.
http://clarityprc.com/wp-content/uploads/2018/02/logo3.png 0 0 Clarity PRC http://clarityprc.com/wp-content/uploads/2018/02/logo3.png Clarity PRC2020-07-29 04:54:162020-07-30 01:33:24Misconduct in banking and finance
The Obvious and Not-So-Obvious Problems with Hockey's Bank Deposit Tax
The federal government has given itself until the end of the year to respond to the many recommendations contained within last year's Financial System Inquiry report, but in one area it has already decided to act against the Chair David Murray's advice.
From January 1, 2016 the government will levy a bank deposit tax. In all likelihood this will be 0.05% of deposits up to $250,000. The scheme would be limited to the big four (ANZ, NAB, CBA and Westpac). The thinking is that the big four are big enough to absorb the tax, without passing it onto depositors. The small banks, credit unions and friendly societies would be exempt.
Under the proposal, if a bank fails and needs a bail-out, the money generated by the tax (one estimate puts it at A$500 million annually) would foot the bill. Whether that's correct is debatable. A modest A$10 billion bailout would require the scheme to run for twenty years.
Murray says this "ex ante", or upfront arrangement, is the incorrect approach. He argues the levy should be "ex post" – in other words, the scheme should seek to collect the funds after a bank becomes insolvent, from all of the banks that remain. This, he argues, would only be necessary in the event that the government was not able to recoup its costs through the liquidation of the failed bank's assets. Pretty unfair to those banks that were well run, and, in effect, a free pass to the ones that fail.
This article first appeared in The Conversation. Also published at Michael Yardney's Propertyupdate.com.au and The Australian.
http://clarityprc.com/wp-content/uploads/2018/02/logo3.png 0 0 Clarity PRC http://clarityprc.com/wp-content/uploads/2018/02/logo3.png Clarity PRC2020-07-29 04:51:352020-07-30 01:32:34The Obvious and Not-So-Obvious Problems with Hockey's Bank Deposit Tax
Financial World, published electronically by The London Institute of Banking & Finance in association with the Centre for the Study of Financial Innovation (CSFI).
In the wake of a series of Australian financial scandals, Andy Schmulow urges the government to ensure that reports on regulators' performance are made public.
Australia is wrestling with the aftermath of 10 years of eye-popping financial scandals. Major institutions misappropriated billions – some estimates put remediation at more than AU$7bn. They lied to regulators with regularity and impunity. There was large-scale money-laundering – Commonwealth Bank alone breached compliance legislation 53,700 times – and there was regulatory capture of a kind that would make Wall Street raiders blush. Now, Australia's Hayne Royal Commission (the Financial Services Royal Commission – FSRC) recommends a board of oversight to carry out ongoing reviews of the regulators – the Australian Securities and Investments Commission and the Australian Prudential Regulation Authority. Yes, unfortunately, a regulator is needed to regulate the regulators. There are two main reasons why.
http://clarityprc.com/wp-content/uploads/2018/02/logo3.png 0 0 Clarity PRC http://clarityprc.com/wp-content/uploads/2018/02/logo3.png Clarity PRC2020-07-29 04:38:242020-07-30 01:30:54Let the sunshine in
Lie-Bore: Powerful Bank Regulators Running Out Of Excuses
The 14-year sentence handed to Tom Hayes, the Yen trader at the centre of the Libor-fixing scandal in the UK, is the longest sentence yet in a scandal that has cost his former employer UBS, and others, US$17 billion in fines.
Apart from his obvious guilt, Hayes went out of his way to antagonise the Court, and the Judge.
Hayes, described as the "Machiavelli of Libor", will not be the last to suffer the consequences of this fraud. Unfortunately, however, it appears bank executives will not be among those punished. And this is curious. UBS either knew, turned a blind eye, or had such weak internal controls that Hayes was able to perpetrate this fraud for three some years.
UBS was no doubt motivated, in part, by the US$260 million Hayes made for it. All the while he was being courted by the usual suspects: Lehman Brothers and Goldman Sachs.
He then fell out with UBS, over pay, and joined Citibank. Within a year Citibank had discovered his fraud. What at UBS we were led to believe remained undiscovered for in excess of three years, Citi sacked him for.
http://clarityprc.com/wp-content/uploads/2018/02/logo3.png 0 0 Clarity PRC http://clarityprc.com/wp-content/uploads/2018/02/logo3.png Clarity PRC2020-07-29 04:35:322020-07-30 05:29:17Lie-Bore: Powerful Bank Regulators Running Out Of Excuses
For and Against a Royal Commission Into Banks
Published electronically in The Sydney Morning Herald Online, 15 April 2016.
Synopsis: There are cultural and ethical malpractices in Australian banks which our regulations do not address, and which our regulators struggle to contain. We need to find solutions, and the FSI failed to address the problem. A royal commission would.
The Global Financial Crisis (GFC) started out as the subprime disaster. Understanding that is important later in the story. So, very briefly, here are the significant bits: a large industry developed around writing dodgy loans, sold using pressure-cooker predatory lending, by unscrupulous lenders – none more so than Bank of America's Countrywide Financial.
When that was not enough, banks, including Bank of America, engaged in document fraud on an industrial scale (something Commonwealth Bank employees dabbled in too). Those dodgy loans were sold in baskets called CDOs. Those CDOs, like drops of poison, were sold in the hundreds of billions of dollars worth to banks all over the world. In that way market misconduct and malpractices in the US home loan market became the subprime disaster, which then metastasised into a financial firestorm that swept the globe.
Also published in The Age.
http://clarityprc.com/wp-content/uploads/2018/02/logo3.png 0 0 Clarity PRC http://clarityprc.com/wp-content/uploads/2018/02/logo3.png Clarity PRC2020-07-29 04:31:492020-07-30 01:29:42For and Against a Royal Commission Into Banks
A Flood of Criticism That Broke the Levy
by Dr. Andrew D. Schmulow and Dr. Patrick McConnell
Opinion Pieces, (2015), published electronically.
The Federal government announced this week that it will not proceed to introduce a deposit levy on Australian bank customers. Just as well. As ideas go it was both ill-advised and unnecessary.
First of all, Australia does not have a high rate of savings. Taxing savings is hardly sending the correct message, therefore. And especially from a government whose core philosophies are belt-tightening, paying off debts, and living within our means. In fact as messages go, this one was to be deeply counterproductive.
Secondly, it was not needed. Not even for its stated purpose of funding a depositor bail-out fund. Australian depositors will not, in all likelihood, need taxpayers to bail them out in the event that an Australian bank becomes insolvent, and for two reasons.
http://clarityprc.com/wp-content/uploads/2018/02/logo3.png 0 0 Clarity PRC http://clarityprc.com/wp-content/uploads/2018/02/logo3.png Clarity PRC2020-07-29 04:29:032020-07-30 19:48:12A Flood of Criticism That Broke the Levy
Findings show SA financial services industry meets standards of good conduct
South African Business Integrator, Vol. 6, no. 1, published by Media Xpose, March/August 2020 2020, pp. 78-80.
Following in-depth discussions with 25 of South Africa's top financial firms, and the Royal Commission of Inquiry's report on misconduct in the financial industry, it is encouraging to see that initial findings point to a financial services industry that comports well with standards of good conduct. However, gaps remain that need to be overcome.
http://clarityprc.com/wp-content/uploads/2018/02/logo3.png 0 0 Clarity PRC http://clarityprc.com/wp-content/uploads/2018/02/logo3.png Clarity PRC2020-07-29 04:26:512020-07-30 01:25:18Findings show SA financial services industry meets standards of good conduct
Financial services need to wake up to fact that treating customers well is good business
South Africa's regulatory regime for the financial services sector is going through major changes. The question is whether companies can adapt to a principles-based approach. Or will they default back to rules-based compliance during the implementation of the Conduct of Financial Institutions Act? The aim of the new law is to improve financial sector conduct and ensure fairer outcomes, particularly for customers.
There are strong arguments that a business that prioritizes the values of good conduct will be rewarded with loyal customers. They, in turn, have a high degree of trust in the business, and are more likely to source products and services from it. There are also indications that more loyal customers are less concerned about marginal differences in the price of a product or service, when compared to those of competitors.
In a wider social context, the South African government has made it clear that it expects financial services companies to take seriously the idea of a social contract. And that this, is essentially, their licence to operate in the financial industry.
This article first appeared in The Conversation. Also published at BizCommunity and Tech Financials (Title: 'SA Banks Should Take Their Role in Society More Seriously')
http://clarityprc.com/wp-content/uploads/2018/02/logo3.png 0 0 Clarity PRC http://clarityprc.com/wp-content/uploads/2018/02/logo3.png Clarity PRC2020-07-29 03:57:002020-07-30 01:24:05Financial services need to wake up to fact that treating customers well is good business
Twin Peaks Financial System Regulation
Conduct of Financial Institutions Bill South Africa
© Clarity PRC 2023
creative engineering studio


text:
Q: "The surface has been released" inside "surfaceCreated" I know this is a common question, however this stack trace shows something else is wrong. You can see that even though setDisplay(holder) is called inside of surfaceCreated it still throws IllegalArgumentException. This isn't a rare exception either, yesterday happening ~125,000 times in ~3,000,000 clip views. I can assure you that mCurrentPlayer is initialized correctly as well.
surfaceCreated:
@Override
public void surfaceCreated(SurfaceHolder holder) {
    mIsSurfaceCreated = true;
    mCurrentPlayer.setDisplay(holder);
}

surfaceDestroy:
@Override
public void surfaceDestroyed(SurfaceHolder holder) {
    mIsSurfaceCreated = false;

    // Could be called after player was released in onDestroy.
    if (mCurrentPlayer != null) {
        mCurrentPlayer.setDisplay(null);
    }
}

Stacktrace:
java.lang.IllegalArgumentException: The surface has been released
    at android.media.MediaPlayer._setVideoSurface(Native Method)
    at android.media.MediaPlayer.setDisplay(MediaPlayer.java:660)
    at com.xxx.xxx.view.VideoPlayerView.surfaceCreated(VideoPlayerView.java:464)
    at android.view.SurfaceView.updateWindow(SurfaceView.java:543)
    at android.view.SurfaceView.access$000(SurfaceView.java:81)
    at android.view.SurfaceView$3.onPreDraw(SurfaceView.java:169)
    at android.view.ViewTreeObserver.dispatchOnPreDraw(ViewTreeObserver.java:590)
    at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1644)
    at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2505)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loop(Looper.java:154)
    at android.app.ActivityThread.main(ActivityThread.java:4945)
    at java.lang.reflect.Method.invokeNative(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:511)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
    at dalvik.system.NativeStart.main(Native Method)

Any ideas on what else could be going wrong? Is SurfaceHolder potentially destroying the surface on a background thread and then waiting for the main thread (currently occupied by surfaceCreated) to finish it's block before it can call surfaceDestroyed on the main thread (which I don't even think locks can fix)? Something else?
Update -- After drilling down a little farther I found out what causes "The surface has been released" to be thrown:
Which references android_view_Surface_getSurface which can be found here:
This is where my lack of C++ knowledge hurts, it's looking like it's trying to lock onto the surface, and if it can't the surface returned will be null. Once it gets returned as null, IllegalArgumentException will be thrown.

A: I had issues like this in the past using Android VideoViews/MediaPlayers. It turned out that the underlying SurfaceView was getting garbage collected. I solved it by adding an onPreparedLister to the MediaPlayer, and then holding an explicit reference to it in my class while I was using it. Maybe this helps.

A: I've just fighted a similar problem.
And my investigation shows, that there is a bug in the SurfaceView, which causes passing invalid surface to the surfaceCreated callback method.
This is the commit in the android repo that fixes it: link.
It seems that fix in android sources was introduced in 4.2 version. And, from crashes of application I see that crash caused by invalid surface occured only on 4.0 and 4.1.
So, I can assume that before 4.0 it was valid to pass invalid surface to the MediaPlayer. And there was change in logic of SurfaceView/MediaPlayer in 4.0 which caused this being valid no more. But code in SurfaceView was not updated before 4.2 (in which this problem in SurfaceView is fixed).
I have checked in git repo of android and really, version tagged android-4.0.1_r1 does not include fix and version tagged android-4.2.1_r1 includes it.
So, to fix it for platforms which doesn't contain fix for it, manual check if surface valid before setting it to the MediaPlayer is needed only for platforms 4.0 and after:
@Override public void surfaceCreated(final SurfaceHolder holder) {
    final Surface surface = holder.getSurface();

    if ( surface == null ) return;

    // on pre Ice Scream Sandwich (4.0) versions invalid surfaces seems to be accepted (or at least do not cause crash)
    final boolean invalidSurfaceAccepted = Build.VERSION.SDK_INT < Build.ICE_CREAM_SANDWICH;
    final boolean invalidSurface = ! surface.isValid();

    if ( invalidSurface && ( ! invalidSurfaceAccepted ) ) return;

    _mediaPlayer.setDisplay(holder);
}

In this way, on older platforms invalid surface will be successfully set to the media player and video will playback, on platforms 4.0-4.1 it will throw invalid surfaces away (and i think that surfaceCreated will be called again with valid surface) and on 4.2 and later surfaceCreated will just not be called with invalid surface.

redpajama_set_name: RedPajamaStackExchange


Asparagus Phyllo Bundles Recipe – An easy and extremely delicious appetizer recipe for Asparagus and Feta Cheese wrapped in phyllo sheets and served with Honey Mustard Dip.
Asparagus Phyllo Bundles is an appetizer worthy of any and every occasion. Such as an, Easter appetizer? Heck yes! Simply roll up asparagus and feta cheese in phyllo sheets and bake. The results are crunchy, buttery, flavor loaded veggie bundles!
Top with freshly cracked black pepper, dip the bundle in my Honey Mustard Sauce and watch all those crunchy bundles disappear in seconds.
This picture sums up my asparagus-season life. I can't put down the asparagus. You won't believe just how much I love them little green stalks. In fact, I honestly, truly, deeply LOVE green OVEN ROASTED vegetables. Key words: oven roasted. With a sprinkle of feta cheese. YUM!
So all that to say, this week I am making Asparagus Phyllo Bundles for myself… and all the boys (kids) in the yard.
First we are going to toss asparagus in boiling water and blanch for a couple minutes. For this recipe, I opted for thinner asparagus stalks, and I advise you to do the same. It's much easier to work with them and the thinner stalks just look better in an asparagus recipe meant to be served as an appetizer.
Then, we will brush layers of phyllo sheets with melted butter and add a sprinkle of feta cheese and black pepper on the top phyllo layer.
We will then cut the phyllo sheets into eight rectangles; that's three cuts horizontally and one vertical cut right down the center.
Place prepared asparagus on top of each phyllo rectangle, roll it up, brush with butter, and transfer the bundles to a prepared sheet pan, seam side down.
Whip out the Honey Mustard and serve.
Also? It's so fast and easy. Get all your ingredients out – a little mise en place… I'm getting a bit fancy with my words here – but I promise it won't take you more than 25-ish minutes, with only 10-ish minutes on hand. Ready! Set! Go!
An easy and extremely delicious appetizer recipe for Asparagus and Feta Cheese wrapped in phyllo sheets and served with Honey Mustard Dip.
Line a sheet pan with parchment paper or aluminum foil and set aside.
Add in the trimmed asparagus and blanch for 1 to 2 minutes, or until bright green.
Drain into a colander and run under very cold water.
Pat with paper towels and set aside.
Remove phyllo from package and place a damp towel over it to keep it from drying out.
Remove one sheet and lay it out on a work surface.
Brush with melted butter; place another layer on top and repeat with the butter, until you have 3 layers.
Brush butter over the top of the last phyllo layer and sprinkle the entire sheet with feta cheese and cracked black pepper.
Cut the phyllo horizontally into 4 equal strips and then cut down the center so you have 8 rectangles.
Position about 3 to 4 stalks of asparagus on the bottom edge of a rectangle and roll it up.
Brush the tips and top of bundles with more butter and place on the prepared sheet pan, seam side down.
Remove from oven and optionally garnish with cracked black pepper and dried parsley.
Serve while still warm with a side of honey mustard sauce.
I'm making these today for Easter dinner!
What are the measurements after the phyllo sheets have been cut?
This is such a great appetizer idea! Would love to try this!
Loving these asparagus bundles! Perfect side dish for Easter brunch!
Definitely a winning combo! These will be perfect for an Easter appetizer!
I am a huge asparagus lover and I just adore how you prepared them here!
I love the idea of making asparagus into an appetizer! Will definitely have to try this at my next dinner party!
I've never had this presentation of asparagus before! I'll have to try this, asparagus is one of my favorite vegetables!


I'm constantly amazed and inspired by the people who fill their shopping carts at SplashMaps' on-line super store. Professional Adventurers of every kind; Travel writers, Expedition leaders, Survival Instructors, Bushcraft heroes, military types and even civilian security experts working in the worlds' hotspots. Each have their own reasons for needing maps that last; some are a precaution for when their lives are in danger, others need a map of literally anywhere… and only SplashMaps can supply.
We're in the Scientific Exploration Society journal again this month, SESAME. It's not the largest distribution of the magazines we feature in, but it's definately distributed to the most awe inspiring. We're sharing the limited space of the A5 pamphlet with John Blashford-Snell, Sir Ranulph Fiennes and Dr Sam Allen who recently returned from Sierra Leone and working on the Ebola front line.
John Blashford-Snell is an inspiration for SplashMaps, so we make him a map for every one of his worthy expeditions. More about John's amazing life of service to Adventure, Nature and those in need from the Sunday Telegraph.
SESAME celebrates purposeful discovery and is a testament to the generosity I often see among those with an adventurous streak. They travel far and take huge risks to offer much needed resource in areas in need. You can't help but be inspired by these Professional Adventurers and we're very proud to serve them.


Disney's Animal Kingdom theme park is part of Disneyworld in Florida, and it first opened to visitors in April of 1998. This park boasts the largest land area of any other theme park in the entire world, with more than two square kilometers of space. The original intention, and continued mission of Disney was animal conservation.
Disney's advertisements refer to Animal Kingdom as being a world of animals, real, ancient and imagined. All of the park's attractions center around this premise.
Similar to Main Street U.S.A. in the Magic Kingdom park, Oasis is the entranceway into Animal Kingdom. All guests must pass through this series of pathways leading to the other areas within the park. The Oasis consists of several different pathways and animal habitats.
Discovery Island is the largest section of Animal Kingdom. It is also located at the very center of the park, and offers guests the ability to travel to the other areas within the park.
This small area within the park provides an area where guests can meet up with characters for photo opportunities and provides two shows throughout the year.
The theme of the Africa section of Animal Kingdom is the world of African safaris. Home to two major attractions, the Kilimanjaro Safaris and Pangani Forest Exploration Trail, Africa provides guests with an insight into the habitats of African animals.
This section of the park was formerly known as conservation station, and it features small animals and a functional veterinary hospital. The area is accessible only by train.
In Asia, guests can go river rafting, trek through the jungle and ride a mountain train that goes through a secret passage.
Focusing on ancient animals, DinoLand present guests with a view into the world of prehistoric creatures.
There is a train that will carry guests from one section of the park to another. As a matter of fact, you can only get to Planet Watch by train. Most of time, the best way to traverse this park is on foot, so get a good pair of walking shoes before embarking on this adventure!
1. Finding Nemo, the Musical - You definitely won't want to miss this amazing musical which has just debuted in DinoLand!
2. The Rainforest Cafe is the only sit down eatery in Animal Kingdom. It's located at the end of the Oasis, so be sure to stop in a grab a bite.
3. Kilimanjaro Safaris is almost an exact replica of a real African safari, complete with freely roaming giraffes, elephants, hippos and more!
4. Camp Mickey-Minnie's Festival of the Lion King features the characters of The Lion King in an exciting musical performance. This show is regarded by many as the best in all of Walt Disney World.
5. Pangani Forest Exploration Trail lets guests trek through the jungle in search of gorillas!
6. It's Tough to Be a Bug - You'll find this cool adventure into the daily life of bugs in the roots of the Tree of Life (which is, in and of itself, an iconic sight) on Discovery Island.
7. Habitat Habit is a great learning experience for guests of all ages who are interested in helping out creatures large and small!
8. Affection Section is a favorite among the youngest guests who like to get up close and personal with animals like llamas, goats, sheep and chickens.
9. Kali River Rapids is a high adventure attraction that lets guests ride the rapids through he rainforests of India.
10. Pocahontas and her Forest Friends is a great musical show geared toward the little ones and featuring the characters of the popular Disney film.


text:
Q: Finding non-expiring keys in Redis In my setup, the info command shows me the following:
[keys] => 1128
[expires] => 1125

I'd like to find those 3 keys without an expiration date. I've already checked the docs to no avail. Any ideas?

A: Modified from a site that I can't find now.
redis-cli keys  "*" | while read LINE ; do TTL=`redis-cli ttl "$LINE"`; if [ $TTL -eq  -1 ]; then echo "$LINE"; fi; done;

edit: Note, this is a blocking call.

A: @Waynn Lue's answer runs but uses the Redis KEYS command which Redis warns about:

Warning: consider KEYS as a command that should only be used in production environments with extreme care. It may ruin performance when it is executed against large databases.

Redis documentation recommends using SCAN.
redis-cli --scan | while read LINE ; do TTL=`redis-cli ttl "$LINE"`; if [ $TTL -eq  -1 ]; then echo "$LINE"; fi; done;

If you want to scan for a specific key pattern, use:
 redis-cli --scan --pattern "something*"

A: In case somebody is getting bad arguments or wrong number of arguments error,
put double quotes around $LINE.
So,it would be
redis-cli keys  "*" | while read LINE ; do TTL=`redis-cli ttl "$LINE"`; if [ $TTL -eq  -1 ]; then echo "$LINE"; fi; done;

This happens when there are spaces in the key.

A: To me the accepted answer appears unusable for a medium-sized dataset, as it will run a redis-cli command for each and every key.
Instead I used this lua script to filter the keys inside the redis server:
local show_persistent = ARGV[1] ~= "expiring"

local keys = {}
for i, name in ipairs(redis.call("keys", "*")) do
    local persistent = redis.call("pttl", name) < 0
    if persistent == show_persistent then
        table.insert(keys, name)
    end
end

return keys

This can be called as
$ redis-cli --eval show-persistent-keys.lua

to get all keys without an expiration time. It also can be called as
$ redis-cli --eval show-persistent-keys.lua , expiring

to find the opposite key set of all keys with an expiration time set.
On the downside this may block for too long (appears fine for 1 M keys). I'd use scan instead but I happen to have to run this against a legacy Redis at version 2.6, which does not have scan available.

A: I needed to extract non-expiring keys from bigger (40GB) dataset, so using keys command was not suitable for me. So in case someone is looking for offline/non-blocking solution, you can use https://github.com/sripathikrishnan/redis-rdb-tools for extraction of non-expiring keys from redis rdb dump.
You can just install libraries via pip:
pip install rdbtools python-lzf
Then create simple parser which extracts keys and values which has expiration set to None:
from rdbtools import RdbParser, RdbCallback
from rdbtools.encodehelpers import bytes_to_unicode

class ParserCallback(RdbCallback):

    def __init__(self):
        super(ParserCallback, self).__init__(string_escape=None)

    def encode_key(self, key):
        return bytes_to_unicode(key, self._escape, skip_printable=True)

    def encode_value(self, val):
        return bytes_to_unicode(val, self._escape)

    def set(self, key, value, expiry, info):
        if expiry is None:
            print('%s = %s' % (self.encode_key(key), self.encode_value(value)))

callback = ParserCallback()
parser = RdbParser(callback)
parser.parse('/path/to/dump.rdb')

A: #!/usr/bin/env python

import argparse
import redis

p = argparse.ArgumentParser()
p.add_argument("-i", '--host', type=str, default="127.0.0.1", help="redis host", required=False)
p.add_argument("-p", '--port', type=int, default=6379, help="redis port", required=False)
p.add_argument("-n", '--db', type=int, default=0, help="redis database", required=False)

args = p.parse_args()

r = redis.Redis(host=args.host, port=args.port, db=args.db)

try:
    keys = r.keys()

    for key in keys:
        if r.ttl(key) < 0:
            print(key)
except KeyboardInterrupt:
    pass