Brandon-T

#include <thread>
#include <utility>
#include <cstdint>
#include <string>
#include <sys/types.h>

class Injector
{
public:
    static bool Inject(std::string module_path, std::int32_t pid, void* bootstrap) noexcept;

Brandon-T

function VirtualKeyCodeToMac(AKey: Word): Word;
begin
  case AKey of
    VK_LBUTTON:             Result := $FFFF;
    VK_RBUTTON:             Result := $FFFF;
    VK_CANCEL:              Result := $FFFF;
    VK_MBUTTON:             Result := $FFFF;
    VK_XBUTTON1:            Result := $FFFF;
    VK_XBUTTON2:            Result := $FFFF;
    VK_BACK:                Result := $33;

Brandon-T

import json
import glob
import os
from datetime import datetime
from subprocess import Popen, PIPE

def plist_to_json(filename):
    command = 'security cms -D -i "' + filename + '"'
    cleanup_command = 'sed "s/data/string/g" | sed "s/date/string/g"'

Brandon-T

Hacking UIView animation blocks for fun and profit

In this article, I'm going to explore a way that we can create views that implement custom Core Animation property animations in a natural way.

As we know, layers in iOS come in two flavours: Backing layers and hosted layers. The only difference between them is that the view acts as the layer delegate for its backing layer, but not for any hosted sublayers.

In order to implement the UIView transactional animation blocks, UIView disables all animations by default and then re-enables them individually as required. It does this using the actionForLayer:forKey: method.

Somewhat strangely, UIView doesn't enable animations for every property that CALayer does by default. A notable example is the layer.contents property, which is animatable by default for a hosted layer, but cannot be animated using a UIView animation block.