Jeremy Kolb

| Field | Description | |--------------|-------------| | Plugin | `gruvbox` | | Nixpkgs | `unstable` | | Home Manager | `unstable` | - [X] I have read the [FAQ](https://nix-community.github.io/nixvim/user-guide/faq.html) and...

Add ability to optionally replace AlertDialog.Builder with android.support.v7.app.AlertDialog.Builder

6

For material design goodness!

How to get coordinate system of shapefile?

1

I am reading in a shape file using to test my code: ```csharp var reader = new ShapeDataReader(path); var bounds = reader.ShapefileBounds; foreach (var thing in reader.ReadByMBRFilter(bounds)) { var attrs...

ros-env fails to evaluate: empy_3 no longer exists

1

https://github.com/lopsided98/nix-ros-overlay/blob/1b9585ae8f529b2b392203f2dda6fb96311621a9/distros/distro-overlay.nix#L9 is causing me some trouble. I get a `error: attribute 'empy_3' missing`

rqt-{robot,common}-plugins is pulling in multiple python-qt-binding packages and failing to build

3

I threw the following under `examples/` and did a `nix-build ./ros-blah.nix`: ```nix { pkgs ? import ../. {} }: with pkgs; with rosPackages.noetic; mkShell { nativeBuildInputs = [ (buildEnv {...

This worked previously but on 7310520 ```console [jkolb@nixos:~/nix-ros-overlay]$ nix build .#noetic.multisense-lib error: builder for '/nix/store/xry9njchs4fkhjicpjx3dmrj1vrxn1xi-ros-noetic-multisense-lib-4.0.5-r1.drv' failed with exit code 1; last 10 log lines: > shrinking /nix/store/nacb31ajwghcklsaykl8ydsbhq58b6i7-ros-noetic-multisense-lib-4.0.5-r1/lib/multisense_lib/LidarCalUtility > shrinking /nix/store/nacb31ajwghcklsaykl8ydsbhq58b6i7-ros-noetic-multisense-lib-4.0.5-r1/lib/multisense_lib/SaveImageUtility...

When assigning adapters should we set the original adapter's ItemSource to null

1

@martijn00 @Cheesebaron We have a number of classes where we can set an `Adapter` and there is an inconsistency between whether or not the previous adapter is 'cleared' or not....

Support deprecated `Fragment.OnAttach(Activity)` in favor of `Fragment.OnAttach(Context)`. This is also true for native fragments where the latest call was added in API 23. We should probably follow suit.

4.2 is the latest and it seems to have a lot of issues that the original 3.0.8 doesn't seem to have.

Fragments seem to hold onto an extra _dataContext

2

All of our fragments do the following: ```csharp public IMvxBindingContext BindingContext { get; set; } private object _dataContext; public object DataContext { get { return _dataContext; } set { _dataContext...