hello... im trying to add a ContentPresenter to my control to allow the user to overlay their own UserControls
this is my control template with added ContentPresenter...
<Grid Margin="0 0" ColumnDefinitions="Auto, *">
<StackPanel Orientation="Horizontal" Name="marginContainer"/>
<tv:TextView Name="textView" HorizontalAlignment="Stretch" Margin="0, 0" Grid.Column="1"
CaretIndex="{TemplateBinding CaretIndex}"
SelectionStart="{TemplateBinding SelectionStart}"
SelectionEnd="{TemplateBinding SelectionEnd}"
Foreground="{TemplateBinding Foreground}"
TextDocument="{TemplateBinding TextDocument}"/>
<ContentPresenter Content="" />
</Grid>
what do I set the content to and what type do I need to add to my perspex property to allow that to be filled from Xaml?
ok... I think I just need to inherit from content control instead of templated control..
ok that works...
but it intercept my mouse clicks
<Grid Margin="0 0" ColumnDefinitions="Auto, *">
<StackPanel Orientation="Horizontal" Name="marginContainer"/>
<tv:TextView Name="textView" HorizontalAlignment="Stretch" Margin="0, 0" Grid.Column="1"
CaretIndex="{TemplateBinding CaretIndex}"
SelectionStart="{TemplateBinding SelectionStart}"
SelectionEnd="{TemplateBinding SelectionEnd}"
Foreground="{TemplateBinding Foreground}"
TextDocument="{TemplateBinding TextDocument}"/>
<ContentPresenter Content="{TemplateBinding Content}" Grid.Column="1"
Margin="{TemplateBinding Margin}"
HorizontalAlignment="{TemplateBinding HorizontalContentAlignment}"
VerticalAlignment="{TemplateBinding VerticalContentAlignment}"/>
</Grid>
so the red bit is my content presenter... it only covers a small portion of the editor... but editor no longer receives mouse clicks...
i think that's because we don't yet have mouse transparency implemented
I set HorizontalAlignment and VerticalAlignment to Left and Top
and this enables mouse click below and to the right of the red bit
but not above or to the left of it
what would be the effect of IsHitTestVisible?
ah yes
that works
ok cool ;)
IsHitTestVisible = false and clicks just fall through to whatever is behind!!
ended up answering my own question
thanks @grokys
np, i didn't do anything ;)
IsHitTestVisible should work the same as WPF
im wondering how to get my usercontrol to handle keydown events..
code behind is not receiving keypress events...
not sure if my control should have a keydown ICommand property?
then user control binds to an ICommand in viewmodel
ah e.handled was set in control
I wanted to fix bug #324. Now I see that GridSplitter is actually working as HorizontalGridSplitter. I think it's better to create two different: HorizontalGridSplitter and VerticalGridSplitter, because in WPF it's kind of ambiguous. You should set VerticalAlignment or HorizontalAlignment, it defines the behavior. How do you think?
i agree that the API in WPF is horrible, but i'm not sure about two separate controls. wouldn't just an
Orientation property work, the same as with StackPanel?
@susloparovdenis I disagree
The way ti worked to me was pretty neat
Oh I see.
Hmmm Actually @grokys @susloparovdenis I see what you mean now, yeah Orientation would probably be better than gridsplitter could do the rest automagically :D
I've already seperated them. I found several advantages in seperating them, and no disadvantages
- It looks more clearer in xaml
- So it does in implementation
- Styling is different, with different properties. For
HorizontalGridSplitteryou should setHeight, for 'VerticalGridSplitter' 'Width' - Look at those nice dots :)
small lib perhaps useful for someone, https://www.nuget.org/packages/Gu.ChangeTracking/1.0.0
@susloparovdenis If you have to committed somewhere, I would love to play withit.
Gridsplitter is crucial to my docking system, I am not sure if it being seperated would break what I have so far XD
There are prefomance issues yet.
I suggest attached property like
Gird.Pos="2,1,2,3" for Grid.Column="2" Grid.Row="1" Grid.ColumsSpan="2" Grid.RowSpan="3"
hmmm
@susloparovdenis looks pretty neat
I think this will do VERY VERY well :D
@grokys what is our equivalent if UIElement?
that'd be
Control
@susloparovdenis cool!
still not sure about having two separate controls to do the same thing though...
thoughts anyone else?
Well, I don't like that you need to supply two separate styles for them
But we don't have LayoutTransform, so it's kinda inevitable
pool request?
thanks @grokys and last but not least, our equivalent of
FrameworkElement
@grokys I think a single control would be better.... but when I looked at it.. the orientation seemed to be defined by if the splitter was positioned between 2 rows or 2 columns... so perhaps you wouldnt need an orientation? or maybe thats how the wpf one works... which confused me completely!
FrameworkElement = Control again
oh nice thanks so I was just doubting myself a bit XD
i never understood the difference between the two in WPF so there's no distinction
@danwalmsley i can never remember how the WPF one works, it's really confusing
to get a single control can the template not workout what orientation it is and make the horizontal version hidden or the vertical one hidden
effectively wrapping @susloparovdenis solution into a single one?
I know the difference between them :O
either way, Control is the way to go I think, makes it a bit more simple
UIElement basic visual stuff, basic input, measure, arrange, (abstract margin, minwidth, other virtual functions)
FrameworkElement styling, databinding, object tree, object lifetime, margin, mindwidth
FrameworkElement styling, databinding, object tree, object lifetime, margin, mindwidth
@grokys I keep asking questions.... grr anyways, I noticed Window does nto have any static things like Window.GetWindow(), is there another place this is held?
GetWindow?
I'm not sure that it's implemented
things like input, layout etc are implemented in the
InputElement, Layoutable etc classes but you never want to use them by themselves
to get the window for a control, you can use
control.GetSelfAndVisualAncestors().OfType<Window>().First()
Ah okay, and what of DIspatcher?
I thought it would but GetSelf, but I wasn't sur ehow to only get the window so that rocks.
Basically, I tear my dock item, it creates a new window of the same type of the items parent window then from there I need to be able to access the dispatcher
Oh reading hes a lot sorry guys
What is the practice for manipulating items contained within an ItemsControl?
sorry @ImaBrokeDude i have no idea what you are asking
@grokys do you have plans to implement LayoutTransform or for example only a single LayoutTransform control?
not sure about LayoutTransform yet - CSS/html seems to do ok without it
it'd add a load of complexity so I'm not sure would be worth it
a single layout transform control sounds interesting though. what would it involve?
sure I think I can help writing a LayoutTransformControl
not sure only about mouse input, but the initial version can be without proper mouse input handling
are you ok with that?
and completelly agree that LayoutTransform on every control can add unnessesary complexity of the base classes
yeah, sounds good! i'd like to see an implementation
sure in the next days i think it should be ready.
Also are you ok with adding some small new stuff like:
Also are you ok with adding some small new stuff like:
- Expander
- PathGeometry like WPF (inherit Streamgeometry) with objects for Arc, line etc. so these can be defined in xaml
3.ScaleTransform
definitely!
those things are all needed
great I'll start work for these features
@grokys the Items Property is an IEnumerable so I can't do things like Items.Clear() and such
that's the same as in WPF
Guys, if anyone wants to contribute to our Skia backend and for some reason wants to do it on Linux/Mac, we have a spare license for CLion IDE
you will usually bind it to a VM property
if not, cast it to the concrete type and do
Clear() etc on that
also see #54
hmmmmmmm interesting
Actually I like that :O
@grokys using ICollection seems to be a good solution
yeah, the only thing i wasn't sure about was if all common collection classes implement that
i was concerned because
ICollection<T> doesn't implement ICollection: https://msdn.microsoft.com/en-us/library/92t2ye13(v=vs.110).aspx
@grokys @kekekeks is there a way to enumerate all of the available
PerspexPropertys in a PerspexObject?
@grokys @kekekeks I think what @ImaBrokeDude is trying to ask is this...
In his docking control, when a Docked item becomes undocked i.e. floating
like this in VS.
how does he maintain the databinding of the viewmodels and controls that are contained within it...
since it will now be in a seperate window with its own visual and logical trees
?
@danwalmsley i can't see where he asks that? anyway - set the DataContext at the level of the control that will be detached/attached
oh lol and can it tell me if a databinding exist on it or not?
yeah i figured out to just copy the datacontext
I think we should try to port AvalonDock
instead of inventing our own dock implementation
@kekekeks its a huge undertaking I think
could be possible...
avalonedit had lots of stuff that would need to be re-written for a direct port... not sure about avalondock
It's better than writting one from scratch
May be we need some kind of auto-porting tool that will use roslyn to replace references
wow that would be pretty cool
forexample on avalonedit... it was hugely reliant on lots of Windows text rendering and formatting stuff..
And some compatibility classes (marked as internal) to be included to the project
like TextRuns, etc
We don't have that yet
and bits that are just not available on mono
No text document model at all
thats why i just took out the TextDocument part... which is top notch btw
but all the rendering stuff started from scratch
and bits that are just not available on mono
Ehm? Are you still talking about stuff from PresentationCore?
ah man XD
but based on what id learnt from avalon edit.. so it was fairly similar architecture...
well I will still write mine too because it would help me learn Perspex a bit more then :P
but simplified down
you guys do what you want XD
@ImaBrokeDude I think you should keep going... im not sure anyone will have the resources to port avalondock any time soon
@kekekeks im wondering again about hiding window chrome?
any new thoughts on that?
even if it was just windows at first?
That will be easy to implement
Proper client decorations support will take time through
what do you need it for?
floating tool windows
kind of like the beforementioned window
This message was deleted