I think it would help productivity and reduce stress if there were little graphics that kind of sauntered up when doing things that are presently met with invisibility.
For instance when you copy something, you hit Ctrl-C that's fine, most people know that it works and are somewhat comfortable, but your brain could construct the idea that you hit the wrong key that causes an invisible quasi-imperceptible amount of stress. That stress could be removed making the editor much more enjoyable to work with by adding a graphic.
For example, a cutesy little graphic that appears to the right hand side of the editor border, a gradient trail of smaller versions of it self (. .o 0 O 0 o .) while swerving back and forth before disappearing off the edge of the editor (with a label - for example Copy). Something like hello-kitty meets ICQ would probably be pleasant, yet if you could make it a skin style that could be changed that would probably be ideal.
This behavior should probably be capable of being turned off in the settings, yet would probably make a decent default.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1739
Am 13. Januar 2018 02:22:20 MEZ schrieb elextr <notifications(a)github.com>:
>@kugel- is this still valid or has it been overtaken by other changes?
>
>--
>You are receiving this because you were mentioned.
>Reply to this email directly or view it on GitHub:
>https://github.com/geany/geany/pull/183#issuecomment-357398226
Should be still valid.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/183#issuecomment-357418254
Returning large aggregates as values is a potential performance problem, but preventing all aggregate returns is inappropriate because:
1. returning small aggregates that are mostly handled as complete objects as return values often makes code clearer.
2. Modern (well not so modern actually) ABIs allow for small aggregates to be returned in registers, so forcing all returns to memory is actually likely to be slower.
3. if code review does not notice a large aggregate return and nobody notices a performance issue then it doesn't matter
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1740
-- Commit Summary --
* Remove requirement to fail build on aggregate return
-- File Changes --
M .travis.yml (2)
-- Patch Links --
https://github.com/geany/geany/pull/1740.patchhttps://github.com/geany/geany/pull/1740.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/1740
Closing, this probably needs to be re-cast as an extension to #1649 after its merged.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/191#issuecomment-357399547
@kugel- is this still valid or has it been overtaken by other changes?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/183#issuecomment-357398226
Closed since nobody cared enough to comment in 4 years, can always be reopened if needed.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/170#issuecomment-357398120