zhangtaoeasy / flexmdi Goto Github PK

What steps will reproduce the problem?
1. Context menu currently only shows on window click

What is the expected output? What do you see instead?

A separate context menu for window click vs container click with differing
options

What steps will reproduce the problem?
1. Clicking and dragging on tiled windows still allows drag.

What is the expected output? What do you see instead?

Dragging is disabled for minimized windows.  I've implemented this on the
container window instances (and will be included with next check-in) but
because the Application instance uses PopUpManager, disabling needs to be
implemented differently.  Giving to you Brian cause you understand it
better than I.

MDIWindow can currently be resized from any corner or edge. Consider adding
MDIWindowResizeMode class with values such as NONE, ALL, BOTTOM_RIGHT,
CORNERS, EDGES, etc

Do it!

Could you please change the MDIWindow and MDIManager to permit the
definition of several windows with different themes (Focus Theme and No
Focus Theme)?
With this the users will have the possibility to define different styles to
their windows.
I’ve difined 2 properties in the MDIWindow for the Focus theme and the
NoFocus theme definition:

public var mdiFocusSkin:String = 'mdiWindowFocus';
public var mdiNoFocusSkin:String = 'mdiWindowNoFocus';


In the MDIManager I’ve changed “executeDefaultBehavior” function to:

case MDIManagerEvent.WINDOW_FOCUS_START:
    mgrEvent.window.styleName = mgrEvent.window.mdiFocusSkin;
    mgrEvent.effect.play();
    break;

case MDIManagerEvent.WINDOW_FOCUS_END:
    mgrEvent.window.styleName =  mgrEvent.window.mdiNoFocusSkin;
    mgrEvent.effect.play();
    break;


This is working for me, probably there is a better way.

Thanks

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Dragging on resize currently resizes real-time
2. Microsoft Windows behaviour draws an outline of intended resize shape

What is the expected output? What do you see instead?

Implement a "liveDragging" flag for resizing to draw an outline vs realtime
size changes.

Should be names like mdiWindowCloseBtn rather than closeBtn

What steps will reproduce the problem?
1. no way to capture/pause events through manager for developer input

What is the expected output? What do you see instead?

an observer to capture all effect events on start, allowing custom
functionality to be run before effect continues (eg. closing of window causes
confirmation dialog popup, etc...)

Something like this I spose:

<mdi:MDIWindow manager="{someManager}" />

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Create a new action script class which extends the MDICanvas class
2. Create a new application and insert the class from step one and then 
insert a couple of MDIWindow's
3. Run the app and ensure one of the windows is aligned at the top, then 
maximize one of the windows that is below. 

What is the expected output?The window maximized should take the entire 
MDICanvas area width=100% & height=100% with the other windows not 
visible. What do you see instead? The windows get maximized but the other 
windows are still visible and can be seen behind the maximized window.


What version of the product are you using?v1.0 On what operating system?XP


Please provide any additional information below. Attaching sample source 
and screen shot of the problem.

Make sure checks are done when adding, removing, etc

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

[deleted issue]

the events the managers set when the window is managed need to be removed
when the window is no longer managed.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

Title says it all

What steps will reproduce the problem?
1. Create a mdiWindow with a combobox and populate with some dumb data
2. Add it to the displaylist using mdiManager.global.add( thatWindow )
3. Click on the combobox to pick a value

What is the expected output? What do you see instead?
we should be able to see the options but they render under the mdiwindow

What version of the product are you using? On what operating system?
version 1.0

What steps will reproduce the problem?
1. Set 2 styles for the Focus and NoFocus of the MDIWindow. In these 2
styles set the backgroundAlpha property to “1” in the Focus and “0.2” in
the NoFocus style.
2. Test the window Focus and NoFocus style without minimising it.
3. Minimise one Window and restore it again.
4. Test the window Focus and NoFocus style again.

What is the expected output? What do you see instead?
The application should respect the user Style definition, but instead, when
the user restores a window the backgroundAlpha is set o “1”.

