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

Scide/theme mgmt fix #1297

Merged
merged 4 commits into from
Mar 17, 2016

Conversation

vdonnefort
Copy link
Contributor

Hi,

Following our discussion with @miczac (#1150), here's some theme related fixes.

This patch adds missing elements to the list of keys to import when migrating
to the new theme management feature.
Only background color is used for current line. See this previous patch:
    ide: themes: disable unused options display for currentLine
Since the transparent color can't be stored, this patch makes sure that when the
picked brush is Qt::NoBrush (~ color transparent), the foreground is not set. It
fixes the transparent color for foreground.
@vdonnefort vdonnefort mentioned this pull request Feb 2, 2015
Since the theme class is not a Q_OBJECT, there is no need to put it into
ide_moc_hdr. This patch fixes the following warning:
  sc-ide/core/settings/theme.hpp:0: Note: No relevant classes found
@vdonnefort
Copy link
Contributor Author

Hi,

I just added a patch which fixes the warning "theme.hpp:0: Note: No relevant classes found. No output generated."

@miczac
Copy link
Contributor

miczac commented Mar 14, 2015

Hi, would be lovely to have this commits pulled! ;) thanks!

@vdonnefort
Copy link
Contributor Author

@telephon @jleben @muellmusik This PR is needed for 3.7. Can you label it?

@bagong
Copy link
Contributor

bagong commented Mar 24, 2015

Or just merge and let testers find problems? In reality pull requests hardly get tested. This one (well, the one this builds upon) had more testing and discussion than most others. I have been using this a bit, seems to work fine. The one confusing thing I found is that you have to create a new theme, before you can change certain settings, but I guess that's by design? (try e.g. to change background color of "matching brackets" in the default settings - currently a hot issue :) )

@scztt scztt added this to the 3.7 milestone Mar 26, 2015
@scztt
Copy link
Contributor

scztt commented Mar 26, 2015

👍 to merge

@bagong
Copy link
Contributor

bagong commented Mar 26, 2015

Sorry, I found two more issues, one very small, the other one significant, but not necessarily directly related to your PR:

  1. disabling the foreground button for 'current line' seems okay, although a bit normative. But then the color box (and the display example) should actually display the foreground color chosen for default text. That is currently not the case, both box and sample always display black.
  2. the color picker (pipette) doesn't work. If you click it, nothing happens. After you close the preferences dialogue though, the cursor displays as magnifying glass in the editor (this is OS X 10.10.2/Qt5.4.1). Obviously the color picker was waiting for the dialogue to close :)

@vdonnefort
Copy link
Contributor Author

@bagong:

The behavior you're encountering is perfectly normal: the "current line" is not used and so is disabled: vdonnefort@83e8490

@bagong
Copy link
Contributor

bagong commented Mar 26, 2015

Yes, that's not my point.

Any comments on the color picker?

@vdonnefort
Copy link
Contributor Author

@bagong @scztt @miczac Do you agree if instead of disabled foreground options I hide them?

@bagong
Copy link
Contributor

bagong commented Mar 26, 2015

Well, I don't want to be too picky, so let somebody else make a judgement. I'll just say that in that case the text sample to the left will still display black as foreground color, regardless of the actual default Text color, so the user will still be confused. But there certainly are more pressing issues. So from my side up to your own judgement.
Would you please say if the color-picker thing is connected to your contribution? If not, I will file a general issue.

@vdonnefort
Copy link
Contributor Author

@bagong, when I make this contribution I've been asked for disabling these unused options. But the fact that the foreground is not used is not related to this PR.

@bagong
Copy link
Contributor

bagong commented Mar 26, 2015

Let me try to be clearer: There are two issues.

  1. GUI-feedback for the user to see if she likes her choices. She can chose fore- and background for default text, see the colors in the boxes, and see the resulting text-background-combination with a sample in the large selection box. This doesn't work in the case of "Current line" where as foreground color always black is displayed, regardless of the color chosen for default "Text". This could make the user think, the "Current Line" can only display black as foreground color. Try to imagine somebody who has no idea of the implementation.
  2. The color-picker pipette issue: if you click on the color-box for fore- or background, the the system color picker will open. At the left bottom it displays a color box that shows the color you have chosen. To it's right there is a icon resembling a pipette. If you click it, you should be able to pick up a color from the graphical environment. The cursor will change into a magnifying glass to enhance the precision of your color-"pick". This is quite useful, but it doesn't work in the context of the preferences dialog, the functionality is dead. Instead you get the cursor shaped as magnifying glass when you close the preferences dialog. This is a proper and reproducible bug - but it might not be related directly to your pull-request. I am asking for a comment on exactly that question.

I am sorry, I won't be able to comment further on this, have to run...

@bagong
Copy link
Contributor

bagong commented Apr 3, 2015

So I took the time to check in vanilla master: both issues are there as well. I'll file two issues and think this should be merged.

@telephon
Copy link
Member

telephon commented Apr 3, 2015

@bagong So we should merge and then treat these issues separately?

@bagong
Copy link
Contributor

bagong commented Apr 3, 2015

Yes, I've already filed issues.

@crucialfelix crucialfelix modified the milestones: 3.8, 3.7.x Feb 29, 2016
@crucialfelix
Copy link
Member

let's merge now, confirm ?

@vdonnefort
Copy link
Contributor Author

Yes

crucialfelix added a commit that referenced this pull request Mar 17, 2016
@crucialfelix crucialfelix merged commit 04ea7e5 into supercollider:master Mar 17, 2016
@crucialfelix
Copy link
Member

Damn we need some structure around here. Over a year to merge a PR ? I just merged a shit tonne of pull requests.

@vdonnefort
Copy link
Contributor Author

And I'm thankful for that, these are bugfix and should have been merged on time for 3.7.

@crucialfelix
Copy link
Member

There was such an incredible backlog it was hard for me to go through so
many issues and PRs.
3.7 was more about shipping what was already done and merged.
3.8 comes June 1

On Thu, Mar 17, 2016 at 5:34 PM Vincent Donnefort notifications@github.com
wrote:

And I'm thankful for that, these are bugfix and should have been merged on
time for 3.7.


You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#1297 (comment)

https://twitter.com/crucialfelix
https://medium.com/@crucialfelix
http://www.mattermind.com/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants