Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG REPORT]: your issue #18

Closed
dazzler2 opened this issue Apr 6, 2021 · 1 comment
Closed

[BUG REPORT]: your issue #18

dazzler2 opened this issue Apr 6, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@dazzler2
Copy link

dazzler2 commented Apr 6, 2021

I used your example file and entered the command:
esplot paygrade, by(male) event(to_male_mgr) window(-20 30) estimate_reference

I got the following message:
(note: named style 143 188 187 % 80 not found in class color, default attributes used)
(note: named style 143 188 187 % 80 not found in class color, default attributes used)
(note: named style 208 135 112 % 80 not found in class color, default attributes used)
(note: named style 208 135 112 % 80 not found in class color, default attributes used)

I think this refers to the colors that are supposed to be used for the confidence intervals. The confidence intervals in my plot come out the same color and difficult to distinguish from one another (see screenshot). I am using Stata 14, so it's possible there's an incompatibility? Let me know if that's the issue or if there's something else going on.

image

@dazzler2 dazzler2 added the bug Something isn't working label Apr 6, 2021
@dballaelliott
Copy link
Owner

Hi there,

I'm fairly confident that this is because the confidence intervals are set to be slightly transparent (that is what the %80 controls). I think support for transparency was added in Stata 15. Since this does not appear to be governed by the version command, it's hard for me to replicate this bug. But, I think I found a workaround.

I'm going to try patching this by removing the transparency automatically for users with Statas earlier than 15; I'm running the test suite tonight, but I'll try to push this fix to the main branch in the morning (assuming no issues).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants