When the segment is selected, it sets the label color to .background.

This is fine for the default colors, but my tint is a shade of blue. I'd prefer that when the segment is selected, the text color is white, but in night mode the text will be black.

Something may have changed in how the underlying UISegmentedControl works but I am now having the following problem/

If you start with MultiSelectSegmentedControl outlet in interface builder all the initial UISegment frame.origin.x are all zero, so initSortedSegmentsArray doesn't do much - just results in the same order as the subviews were added.

But if you now add an extra segment programatically it will get a non-zero frame.origin.x and now sortedSegments is no longer in sync with the subview order.

The segments will display as expected but when you try and setSelectedSegmentIndexes: with index 0 visually this will result in the second segment being selected.

Description of the problem: When Archiving my project I am getting these errors. I am not using SwiftUI.

/MultiSelectSegmentedControl/Sources/MultiSegmentPicker.swift Cannot find type 'UIViewRepresentable' in scope Unknown attribute 'Binding' Cannot find type 'Binding' in scope Cannot find '_selectedSegmentIndexes' in scope Cannot find type 'UIViewRepresentableContext' in scope

Description: I am trying to have the MultiSegmentPicker extend the width of the screen. Before I tried to implement this in SwiftUI, I was able to achieve this:

by embedding the control inside a view, and then, after viewDidAppear, setting the frame of the control to the size of the view which it was inside.

I am now migrating my app to SwiftUI and trying to achieve similar behavior. I am not as knowledgable in it, and am having some difficulty. The code I am using is:

struct GradePickSegmentedControl: View {
    let items: [String]
    @Binding var indexSet: IndexSet
    var body: some View {
        MultiSegmentPicker(
            selectedSegmentIndexes: $indexSet,
            items: items
        )
        .background(Color.red)
        .fixedSize(horizontal: false, vertical: true)
    }
}

which is producing:

From what I understand about SwiftUI, the parent view gives the available size to the child, but ultimately the child decides how large it will be. It thus seems that it is up to the control to expand each cell to take up the full width of the screen. But I am unsure how to do this.

Any help would be appreciated.

I am using this multi-select segmented control using Interface Builder and not SwiftUI, and everything runs smoothly. However, when I go to archive the project to publish in the App Store, it seems to give compiler errors in the MultiSegmentPicker.swift file, although this code should not run since I am not using SwiftUI. Is there a way to get around this issue?

Description of the problem: When using the cocoapods default entry. The base version offered is 1.2.1 which fails the tests etc.

Minimal project that reproduces the problem (so I'll be able to figure out how to fix it):

• Create a new app.
• Git init the project.
• pod 'MultiSelectSegmentedControl' in the Podfile
• pod install
• check the version is 1.2.1 not the most current which should. e the default behavior.

I want to put a bar at the top of the screen, like the demo. The non-swiftui version works perfectly, but the SwiftUI version has a lot of space below the actual bar:

How do I shrink the blue area down to the height of the control?

Minimal project that reproduces the problem (so I'll be able to figure out how to fix it): I have opened a question on StackOverflow with more details.

StackOverflow

Description of the problem: Hello, I've started seeing some crash reports in my app with the latest version of this control. The issue seems to be limited to iOS 12.2, 12.3, & 12.4; this does not occur on iOS 13. When I run a simulator using a pod of the latest version I get the following errors immediately on load:

dyld: lazy symbol binding failed: can't resolve symbol _$s7SwiftUI7BindingVMa in /Users/.../Library/Developer/CoreSimulator/Devices/7E3DD44E-.../data/Containers/Bundle/Application/72E31CE6-.../MyApp.app/Frameworks/MultiSelectSegmentedControl.framework/MultiSelectSegmentedControl because dependent dylib #1 could not be loaded

dyld: can't resolve symbol _$s7SwiftUI7BindingVMa in /Users/.../Library/Developer/CoreSimulator/Devices/7E3DD44E-.../data/Containers/Bundle/Application/72E31CE6.../MyApp.app/Frameworks/MultiSelectSegmentedControl.framework/MultiSelectSegmentedControl because dependent dylib #1 could not be loaded

The crash log shows "type metadata accessor for Binding + 52" as the break point.

Minimal project that reproduces the problem (so I'll be able to figure out how to fix it): Tested with iOS Simulator using iPhone 8 on iOS 12.4

Hello, I just recently ran a pod update from 1.2.1 to 2.0.1. For whatever reason, Interface Builder is not recognizing the class anymore. It refuses to be set. So while the project compiles (after updating headers to -Swift.h, updating a couple of API calls), interface builder falls back to creating a UISegmentedControl and then the properties (like selected indexes) fail as unrecognized selectors.

iOS 13 release is right around the corner. Any help? Something I'm doing wrong in the transition from obj C to swift?

Description of the problem: This module has been very helpful for me and my project, but starting with Xcode 13.3, I began receiving many reports from iOS 14 users stating that my app had begun crashing immediately at startup, and this module has been identified as the culprit. More specifically, the issue is in the SweeterSwift dependency which this package relies on.

My colleague forked the SweeterSwift package to devise a workaround here: https://github.com/zabolotiny/SweeterSwift

Similarly, I can see another fork of this dependency has been created by another user ( @Janek-CL ) that claims to fix the issue in a different way: https://github.com/CONVELOP-GbR/SweeterSwift

(Issue cross-posted in the SweeterSwift module as https://github.com/yonat/SweeterSwift/issues/7 )

For UISegmentedControl's you are able to use .apportionsSegmentWidthsByContent = true, this will automatically decrease the text size so everything fits in the UISegmentedControl's width.

When using a MultiSelectSegmentedControl and using .apportionsSegmentWidthsByContent = true it will cut off elements since the test size is not decreasing to fit.

Example of what it should do:

What it currently does:

When using SPM and a barebones project I get auto layout warnings.
When I set uiView.translatesAutoresizingMaskIntoConstraints to false in MultiSegmentPicker.init() the project runs fine without warnings or errors. But if I debug the ViewHierarchy there is a warning due to ambiguous contraints. I have opened a question on StackOverflow regarding this issue in which I documented the process and provided screen shots.

StackOverflow Issue

If I get any useful response from anyone there, I will post it here.