2010 R2 will include UXCurrencyEditor with sophisticated currency editing experiences, such as value and decimal spinning, automatic format as you type, and more.

You can login to http://dev2.intersoftpt.com to read the complete roadmap.

Thanks,
Jimmy

Chris,

The UXDesktop requires the TaskBar to perform minimize and maximize command because TaskBar is responsible to "perform" the minimize logic and "determines" the largest boundary for a maximized window, this conforms to desktop UI/UX standards.

The good news is the TaskBar property in UXDesktop is defined with ITaskBar interface type, so you can actually implement any kind of task bar user interface as long as you implement the ITaskBar interface. You can learn more about the concept here.

So in your case, yes, you can do whatever you desire for your custom task bar to do when a minimize or maximize command occur. This is done in your implementation of the ITaskBar interface, which has the following signature:

    public interface ITaskBar : IAnimationProvider
    {
        Dock DockPosition { get; set; }
        ISItemsControl Owner { get; set; }

        Point GetPositionOffset();
        Size GetSizeBoundary();
        WindowStateData GetWindowStateData(string targetState);
        bool PerformWindowOperation(IWindow window, string operation);
        bool PrepareWindowOperation(IWindow window, string operation);
    }

If your task bar doesn't implement any docking capability, you may want to always set it to Dock.Bottom (considering the most common task bar position).

The PrepareWindowOperation and PerformWindowOperation are executed consecutively when a window demands an operation in the task bar. You generally perform preparation in the PrepareWindowOperation (i.e, preparing animation and storyboard if any).

The GetPositionOffset and GetSizeBoundary tells UXDesktop the position and the size of your task bar. You need to return the correct coordinate of your task bar location, UXDesktop automatically knows what to do when performing maximize command.

Note: The interface is defined in Intersoft.Client.Framework assembly.

Hope this helps,
Jimmy

Glad to hear you figured out the problem. Let me know if you found any glitches when integrating it to the UI.

I initially didn't see any relations between the UI and the error that you encountered, but thought that you may add an object in the "callback" context, thus I suggest you using the BeginInvoke technique.

Based on your error stack trace, I still didn't see the relation between the dialog box and the "business rules". At a glance, this seems to be a constraint in DF in which a collection shouldn't be modified while it's being enumerated. Generally, your business rules wouldn't affect the Views, and vice versa.

I suggest you to replicate the problem "without" using dialog box/UI and see if you can successfully perform subsequent edits within the callback context. I presume that you should get the same exception here, I would be definitely interested if your results show otherwise.

Bill,

Thank you for providing more information about your scenario,

Okay, it appears that you're trying to modify the collection of the results passed from the collection in the event raised by DevForce, which is not allowed in this context.

CrossPlatform.BeginInvoke(
    new Action(delegate
    {
        // your code here
    }));

Let me know if that solves your problem.