|
Well, you don't know which MQOTD you would get  .
|
|
|
|
|
I can guess! 
And I suspect ovine interactions would be involved...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
OriginalGriff wrote: And I suspect ovine interactions would be involved...
You know what to do to get an answer to that ultimate question :p
|
|
|
|
|
As bribery attempts go...
...I wouldn't try to get out of speeding tickets, if I was you.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
No further comment, really. Been farting around with some xaml for most of the day just to get a few controls lined up, and still not succeeded.
Now my machine blew up (ran out of memory) presumably because VS2010 is crap too.
Oh for a lawn mowing job!
|
|
|
|
|
_Maxxx_ wrote: Oh for a lawn mowing job!
MBRC are advertising for those at the moment...
|
|
|
|
|
Hand code it (don't use the designer, it makes messy xaml) and get familiar with the different layout containers (Grid, StackPanel, etc) as well as how margin and padding work. Initially it's a pain, but I wouldn't want to go back to winforms.
|
|
|
|
|
Jacquers wrote: Hand code it (don't use the designer, it makes messy xaml)
I am hand coding it = not because the designer makes messy CAML buyt because the designer doesn't handle complex Xaml at all, crashing, freezing and not displaying things anything like they will look at runtime.
(I know that this is get-aroundable by having design-time VMs which I would love to do, but I'm stuck in a system that doesn't and have to live with existing screeds of Xaml cobbled together by 15 developers over several years.
Jacquers wrote: get familiar with the different layout containers (Grid, StackPanel, etc) as well as how margin and padding work.
Margin and padding are the least of my problems.I'm reasonably fine with simple xaml, but when there are user controls within user controls in grids in panels in grids in viewboxes in ... well, you get the picture..,
|
|
|
|
|
Kaxaml[^] is great for playing around with layouts.
|
|
|
|
|
I had a brief moment of hope, then. Then I downloaded it, opened some Xaml I've been playing with for the last 7 hours, and it failed to open with an error on line 1...
|
|
|
|
|
So, which one you like more?
- WPF/XAM?
- WinForm?
- HTML?
Just asking.. 
|
|
|
|
|
Win32 GDI. DrawFrameControl and CreateCompatibleBitmap works every time.
|
|
|
|
|
HO yes, I forgot to ask about MFC, ATL and... Win32!!
And Direct2D! 
|
|
|
|
|
Don't forget COM and ActiveX
Microsoft ... the only place where VARIANT_TRUE != true
|
|
|
|
|
I sense irony, but I could get things done in these technologies quite fast.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
|
|
|
|
|
OK, well, with WinForm the designer works, out of the box.
With HTML there are many many designers that work pretty well, but it can sure get complex especially with complex CSS - but I've only worked on complex stuff that I have written myself.
WPF/Xaml - if it is initially well thought out and well designed I'm sure it's fine. Unfortunately it's generally not.
|
|
|
|
|
it's just beginner bad luck! 
(because, in WPF, if you so wish, you can use the exact same layout option as WinForm!)
tip of the day (free!): read about Panel and layout.
And learn how to use all 5 of the out of the box panel, it will save you countless hours!!
And please, don't get me started on HTML!!! grrr... I hate it much less than before, but it's because no one recently complained about some unexpected pixel misalignment... 
|
|
|
|
|
Super Lloyd wrote: And please, don't get me started on HTML!!! grrr... I hate it much less than before, but it's because no one recently complained about some unexpected pixel misalignment...
*cough* shim.gif to the rescue 
|
|
|
|
|
In cases like this, I recommend using Snoop to see what your Visual Tree looks like. You can use this to find out what's borking the layouts.
|
|
|
|
|
Oh, believe me, Snoop is my constant companion.
The problem is once a certain complexity is reached, it's really hard to see what the problem is.
In this case, for example, I have a simple grid with two rows. The bottom row contains a viewbox and the top may contain one of two or three different controls depending on various bound properties.
Simple, no?
The problem was that the top row would sometimes expand to cover the entire form, fixing that cause d the bottom row to shrink the viewbox to pinhead size.
After hours, I asked the other guys to look at it.
At the end of the day, one of them fixed it for now by hard-coding sizes to make sure it runs at 1024x768 and ust looks crap at higher resolutions.
As that is the resolution it is going to be used at initially that will do for now - but something like 10 man hours to try to do a screen layout is madness.
|
|
|
|
|
|
All your bases are belong to DOS!
It was broke, so I fixed it.
|
|
|
|
|
Heh - clever 
|
|
|
|
|
News so good that it's posted twice in the insider news already.
|
|
|
|
|
Its like a childhood fantacy come true
Not that fare from the truth for me at least 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
