<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Inputs layout in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-layout/m-p/42070#M7819</link>
    <description>&lt;P&gt;No I'm afraid I ended up working around it.&lt;/P&gt;</description>
    <pubDate>Thu, 11 Apr 2013 13:51:56 GMT</pubDate>
    <dc:creator>dkuk</dc:creator>
    <dc:date>2013-04-11T13:51:56Z</dc:date>
    <item>
      <title>Inputs layout</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-layout/m-p/42068#M7817</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Does anyone know if it's possible to specify a limit on the number of fieldset inputs that a given view displays on the same line. I.e. lets say we have 10 drop downs and want to oraganise them neatly into 5 rows of two (to categorise them). If the default layout is used (simple XML), the input objects will be organised end to end with a wrap to the next line only occurring when horizontal browser window space runs out. This results in a rather messy layout.&lt;/P&gt;

&lt;P&gt;Any suggestions appreciated. &lt;/P&gt;

&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Feb 2013 13:34:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-layout/m-p/42068#M7817</guid>
      <dc:creator>dkuk</dc:creator>
      <dc:date>2013-02-25T13:34:33Z</dc:date>
    </item>
    <item>
      <title>Re: Inputs layout</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-layout/m-p/42069#M7818</link>
      <description>&lt;P&gt;Did you find a solution to this problem? I'm in the same boat.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2013 21:58:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-layout/m-p/42069#M7818</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2013-04-05T21:58:32Z</dc:date>
    </item>
    <item>
      <title>Re: Inputs layout</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-layout/m-p/42070#M7819</link>
      <description>&lt;P&gt;No I'm afraid I ended up working around it.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2013 13:51:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-layout/m-p/42070#M7819</guid>
      <dc:creator>dkuk</dc:creator>
      <dc:date>2013-04-11T13:51:56Z</dc:date>
    </item>
    <item>
      <title>Re: Inputs layout</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Inputs-layout/m-p/42071#M7820</link>
      <description>&lt;P&gt;In case you (or someone else who stumbles across this question) is still interested in a solution, I have found the following:&lt;/P&gt;

&lt;P&gt;The &lt;CODE&gt;.fieldset .input&lt;/CODE&gt; have &lt;CODE&gt;display: inline-block&lt;/CODE&gt;, so if you make each of them &lt;CODE&gt;float: left&lt;/CODE&gt; and every other one &lt;CODE&gt;clear: both&lt;/CODE&gt;, you get exactly what you need:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;.fieldset .input {
    float: left;
}

.fieldset .input:nth-child(odd) {
    clear: both;
}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Another option would be to use jquery and append a break after every other &lt;CODE&gt;field&lt;/CODE&gt; element.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Apr 2015 12:20:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Inputs-layout/m-p/42071#M7820</guid>
      <dc:creator>jeffland</dc:creator>
      <dc:date>2015-04-07T12:20:59Z</dc:date>
    </item>
  </channel>
</rss>

