stuffy-doll

Added this to the modprobe.d configs:

options iwlmvm power_scheme=1 options iwlwifi power_save=0

Find game’s App ID number (for example, you can get it from Steam’s game page URL)

Each Proton-enabled game you install will have a copy of wine prefix for it. It should be located at steam-install-dir/steam/steamapps/compatdata/pfx. For example, in my case for Darksiders Genesis, the prefix path was ~/.steam/steam/steamapps/compatdata/710920/pfx. Get a hold of that path.

Clone the unofficial mfplat repository: https://github.com/z0z0z/mf-install.

Export the WINEPREFIX environment var with the path obtained at step 2, then run the mf-install.sh:

export WINEPREFIX=/path/to/game/pfx ./mf-install.sh

Profit.

For anyone who had ever struggled with converting videos to compact quality GIFs, here's a oneliner that does this:

ffmpeg -i <INPUT> -vf "fps=10,scale=<OUTPUT-WIDTH>:-1:flags=lanczos" -c:v pam -f image2pipe - | convert -delay 10 - -layers optimize <OUTPUT>

Prerequisites: ffmpeg and ImageMagick. For convenience I'd recommend adding it as an alias to your .bashrc:

# Video to GIF. Params: # 1) Original video file. # 2) Output GIF file name. # 3) Output image width. Height will be scaled proportinally keeping the aspect ratio. function gifify { local INPUT=$1 local OUTPUT=$2 local WIDTH="" if ! [ "$3" == "" ]; then WIDTH=",scale=$3:-1:flags=lanczos" fi `ffmpeg -i $INPUT -vf "fps=10$WIDTH" -c:v pam -f image2pipe - | convert -delay 10 - -layers optimize $OUTPUT` }

Voila:

/network add -nick yournickname Twitch /server add -network Twitch irc.twitch.tv 6667 oauth:yourtoken /connect Twitch

Main ones:

Array (NSArray)

Set (NSSet)

Dictionary (NSDictionary)

Mutable variants:

NSMutableArray

NSMutableSet

NSMutableDictionary

Other variants:

IndexSet (NSIndexSet)

OrderedSet

Obscure ones:

NSCache

NSHashTable (A collection similar to a set, but with broader range of available memory semantics.)

NSMapTable (A collection similar to a dictionary, but with a broader range of available memory semantics.)

NSPointerArray

Things that also conform to collections:

Repeated: a collection repeating a single element

EmptyCollection, CollectionOfOne

StrideTo, StrideThrough

ArraySlice, Substring

Data (no, seriosly, it conforms to Collection protocol)

a lot more...

See:

https://developer.apple.com/documentation/swift/collection

https://developer.apple.com/documentation/swift/swift_standard_library/collections

https://docs.swift.org/swift-book/LanguageGuide/CollectionTypes.html

https://github.com/cjwirth/awesome-ios-ui

Problem:

You have a big app with CoreData store, NSFetchedResultsController's, huge networking layer & some background updates. Everything should work smoothly: data updates should be independent of each other, your table views should always show latest data available, etc.

How to organize your CoreData stack properly to avoid any kind of lagging and filesystem access errors?

Solution:

Create a master context:

- (NSManagedObjectContext*)masterObjectContext { if (_masterObjectContext != nil) { return _masterObjectContext; } _masterObjectContext = [[NSManagedObjectContext alloc] initWithConcurrencyType:NSPrivateQueueConcurrencyType]; [_masterObjectContext setPersistentStoreCoordinator:self.persistentStoreCoordinator]; return _masterObjectContext; }

Note the private concurrency type here. This will allow it to do all the disk I/O operations in background, without blocking the UI for a millisecond.

Then create a main context for the UI thread, and attach it to the master context as a child:

- (NSManagedObjectContext*)mainObjectContext{ if (_mainObjectContext != nil) { return _mainObjectContext; } _mainObjectContext = [[NSManagedObjectContext alloc] initWithConcurrencyType:NSMainQueueConcurrencyType]; [_mainObjectContext setParentContext:[self masterObjectContext]]; return _mainObjectContext; }

