150 reputation
7
bio website
location Szczecin
age
visits member for 1 year, 4 months
seen May 22 at 8:52
stats profile views 4

I'm a C# developer from Szczecin, Poland. Certified as MCTS in Windows applications.


Sep
3
revised Best approach to designing a long multi-level side menu
added 521 characters in body
Sep
3
answered Best approach to designing a long multi-level side menu
Sep
2
awarded  Scholar
Sep
2
accepted Desktop application problem: how to present a new option without confusing existing users
Sep
2
awarded  Critic
Sep
1
comment Desktop application problem: how to present a new option without confusing existing users
I quite like this solution - I think that's definitely the one to go with if we were designing the thing from scratch. One thing that bothers me is whether this new layout doesn't sort of break "backward compatibility"? Is it obvious for user which option was which before they upgraded the app? You're right about the use of red, too; unfortunately that's crude convention used everywhere in the app. Red simply stands for "no", even if there is nothing warning nor alarming about this "no" . For now I'll wait and see if any other answers come up throughout the weekend, thanks for looking into it
Sep
1
comment Desktop application problem: how to present a new option without confusing existing users
@Izkata - well, that's the specification. Removing (ignoring) products is only meant to apply to specific, selected products; no "apply to all" command is available. (It would effectively disable the entire offer). It's obviously debatable, but it's not up to me.
Aug
31
awarded  Student
Aug
31
awarded  Editor
Aug
31
revised Desktop application problem: how to present a new option without confusing existing users
deleted 13 characters in body
Aug
31
asked Desktop application problem: how to present a new option without confusing existing users
Jul
18
awarded  Teacher
Jul
18
answered What should my button read, when user is done reading a text / message
May
13
comment Visualize deceased user on social media?
A grey entry in a member list, for example, might just look like a disabled or banned account. Why not put a thick black rectangular border around their name, as in necrologues in papers or movie credentials?
Apr
25
awarded  Commentator
Apr
25
comment Should “gender” be required, or is there a better way to collect this information?
@TRiG it could be a scrollbar, too.
Apr
19
comment User Interface that adjust itself to the user behaviour
Personally I wish to have tabs on the top even if I'm using only 4 on average. It's just superior. Tabs on the top (or on the edge of the screen) make it easier to switch tabs regardless of how many there are. The browser could make it easy to switch between tabs being put on the top or not and I have no problem about it, I just still wouldn't like it to make that decision for me. It could be annoying like Clipper was. The idea is nice in theory, but execution would be troublesome. Why not just a few reasonable presets (ready-made UI layouts) instead? Much cheaper to implement
Apr
19
answered User Interface that adjust itself to the user behaviour
Apr
18
comment Good reasons to use bad UI
@Izkata it doesn't really say that QWERTY does a better job than Dvorak at alternating hands, unless I'm missing something. It's not the case really, and it's not difficult to measure at all - see patorjk.com/keyboard-layout-analyzer. Eg. to type "Alice's Adventures in Wonderland", you'd have to use the same hand consecutively for 25.3% of characters with QWERTY and 17.0% with Dvorak. When consecutive finger use is taken into account, QWERTY scores nearly 2 times worse than Dvorak (3.8% vs 1.9%) (Miscellaneous tab). Dvorak doesn't seem to be "completely abandoning" this aspect.
Apr
18
comment Good reasons to use bad UI
It may be ugly, it's simplistic, but it doesn't mean it's "bad". It's clear and intuitive.