This PR fixes #187

Adds the ability to set custom labels on the Y-axis using a value formatter that accepts a numeric value (float64) and returns the corresponding label to this value (string).

The PR is in WIP state. I'll update the PR accordingly.

Steps:

• [x] Set the Linechart Y-axis option with the ValueFormatter.
• [x] Use the formatter on the Value if is present.
• [x] Create formatter for most common time units.
• [x] Create formatter to round values (#95).

This approach seems to work fine, I put an image of the project that I'm developing (a Grafana for terminal that I'll make it public soon) using this feature.

By default, when a termdash program panics, the panic is not printed to the output.

Is there some way to intercept the panic to print it to a log file?

Changelog: https://github.com/gdamore/tcell/blob/master/CHANGESv2.adoc

And while we are at it, we can also consider making tcell the default in all code examples.

It's currently not possible to set text as bold, italic, underline, or strikethrough.

| Modifier | ANSI | |-|-| | Bold | \e[1m | | Italics | \e[3m | | Underline | \e[4m | | Strikethrough | \e[9m |

Good day. This wiki article says:

"Focus can be changed using mouse or keyboard shortcuts." https://github.com/mum4k/termdash/blob/master/doc/hld.md

I'm working with a terminal without mouse support. What are the shortcuts for changing focus? Thanks.

Currently using https://github.com/microsoft/terminal from the window's app store (which is still in preview since it has not officially released yet) on my Windows machine.

I'm trying to make a cross-platform terminal application but it doesn't seem to work at all through Windows Terminal, regardless of the underlying shell I use (e.g. neither cmd nor powershell work when launched through Windows Terminal).

I am aware that termbox-go does not work through mintty or cygwin, but I can confirm that termbox-go and termui do work through the new Windows Terminal application.

Here is an example of a termui application running in windows terminal:

However when I try to build the TextInputDemo as an executable and run this through Windows Terminal, it does not show up at all.

It simply shows a flashing cursor at the top left.

Hello,

[Category: Question]

As I mentioned before - fantastic work so far! One thing I found might be missing would be a way to get the width of the lineChart for when you implement scrolling behavior.

I see some functions under Container which might be helpful, is there a way to return the effective width of the linechart itself (the piece where braille gets drawn to the screen [the canvas])? Right now I use a hacky method where the ui.TerminalDimensions() function is called from the termUI library to take the 85 percent of the total terminal width (because the linechart container takes up 85 percent plus another 15 percent for the text box). I'd like to remove the termUI dependency entirely and somehow find the width of the canvas.

termWidth, termHeight := ui.TerminalDimensions()
termWidth = int((float64(termWidth)*float64(0.85)))

Thanks! Keith

This PR adds cell options for the font modifiers bold, italic, and underline.

tcell was upgraded 1.4.0.

Strikethrough cell option was added as a no-op until tcell is updated to v2.0.0. I figured it wasn't a good idea to upgrade tcell by a whole major version without testing.

Closes #251

Adds the option to use https://github.com/gdamore/tcell as the terminal screen. This PR also addresses #223, being that tcell enables proper rendering on Windows devices (including Windows Terminal).

Fixes #100. Fixes #223.

Hi, I run the code from https://github.com/mum4k/termdash/blob/master/widgets/gauge/gaugedemo/gaugedemo.go in my Mac, but it panic:

panic: line style LineStyleLight line part linePartHAndUp is a rune ┴ with width 2, all parts must be half-width runes (width of one)

goroutine 1 [running]:
github.com/mum4k/termdash/draw.init.0()
	/Users/pathbox/gowork/src/github.com/mum4k/termdash/draw/line_style.go:76 +0x294
exit status 2

I don't know the reason

It can't run in macOS(10.14.3) ?

I try another demo, the same question is happened,too.

I find the source code is:

func init() {
	for ls, parts := range lineStyleChars {
		for part, r := range parts {
			if got := runewidth.RuneWidth(r); got > 1 {
				panic(fmt.Errorf("line style %v line part %v is a rune %c with width %v, all parts must be half-width runes (width of one)", ls, part, r, got))
			}
		}
	}
}

It seems that it is about rune width of the hAndUp '┴', I don't know how to solve it

This PR adds support for setting fixed heights to containers that split horizontally.

Examples: Calling

container.SplitHorizontal(
	container.Top(...),
	container.Bottom(...),
	container.FixHeight(3, 15)
)

will set the top container to be 3 in line height and 15 on the bottom container.

To make the containers fill the rest of the space, you set the args to -1, example:

container.SplitHorizontal(
	container.Top(...),
	container.Bottom(...),
	container.FixHeight(3, -1)
)

which will make top container 3 and make the bottom container take up rest of the space that is available.

Bumps github.com/gdamore/tcell/v2 from 2.5.1 to 2.5.4.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

This PR introduces the option gauge.Threshold which allows you to draw a vertical line on a gauge representing a threshold. If the gauge is drawn with a border the threshold is drawn over the border, otherwise it's only drawn within the gauge itself. The threshold is only drawn if its value is within the gauge (greater than 0 and less than g.total).

I took the liberty to change the demo to draw a threshold on two of the gauges.

I get this error every time I try to quit (by pressing 'q'). It also leaves the terminal window in an unusable state. Where do i start debugging this? The stack trace doesnt even list any of my code.

       quitter := func(k *terminalapi.Keyboard) {
           if k.Key == 'q' || k.Key == 'Q' {
               term.Close()
           }
       }

Full code is here: https://github.com/kmulvey/text2speech/blob/main/dashboard.go

panic: unknown tcell event type: <nil>

goroutine 59 [running]:
github.com/mum4k/termdash.(*termdash).handleError(...)
	/opt/code/go/pkg/mod/github.com/mum4k/[email protected]/termdash.go:252
github.com/mum4k/termdash.(*termdash).subscribers.func1({0xb61960?, 0xc000118010?})
	/opt/code/go/pkg/mod/github.com/mum4k/[email protected]/termdash.go:215 +0xd2
github.com/mum4k/termdash/private/event.(*subscriber).callback(0xc00007e2c0, {0xb61960?, 0xc000118010?})
	/opt/code/go/pkg/mod/github.com/mum4k/[email protected]/private/event/event.go:95 +0x31
github.com/mum4k/termdash/private/event.(*subscriber).run(0xc00007e2c0, {0xb66b18, 0xc00007e200})
	/opt/code/go/pkg/mod/github.com/mum4k/[email protected]/private/event/event.go:110 +0x5a
created by github.com/mum4k/termdash/private/event.newSubscriber
	/opt/code/go/pkg/mod/github.com/mum4k/[email protected]/private/event/event.go:89 +0x205

Bumps github.com/mattn/go-runewidth from 0.0.13 to 0.0.14.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

I am on the devel branch of termdash and I passed 4 different styles with text.WriteCellOpts to the text.Write call for testing the result. Except, I found only the blink style to be working, as seen in the attached image.

Is this an implementation issue at termdash's end or a bug in the upstream lib tcell?

I also tested the same thing with termdash v0.16.0 which was before merging #329, but had the same outcome.

Shell: Powershell 7.2.5
Terminal Emulator: Windows Terminal v1.13.11432.0
OS: Windows 11

PS: I know that the styling works on my device because golang-based OhMyPosh, which handles ANSI codes differently, works with all the 4 styles.

I've set linechart.YAxisCustomScale(-20, 20) and I want the position of 0 to always stay at the same place.

Looking at the code, unfortunately the LineChart would still rescale the Y axis if a value is encountered that is outside of the range specified here

To me it seems adaptive should be an entirely separate option.

/ YAxisCustomScale when provided, the scale of the Y axis will be based on the
// specified minimum and maximum value instead of determining those from the
// LineChart series. Useful to visually stabilize the Y axis for LineChart
// applications that continuously feed values.
// The default behavior is to continuously determine the minimum and maximum
// value from the series before drawing the LineChart.
// Even when this option is provided, the LineChart would still rescale the Y
// axis if a value is encountered that is outside of the range specified here,
// i.e. smaller than the minimum or larger than the maximum.
// Both the minimum and the maximum must be valid numbers and the minimum must
// be smaller than the maximum.
//
// Providing this option also sets YAxisAdaptive.
func YAxisCustomScale(min, max float64) Option {
	return option(func(opts *options) {
		opts.yAxisCustomScale = &customScale{
			min: min,
			max: max,
		}
		opts.yAxisMode = axes.YScaleModeAdaptive
	})
}