This one is the entry point for all your table views with fetch controllers. This one will always keep the UI up to date without any additional work from your side. To hell all those notifications & merges. Everything that is saved to the main context becomes automatically visible.

Then create your worker contexts with private queues and attach them to the main context:

- (NSManagedObjectContext*)privateObjectContext { NSManagedObjectContext* objectContext = [[NSManagedObjectContext alloc] initWithConcurrencyType:NSPrivateQueueConcurrencyType]; [objectContext setParentContext:[self mainObjectContext]]; return objectContext; }

Those are the things that you do your background updates with. You download all the data (in background, of course), then you push all the data to your private context and call it a day:

[privateContext performBlock: ^{ NSError* error = nil; [privateContext save:&error]; if (error) { DDLogError(@"Error while propagating changes to parent context: %@", error.localizedDescription); } }];

Now the data is kind of saved, but not yet propagated to the main context. How to get it there? Just save the main context:

[privateContext performBlock: ^{ NSError* error = nil; [privateContext save:&error]; if (error) { DDLogError(@"Error while propagating changes to parent context: %@", error.localizedDescription); } else { NSManagedObjectContext* mainContext = privateContext.parentContext; [mainContext performBlock: ^{ // Push changes to a parent context, it it exists. NSError* error = nil; [mainContext save:&error]; if (error) { DDLogError(@"Error while propagating changes to parent context: %@", error.localizedDescription); } }]; } }];

Simple, right? So finally, how to get data to the store? You guessed right - just save the master context. Nice and easy.

If you don't want to do this manually, you can set up a single listener in your CoreData stack manager and do this on every notification:

So, I've recently tried to switch to Genymotion as main emulator for Android projects & stumbled upon a very annoying bug:

03-30 03:21:10.787: E/AndroidRuntime(2637): java.lang.IllegalArgumentException: eglChooseConfig failed EGL_NOT_INITIALIZED

The point is that ADB fails to run a project on an emulator, complaining about some EGL libraries not initializing properly. I assume this is due to the fact that Genymotion emulators try to use host GPU for graphics acceleration and fail to do so in some random cases. (My guess is probably because VirtualBox is still not good at it. Or not every GPU/driver support OpenGLES-2.0)

So, if you are tired of weird Eclipse key bindings that make you swear every time you hit Home or End buttons while editing code, do this:

Open Eclipse Preferences

Go to General->Keys

Find "Line Start", delete everything from the Binding field and press Home button while you are there

Find "Line End", delete everything from the Binding field and press End button while you are there

Optionally you can also change "Select <>" bindings

Hit Apply

If you are working under Linux, you could encounter a problem when some devices doesn't show up in Eclipse's device selection box when you run your Android project, or show up as undefined devices with "????" instead of their names/properties. In this case you should try the following...

1. Download the latest google-chrome deb package from official site. Let's put it into some temp folder, like "~/tmp/"

2. Download the package build script. You can get one for Slackware here:

http://slackbuilds.org/mirror/slackware/slackware-14.0/extra/google-chrome/

and for the Zenwalk here:

http://distro.ibiblio.org/zenwalk/source/extra/xap/google-chrome/

Put them in the same folder with the deb package.

3. Go to your temp folder and run google-chrome.SlackBuild / build-google-chrome.sh.

# ./build-google-chrome.sh

If everything goes well, you should get an *.txz package ready for installation. It should run OK on clean system. I've ran it on out-of-box fresh Zenwalk & Slackware installations without any problems.

Slackware package /root/tmp/google-chrome-5.0.375.86-i486-66.2.txz created.

4. Installpkg google-chrome-*.txz. It should install Chrome in /usr/lib/google-chrome. Try to run it by executing

/usr/lib/google-chrome/google-chrome

If you get some errors about missing SUID sandbox, try this: