Solution

To hide the annoying, unnecessary, pixel eating right panel in Acrobat Reader DC:

1. Close the Acrobat Reader DC
2. Go to: C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroApp\ENU
3. Create a folder named “Disabled” inside the folder.
4. Move Viewer.aapp into that folder..

If you are not interested in my rant you can close your browser tab right now.. 🙂

My Rant

I’ve been using Foxit Reader for a long time. It has been “OK” until printing pages started to take infinite.. It has tabbed GUI, however you have to select one between tabbing vs open in new window. If you want to drag a tab out of the stack, it would not allow you to do so.. It only rearranges the tabs.. Weird but I’ll live..

I am really confused why the software developers are really blind to what is obvious.. I see this pattern in every software.. Developers are eager to play with new features but they are really bad at fixing bugs, removing knots, cleaning weeds..

Last week, with the reinstall of Foxit Reader, printing a few pages took infinitely long.. I am not sure the new version or some last versions have this “feature”, because I haven’t been printing PDFs for a long time to feel as if I am not a part of the crime of killing trees..

I suspected of my old Wifi connection. My Wifi settings tells me the connection is at 300Mb however I have been only seeing 1MB/s with LinkSys e900.. It’s funny that my internet connection is much faster than this gimmick access point’less.. I connected my gigabit ethernet and tried reprinting, no, it was not the connection..

I tried Adobe Acrobat Reader DC and its printing speed was acceptable even with my 300Mb on screen, 8Mb at most e900 connection..

In the past Acrobat Reader was too slow. Its name “acrobat” would be like a child’s answer to the question: What will you be when you grow up. Adobe would be acrobat some day.. :))

I don’t know if we started to have SSD’s, gigabytes of memory, fast CPU’s as a standard, but this time Acrobat Reader was not that much slow at all.  As usual, no software gives you what you want without giving you some stupid annoyance. With Acrobat this was the side bar:

You may hide side bar by clicking the separator between the document and the bar, however if you open another document it comes back.. There is no option to hide it, kill it, trash it permanently.. Each time user opens a new document, it resurrects and says “hello, not this time”.. User have to click the separator to hide it again. What a waste of precious space and time! This time, space and time is connected though…

I run into this every where, sites with unnecessary stationary banners, annoying big buttons. The most successful waster company could be Google. Try Google App’s or whatever name it has now. You would see top of the screen is eaten by the app to show you the buttons/information you never use.. Do software developers use #@!@#!!234234 number of 27″ 4K monitors? If I were the manager of those companies, I’ll force them using 1280×800 resolution MacBook Pro for a day in a week to make the developers feel why every pixel and any user convenience is important..

Developer! Be respectful to our pixels, clicks, time and patience.

I’ve been working on different brands of MCU for over 20 years and have to reinvent how to use UART, I2C, SPI hardware again and again. 8 years ago I said “enough reinventing” and started to write my own set of libraries that I would port on any MCU I would use..  It evolved from very simple, cooperative tasker, simple drivers to premptive operating system, synchronization primitives to complex drivers. Name and naming conventions also have been changing while the libraries evolve. Nowadays I call it Art. It may even change until I ship it.

When I first started Art, my first aim was to create a simple HAL layer.  On any MCU, developer uses UART, SPI, GPIO, timers most of the time.. If I define what an UART is and write the components that suits the definition, that’s it, I could reuse what I wrote for project A in project B. And that worked really well..

However, that task wasn’t that easy. The different needs for different uses contradict each other.. For instance, serial port uses rx and tx buffer; Modbus uses single buffer to hold received and transmitted as Modbus is unidirectional at a time.. One can use two buffers but that will use unnecessary RAM.

With GPIO pins, you can drive a led, or you can wait for a change on the pin. You can connect many SPI slaves to SPI port, and also that SPI might be slave of other SPI master. The same applies to I2C.

The abstraction of the port should allow those configurations, also there should be a naming convention. With the evolution of the Art, my final design is the following:

1. Each HAL implementation class has Port suffix: UartPort, SpiPort, I2cPort, PinPort. This is platform specific. Art should supply its implementation as UartPort* uart0(); UartPort* uart1(); SpiPort* spi0(); I2cPort* i2c0(); etc..
2. Each actual implementation uses the ports as property: Uart port has setUartPort(UartPort*) and UartPort* uartPort(). Similarly SpiMaster, SpiSlave has setSpiPort(SpiPort*) and SpiPort* spiPort() etc.. I2C has similar pattern. This implementation is portable. There is no need to rewrite.
3. The classes given in 2, are the actual implementations that one should use.

That way, with two level of abstraction, the platform specific implementation becomes very minimal. The HAL component of xxxPort only does very specific job. For instance SpiPort::write(void* buffer, Word length) writes given length of Spi Words to the hardware port. If the length is short enough it uses registers directly. If the data is longer than certain amount it uses DMA. If the hardware has FIFO, it pushes the data into FIFO and if all the data is pushed into the FIFO it does not block the CPU as the hardware may continue the job by itself.. All the management code is moved into SpiMaster.

SpiSlave is a little different story. If you code it blocking, the complation of the execution depens on the behaviour of the master. That will effect all the other codes in the MCU as execution of them will be deferred. To overcome this one can use a dedicated Thread however, that will use resources and also requires synchronization which will add unnecessary complexity to the project.

My approach is using asynchronous writes and reads. That way the you gave the data to SpiSlave and tell it which function to call when the job is done. The thread may handle other jobs at mean time.. Although I talked about asynchronous reads and writes for SpiSlave it shares the same methods with SpiMaster. You can do the same in that class as well but as the control belongs to master and Spi is fast, you usually do not need asynchronicity..

A few sample use case would be the following:

Gpio

Make pin 0 of port A output and clear the pin for STM32F series:

pa0()->configure(PinFunctionOutput0);

Similary, one may hold a pointer to pin and use it:

PinPort* led = pa0();
led->configure(PinFunctionOutput0);
led->toggle();

But there is a better way, with Pin class using PinPort as a port:

Pin led;
led.configure(pa1(), PinFunctionOutput);
led = 1;
led = 0;

This leads to being able to seperate definition and usage:

Pin led(pa1());

int main()
{
  led.configure(PinFunctionOutput0);
  led = 0;
  led = 1;
  led.toggle();
}

Spi

SpiMaster spiMaster;
spiMaster.setPort(ssp0());
spiMaster.setSelectPin(p1_0);
spiMaster.open();

spiMaster.start();
spiMaster.writeRead(dataA, dataB, 8);
spiMaster.stop();

Edge Detection

This code calls handlePinEvent when pin 0 of port 2 of LPC series changes from 0 to 1:

EdgeDetector edgeDetector;
edgeDetector.onEvent().connect(handlePinEvent);
edgeDetector.setPin(p2_0());
edgeDetector.setEdge(EdgeRising);
edgeDetector.start();

The EdgeDetector class is the most easy one to describe why 2 level HAL is beneficial. If all the abstraction is implemented in the PinPort class, we had to put necessary data into it. That means two pointers (one for callback list, one for thread pointer) into every PinPort instance. If one uses 30 pins in a 32 bit environment that means 240 bytes on that platform are wasted just for unused callback pointer and thread pointer. With two level abstraction only those pointers are used in EdgeDetector class..

Thread pointer on the EdgeDetector or similar class is used to denote in which thread the callbacks are run.. With this design, PinPort class uses 0 RAM. Literally.. The tip: The content of it is stored in ROM. p2_0() returns a pointer to ROM..