Please provide any additional information below.
The problem occurs because the MDIManager is forcing the backgroundAlpha
property in the “windowEventProxy” and “onMinimizeEffectEnd” functions.
I’ve commented these lines in the MDIManager code and tested it with success.

Thanks

Enables code like newMgr = new MDIManager(myCanvas) to add all mxml
children of myCanvas that are MDIWindows

What steps will reproduce the problem?
1. Only 1 "special" effects library currently

What is the expected output? What do you see instead?

We each create a custom effects library for demo

Allow resizing capability to be turned off

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

Should more accurately reflect their purpose, which has evolved since they
were defined

What steps will reproduce the problem?
1. If a window is minimized, it is still included in tiling/cascading
causing it to restore its siz

What is the expected output? What do you see instead?

Minimized windows should be ignored by tiling/cascading

What steps will reproduce the problem?
1. Minimizing window will reduce panel to header only, but leaves in
current position


What is the expected output? What do you see instead?

Minimized window will move to bottom of container in a tiled layout with
other minimized windows

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Create some windows for the global mgr and resize your browser
2. Minimized windows stay put
3.

What is the expected output? What do you see instead?
Should stay pinned to bottom

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Create an application
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" 
layout="absolute" xmlns:flexmdi="flexmdi.containers.*">
<flexmdi:MDICanvas width="100%" height="100%">
    <flexmdi:MDIWindow />
</flexmdi:MDICanvas>
</mx:Application>
2. Maximize
3. Minimize

What is the expected output? What do you see instead?
Nice little minimized bar.   Huge window on the bottom.

Please provide any additional information below.
Moxie B2

What steps will reproduce the problem?
1. This can be seen by the mdi explorer at 
http://www.returnundefined.com/flexmdi/explorer/
2. Go to the above site and right click on window 1 and select maximize 
without making the window active.
3. Window 1 will be maximized but window 2 can be seen inside of window 1

What is the expected output?Window should be maximize without other 
windows being visible. What do you see instead? Other windows can be seen 
when the non active window is maximized thru the context menu. Perhaps the 
option should not visible if the window is active or make the window 
active when context menu is shown.


What version of the product are you using?I believe its version 1.0 that 
the site http://www.returnundefined.com/flexmdi/explorer/ is using. On 
what operating system? XP


Please provide any additional information below.

What steps will reproduce the problem?
1. Cascading large windows will cause them to extend off container boundaries

What is the expected output? What do you see instead?

Determine an appropriate window height and width given number of windows
and size of container and resize all windows during cascade to match the
container dimensions.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. with the MDIExampleExplorer.mxml, in the addWindow() function, add this
line of code rigth before close the function and after all the normal code:
win.maximize();
2. the entire function will be like this:
private function addWindow():void
{
var win:MDIWindow = new MDIWindow();
win.width = 350;
win.title = "Window " + String(mdiCanvas.windowManager.windowList.length + 1);
mdiCanvas.windowManager.add(win);
win.maximize();
}
3. then run the program. Click on the button: "Add Window". Now click on
the restore button of the newest window.


What is the expected output? What do you see instead?
expected: window appear, maximize and user can restore it to the original
width and heigh that it was created in AS code.
what happens: when user click on restore, an error appear with the msg:
TypeError: Error #1009: Cannot access a property or method of a null object
reference.
    at flexmdi.effects.effectsLib::MDIVistaEffects/getWindowRestoreEffect()
    at flexmdi.managers::MDIManager/::windowEventProxy()
    at
flash.events::EventDispatcher/flash.events:EventDispatcher::dispatchEventFunctio
n()
    at flash.events::EventDispatcher/dispatchEvent()
    at mx.core::UIComponent/dispatchEvent()
    at flexmdi.containers::MDIWindow/maximizeRestore()

What version of the product are you using? On what operating system?
flexmdi 1.0, on Flex2.0.1, windowsXP

Please provide any additional information below.

What steps will reproduce the problem?
1. minimizeSize in MDIWindow class is mis-named

