These are chat archives for AvaloniaUI/Avalonia

30th
Nov 2018
MonkAlex
@MonkAlex
Nov 30 2018 05:28

Double click on it makes file dialog enter said directory

what about keyboard navigation, if directory selection disabled?

Nikita Tsukanov
@kekekeks
Nov 30 2018 05:28
Keyboard focus and selection are different things
Keyboard-focused file item
Keyboard-focused directory item
MonkAlex
@MonkAlex
Nov 30 2018 05:30
not intuitive for me ~_~
Nikita Tsukanov
@kekekeks
Nov 30 2018 05:33
It's even less intuitive if you can multiselect directories along with the files
MonkAlex
@MonkAlex
Nov 30 2018 05:33
How its work in winform? Directories can be selected?
Nikita Tsukanov
@kekekeks
Nov 30 2018 05:33
For example, GtkFileChooser's OK button does nothing if you have a directory in your multiselection
No idea, I'm replacing Linux file dialogs, not Windows ones
ahopper
@ahopper
Nov 30 2018 07:03
@kekekeks if your scrollintoview issue is when it scrolls down and puts the item second to last in the displayed items, I think it is ItemVirtualizerSimple allowing for the last item not completely fitting the viewport.
Nikita Tsukanov
@kekekeks
Nov 30 2018 07:05
I'm scrolling to the 40th item in the list of ~300 items
ListBox gets scrolled to the 41th item
40th item isn't visible
ahopper
@ahopper
Nov 30 2018 07:05
with the 41st at the bottom?
Nikita Tsukanov
@kekekeks
Nov 30 2018 07:05
At the top
To scroll to 40th item I have to ScrollIntoView 39th
ahopper
@ahopper
Nov 30 2018 07:06
that's bad :)
Nikita Tsukanov
@kekekeks
Nov 30 2018 07:06
Then 40th item is placed correctly at the top of the area
Steven Kirk
@grokys
Nov 30 2018 07:07
that's definitely an off-by-one error somewhere!
ahopper
@ahopper
Nov 30 2018 07:13
is this a virtualized list
ahopper
@ahopper
Nov 30 2018 08:32
I can't recreate this with either virtualized or non virtualized lists. For me, depending on the inital start point, the correct item is displayed at the top or the bottom (or second to bottom).
Nikita Tsukanov
@kekekeks
Nov 30 2018 09:28
@DmitryZhelnin @wieslawsoltes FYI: NumericUpDownPage from control catalog doesn't work with Wine
Nikita Tsukanov
@kekekeks
Nov 30 2018 09:46
Complains about en-US culture or something
Benedikt Stebner
@Gillibald
Nov 30 2018 14:59
Somehow AvaloniaResources isn't updated when I add a resource(asset).
Using the resm scheme works and lists the added asset
But avares doesn't show the added one
Nikita Tsukanov
@kekekeks
Nov 30 2018 15:34
Are you using Visual Studio?
Does it actually build the project?
Nikita Tsukanov
@kekekeks
Nov 30 2018 15:39
Also check if you are using the latest master
Benedikt Stebner
@Gillibald
Nov 30 2018 15:53
Just merged the latest but recheck
I use Visual Studio
Benedikt Stebner
@Gillibald
Nov 30 2018 16:08
I just add this to Assets/Fonts and make sure the build type is embedded resource
AssemblyDescriptor.Resources does have the resource(asset) but AvaloniaResources doesn't.
Btw @danwalmsley the font Looks okay with skia
ahopper
@ahopper
Nov 30 2018 16:14
Something for the x-platform 3d widget w3c/strategy#153
danwalmsley
@danwalmsley
Nov 30 2018 17:24
@Gillibald interesting, in avalonstudio it wouldn't show
did you implement the using nearest font face?
Benedikt Stebner
@Gillibald
Nov 30 2018 17:28
Just tested the font to check if that was the issue. Haven't started implementing the fallback.
WPF seems to search parent namescopes for bindings in DataTemplates it seems?
"namescopes, how the fuck do they work?" as the insane clown posse said in a meme in the late 2000s
ahopper
@ahopper
Nov 30 2018 22:37
the name thing starts to loose meaning when dataTemplates are defined at a distance from their use
Steven Kirk
@grokys
Nov 30 2018 22:37
it seems to be that parent namescopes are searched if they're defined in the same XAML file
ahopper
@ahopper
Nov 30 2018 22:38
that sort of seems ok to me
Steven Kirk
@grokys
Nov 30 2018 22:38
yeah, the question is how the fuck to implement that behavior
especially because we try to be XAML-independent
ahopper
@ahopper
Nov 30 2018 22:42
just thinking out loud but adding some sort of namespace prefix would not offend me
Steven Kirk
@grokys
Nov 30 2018 22:42
i know we're already not handling namescopes properly: AvaloniaUI/Avalonia#1100
namespace prefix?
ahopper
@ahopper
Nov 30 2018 22:43
well currently within a dataTemplate # can't see beyond the template
but what is beyond the template could be anything in any file
and stuff in remote files does not make much sense(to me right now)
so one step towards a solution might be to describe the limited scope with an extension to the # syntax
Steven Kirk
@grokys
Nov 30 2018 22:49
i think i may have had a similar idea, but to check: what sort of extension were you thinking?
ahopper
@ahopper
Nov 30 2018 22:50
not got that far, it is friday night.
Steven Kirk
@grokys
Nov 30 2018 22:52
haha ok ;)
i do have a beer sitting next to me. which is probably advisable when trying to work this stuff out
ahopper
@ahopper
Nov 30 2018 22:54
yep, it appears wpf rather hides the truth, being more explicit makes sense to me.
can you chain binding paths?
$parent[ListBox]#something
Steven Kirk
@grokys
Nov 30 2018 22:59
not currently, no. but that might be a good idea
i mean, WPF's behavior makes a lot of sense in an intuitive way
it's quite user-friendly (rare for WPF ;) )
ahopper
@ahopper
Nov 30 2018 23:00
yep, in a file once you have names you will want to do it
Steven Kirk
@grokys
Nov 30 2018 23:02
the #name syntax is already actually defined in the XAML assembly, as is ElementName
so we could probably do this...
first i think i'll have to fix #1100 though
ahopper
@ahopper
Nov 30 2018 23:15
since I first found the issue it has not been a big problem for me in honesty but @toytonics issue made me realize I was not doing any 'cross tree' binding, but I can see a use for it.