<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>UX on MXI</title><link>https://mxii.eu.org/categories/ux/</link><description>Recent content in UX on MXI</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 06 Nov 2019 17:00:00 +0300</lastBuildDate><atom:link href="https://mxii.eu.org/categories/ux/index.xml" rel="self" type="application/rss+xml"/><item><title>SDRSharp plugin for touch devices, some thoughts on license</title><link>https://mxii.eu.org/2019/11/06/sdrsharp-plugin-for-touch-devices-some-thoughts-on-license/</link><pubDate>Wed, 06 Nov 2019 17:00:00 +0300</pubDate><guid>https://mxii.eu.org/2019/11/06/sdrsharp-plugin-for-touch-devices-some-thoughts-on-license/</guid><description>&lt;p>This project was sitting on my hard drive for several years until now. Last time I made an attempt to clean it up and prepare for publishing to GitHub in 2017.&lt;/p>
&lt;p>Making sure it compiles against all required targets and contains all the required notes - is easy for such a small project. But there was something I just didn&amp;rsquo;t know how to deal with&amp;hellip; More on this below.&lt;/p>
&lt;p>&lt;img src="https://mxii.eu.org/post/2019-11-04-SdrSharp-plugin-for-touch-devices-and-some-thoughts-on-license/screenshot.png" alt="Frequency Navigation plugin screenshot" />&lt;/p>
&lt;p>Back in time, I was playing with RTL-SDR dongles, and the device I was connecting them to was a Microsoft Surface 2 Pro - &amp;ldquo;laptop-but-more-like-a-tablet&amp;rdquo;. I love Microsoft Surface devices, especially that old one, for it&amp;rsquo;s compact size. It is really cool to be able to move around freely, listening what&amp;rsquo;s coming from a dongle, no awkward balancing acts with a classic laptop&amp;hellip;&lt;/p>
&lt;p>Portable use has some UX specifics. Namely, having to use keyboard and mouse is really limiting, and touch screen operation on a tablet device is much more preferred.&lt;/p>
&lt;p>While SDR# had quite clean UI, it was clearly made without such considerations. The core functionality - frequency navigation - was nearly impossible to perform on the go. It is really hard to hit top or bottom of the right digit on the frequency display.&lt;/p>
&lt;p>At the same time, I had some examples of test and measurement equipment in access. These are historically made with very good tactile operation in mind. So I figured I can bring some of that experience to an SDR# plugin.&lt;/p></description></item><item><title>Next folder, previous folder navigation in Explorer with QTTabBar</title><link>https://mxii.eu.org/2018/12/22/next-folder-previous-folder-navigation-in-explorer-with-qttabbar/</link><pubDate>Sat, 22 Dec 2018 12:15:11 +0300</pubDate><guid>https://mxii.eu.org/2018/12/22/next-folder-previous-folder-navigation-in-explorer-with-qttabbar/</guid><description>&lt;p>&lt;a href="http://qttabbar.wikidot.com/">QTTabBar&lt;/a> surprised us with the update recently, after almost three years of silence. &lt;em>(The &lt;a href="http://qttabbar.wikidot.com/change-log">changelog&lt;/a> also points to an importance of having a full copy of your code somewhere outside of your PC. Version control systems to the rescue.)&lt;/em>&lt;/p>
&lt;p>To celebrate this fact, I decided to publish a little custom feature I&amp;rsquo;m using with QTTabBar &amp;mdash; a script and UI buttons to navigate between folders within one common parent folder.&lt;/p>
&lt;p>There are cases when you need to visit a set of folders, and going up and down in the folder structure is getting tedious. That&amp;rsquo;s where magic &amp;ldquo;Next folder&amp;rdquo;, &amp;ldquo;Previous folder&amp;rdquo; buttons come in handy.&lt;/p>
&lt;div class="sidenote">
&lt;p>Navigation pane, a.k.a. tree view can, in principle, be used for that, but it isn&amp;rsquo;t always convenient to use. I can only use it for top level navigation, unless Microsoft will come up with some way to reduce clutter in the tree - not showing subfolders that aren&amp;rsquo;t ascendants or descendants of current folder for example.&lt;/p>
&lt;/div>
&lt;p>My QTTabBar panel looks like this:&lt;/p>
&lt;p>&lt;img src="https://mxii.eu.org/post/2018-12-22-next-folder-previous-folder-with-qttabbar/qttabbar-panel.png" alt="QTTabBar panel screenshot" />&lt;/p>
&lt;p>Two triangles looking in opposite directions are the buttons this post is dedicated to.&lt;/p>
&lt;p>Below is the code and description for the buttons.&lt;/p></description></item><item><title>JavaScript spoiler with a twist (collapsing up or down)</title><link>https://mxii.eu.org/2017/09/07/javascript-spoiler-with-a-twist-collapsing-up-or-down/</link><pubDate>Thu, 07 Sep 2017 21:28:11 +0300</pubDate><guid>https://mxii.eu.org/2017/09/07/javascript-spoiler-with-a-twist-collapsing-up-or-down/</guid><description>&lt;p>I thought that I will eventually need to use spoilers in this blog to hide long and optional blocks of text. And at the same time I&amp;rsquo;m often unhappy with collapsible block implementations across the Internet.&lt;/p>
&lt;p>So I decided to design my own spoiler with one useful feature: it can be collapsed not only from the top edge but also from the bottom edge &amp;mdash; you will not lose the line you were reading and you don&amp;rsquo;t have to scroll all the way to the beginning of the spoiler.&lt;/p>
&lt;p>Examples:&lt;/p>
&lt;div class="spoiler">
&lt;div class="spoiler-btn spoiler-btn-top">&lt;i class="fa-solid fa-chevron-down">&lt;/i> click to &lt;span class="show">show&lt;/span>&lt;span class="hide">hide&lt;/span>&lt;/div>
&lt;div class="spoiler-body">
&lt;p>This spoiler can be expanded up and down. And your mouse is left right over the button you just pressed whenever it is possible (on top and bottom of a page there may be not enough stuff to keep it so, obviously).&lt;/p>
&lt;p>&lt;img src="https://picsum.photos/410/410?random=1" alt="" />&lt;/p>
&lt;/div>
&lt;div class="spoiler-btn spoiler-btn-bottom">click to &lt;span class="show">show&lt;/span>&lt;span class="hide">hide&lt;/span> &lt;i class="fa-solid fa-chevron-up">&lt;/i>&lt;/div>
&lt;/div>
&lt;div class="spoiler simple">
&lt;div class="spoiler-btn spoiler-btn-top">&lt;i class="fa-solid fa-chevron-down">&lt;/i> click to &lt;span class="show">show&lt;/span>&lt;span class="hide">hide&lt;/span>&lt;/div>
&lt;div class="spoiler-body">
&lt;p>This spoiler can be expanded in one direction only. Collapsing behavior is still the same. The difference is just a few lines in CSS.&lt;/p>
&lt;p>&lt;img src="https://picsum.photos/410/410?random=2" alt="" />&lt;/p>
&lt;/div>
&lt;div class="spoiler-btn spoiler-btn-bottom">click to &lt;span class="show">show&lt;/span>&lt;span class="hide">hide&lt;/span> &lt;i class="fa-solid fa-chevron-up">&lt;/i>&lt;/div>
&lt;/div>
&lt;p>Keep reading to see how it is done.&lt;/p></description></item></channel></rss>