What is the expected output? What do you see instead?

should be named minimizeHeight

What steps will reproduce the problem?
1. I am using the http://www.returnundefined.com/flexmdi/explorer/. Click 
on add a window twice, so u should now have 4 windows in the canvas
2. Select window one to bring it to the front i.e. focus and then click on 
cascade.
3. It should be tile from top to bottom 1, 2, 3, 4 where 1 is still active.
4. Select window 4 to bring to front and you'll notice that is not active 
so when u drag around the window does not still become active. The only 
way to bring it to the front is to select another window, maximize does 
not show correctly as the other windows bleed thru. There are also times 
when multiple windows have focus, so it has two or more active windows. It 
seems to occur when the cascade operation is done.

What is the expected output?Only one window should be active, and when u 
click on a non active window it should become active and the other windows 
should be non active. What do you see instead? Multiple windows are 
active, some don't become active when clicked after a cascade operation.


What version of the product are you using?v1.0 On what operating system?xp


Please provide any additional information below.

What steps will reproduce the problem?
1. set the text to a large string
2. resize the window to the minimum

What is the expected output? What do you see instead?

Text should truncate as rigth buttons comes to the left.


What version of the product are you using? On what operating system?

actual trunk version

Please provide any additional information below.

Could you please change the MDIWindow container to permit the cursor
resizing images (cursor theme) to be customizable in the CSS file?

Thanks

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Generic skins on demo right now

What is the expected output? What do you see instead?

Get Fortier to start putting together some skins for us... 3 would be nice

What steps will reproduce the problem?
1. Define a MDICanvas class and insert a MDIWindow laying out the 
component in MXML.
2. Add constraint on the MDIWindow component.
3. When running the APP and u try to drag the MDIWindow component it 
always returns to the orignal position.

What is the expected output? It should move to the new position that you 
drag the window to. What do you see instead? The MDIWindow component 
returns to the original position instead staying where it was dragged to. 
If you maximize the MDIWindow componnent first then restore it and do a 
drag it will work correctly and stay where the MDIWindow was dropped to.

e.g. 
<flexmdi:MDICanvas id="mdic" width="500" height="500">
    <flexmdi:MDIWindow width="48%" height="48%" top="0" left="10" 
         id="panel1" title="panel1" />
    <mx:Spacer width="1%"/>

    <flexmdi:MDIWindow width="48%" height="48%" right="0" 
        top="0" id="panel2" title="panel2" />
    <flexmdi:MDIWindow width="48%" height="48%" bottom="0" 
        left="10" id="panel3" title="panel3"/>

    <mx:Spacer width="1%"/>

    <flexmdi:MDIWindow width="48%" height="48%" right="0" bottom="0"
         id="panel4" title="panel4" />       
</flexmdi:MDICanvas>

What version of the product are you using?FLEX 2.01 On what operating 
system? WINXP


Please provide any additional information below.

What steps will reproduce the problem?
1. Right now we only accept a function
2.
3.

What is the expected output? What do you see instead?
Should probably allow params to be sent also that can be passed in via
function.apply()

Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Drag a window close to the edge of a container, or another window instance
2. Dragged window does not recognize it is in the vicinity of an edge or
other window currently.

What is the expected output? What do you see instead?

When a window is in the vicinity of another window, or edge of container it
will "snap" to the other window/edge to dock itself.  When the "docked"
edges are resized, they will resize equally.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

The effects interface has a show effect but I think it should probably be
removed. ADDED_TO_STAGE might be a good replacement.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1. Open two MDIWindows.
2. Close one MDIWindow.
3. The remening MDIWindow dosn't receive a focusStart event.

What is the expected output? What do you see instead?

The MDIWindow that is remaning needs to be notified that it is now the one 
with focus.
No focusStart event is dispatched. 

What version of the product are you using? On what operating system?
latest flexmdi on Flex 2.0.1

Please provide any additional information below.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


Please use labels and text to provide additional information.