No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Datable rowHeight doesnt change the Height of the radio button column

    Help
    2
    3
    940
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      peterPanParker last edited by peterPanParker

      Hi
      I have a data table with single select and rowheight of 30px; all the columns except radio button column takes that height, if i change back to 50px it looks well again; i want to know how to fix it, is there any property for radio buttons column height?

      here is my data table config:

      rowHeight: ‘30px’,
      title: ‘Catálogo de Perfiles’,
      noHeader: false,
      refresh: false,
      columnPicker: true,
      leftStickyColumns: 0,
      rightStickyColumns: 0,
      pagination: {
      rowsPerPage: 10,
      options: [5, 10, 15, 30, 50, 500]
      },
      selection: ‘single’,
      bodyStyle: {
      maxHeight: ‘500px’,
      minHeight: ‘300px’
      },
      messages: {
      noData: ‘<i>warning</i> No data available to show.’,
      noDataAfterFiltering: ‘<i>warning</i> No results. Please refine your search terms.’
      },
      labels: {
      columns: ‘Columnas’,
      allCols: ‘Todas las Columnas’,
      rows: ‘Filas’,
      selected: {
      singular: ‘Fila Seleccionada.’,
      plural: ‘Filas Seleccionadas.’
      },
      clear: ‘Limpiar’,
      search: ‘Buscar’,
      all: ‘Todos’
      }

      0_1510258218797_err.png

      1 Reply Last reply Reply Quote 0
      • rstoenescu
        rstoenescu Admin last edited by

        Hi, v0.15 has a revamp of the DataTable. Although I could not reproduce it, this will no longer be an eventual issue in v0.15. Thanks for your patience until the new version comes along. I’m currently working inhuman hours for the new version so investigating what is already obsolete would further slow me down. Sorry for this.

        1 Reply Last reply Reply Quote 1
        • P
          peterPanParker last edited by

          ok, thanks

          1 Reply Last reply Reply Quote 0
          • First post
            Last post