Protocol described in the official PDF mention CRC byte that complete each request and replay. But omit algorithm for it calculation.
After some researches, something sounds like true was found:
#include <iostream>
#include <cstdlib>
#!/usr/bin/env bash | |
# TODO: check me | |
#QTC_EXE=${QTC_EXE:-qtcreator-master} | |
QTC_PTREE_DEBUG=${QTC_PTREE_DEBUG:-no} | |
get_ppid() | |
{ | |
local pid=$1 | |
ps -o ppid= -p $pid |
// Based on: https://stackoverflow.com/a/76915043/1828241 | |
// 1. Open Spread Sheet | |
// 2. Go Menu → Extensions → App Scripts | |
// 3. Create new script, rename it to JsonData.gs | |
// 4. Put this code, save | |
// 5. Return back to Spread Sheet, entry formula as usial: `=JsonData(A1; "field_name")` | |
// For compres JSON and nested fields script must be adjusted | |
function JsonData(jsonText, key) { | |
try { | |
var data = JSON.parse(jsonText); |
// [SerialSend.c] | |
// Эта программа посылает текст или файл через последовательный порт | |
// Автор Ted Burke, последнее обновление 8-4-2015 | |
// | |
// Обновление: | |
// 2024-06-07: Alexander Drozdoff <[email protected]>: | |
// - Добавлено отправка данных из файла as-is | |
// - Добавлен режим /read_back для вычитывания после | |
// отправки данных из порта. Полезно для синхронных | |
// устройство которые отсылают эхо, но которые блокируются |
#include <opencv2/opencv.hpp> | |
#include <opencv2/core/ocl.hpp> | |
void opencv_opencl_dump() | |
{ | |
std::vector<cv::ocl::PlatformInfo> platform_info; | |
cv::ocl::getPlatfomsInfo(platform_info); | |
std::cout << "OpenCL infos: " << platform_info.size() << '\n'; | |
for (auto &&item : platform_info) { | |
std::cout << " - Name: " << item.name() << '\n' |
Protocol described in the official PDF mention CRC byte that complete each request and replay. But omit algorithm for it calculation.
After some researches, something sounds like true was found:
#include <iostream>
#include <cstdlib>
Y = a * R + b * G + c * B
Cb = (B - Y) / d
Cr = (R - Y) / e
BT.601 | BT.709 | BT.2020 | |
---|---|---|---|
a | 0.299 | 0.2126 | 0.2627 |
b | 0.587 | 0.7152 | 0.6780 |
import = ["~/.config/alacritty/alacritty-theme/themes/konsole_linux.toml"] | |
live_config_reload = true | |
[cursor] | |
blink_interval = 500 | |
blink_timeout = 0 | |
thickness = 0.40 | |
[cursor.style] | |
shape = "Underline" |
# /usr/share/libalpm/hooks/99-99-aur.hook | |
# /etc/pacman.d/hooks/99-99-aur.hook | |
[Trigger] | |
Operation = Upgrade | |
Type = Package | |
Target = * | |
[Action] | |
Description = "Check non-repo packages integrity" | |
When = PostTransaction |
@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); | |
.tabbrowser-tab:not([pinned]):not([selected]) { | |
min-width: initial !important; | |
overflow: hidden; | |
} | |
.tabbrowser-tab:not([pinned]) { | |
min-width: initial !important; | |
} |
Not a question, just a life-hack :-)
Changes, that allows showing all project files in project view is discarded. Clarification that Project View is not a Project View but Build System View is added to the documentation. So, now there is no way to propagate CMakeProjectManager2 changes to the upstream at all.
But we can still display all files using stock plugin and existing functionality. Just hack it using fake CMAKE_TOOLCHAIN_FILE
...
Idea:
file(GLOB_RECURSE ...)
scan project tree for files