Resizing Regions
Hi,
I'm a new user to Logic having been a Cubase/Nuendo stalwart for 10 years.
I'm just playing around with the interface right now and trying to plug in to what I already know about what's different between the apps, thankfully they are very similar, however...
I can't resize a region!!!
I know I'm doing something wrong but myself and 2 other engineers sat here for 3 hours last night and could not drag a region from the start up to say half way or near the end of the region.
When clicking on the end of the region the pop up tooltip says: length change, but when clicking on the start of a region it says: left corner.
I can change the length from the start of the region when the region has no recorded notes in it, but as soon as notes are recorded I can't drag the region past the first recorded notes. If I cut the region, same deal...it only resizes from the new start point up until it hits the first note in that region.
This can't be a default function...can it? Everything I've read in the manual says it can be resized from the start or the end, so what's going on or what am I doing wrong??
Absolutely stumped!
Audio regions can be resized like you expect but Midi regions won't resize beyond a certain limit if they contain Midi events before the actual start of the Region containing that Midi data. You will have to cut them up using the scissor tool or make a selection with the marquee tool and click on the selection to create a new region.
Similar Messages
-
I'm having a problem resizing regions.
On some regions, I can make the region shorter, but I cannot lengthen it.
On other regions, I can make the region longer, but there is not silence in the added length - instead, the first notes of the region repeat (this happens using the little ruler symbol, not the the little circular arrow symbol)
Does it make any difference if the region is a copied region? Can you only lengthen original regions and not copied regions? I tried changing the resolution as per a prior post about this problem and that did not help.
Thanks for your suggestions.On some regions, I can make the region shorter, but I cannot lengthen it.
you can not make an audio ("real") region longer then it's total length.
On other regions, I can make the region longer, {but} the first notes of the region repeat (this happens using the little ruler symbol
by "ruler" do you mean the Right bracket? something like <]>
what type of region? -
Please help-resizing regions problem
It's only this song that's doing this:
When I resize the beginning of a region
in the arrange window, the contents of the region
shifts forward. It is behaving as though I am moving the
'anchor' of the region.
When I resize the end of a region, all the regions following it
move forward in the song.
I went through all the preferences, but there's nothing
that resembles this behavior.
From what I know, it is what I think pro tools calls "Slip editing"?
HELP!!!
MikeHi Mike,
Sounds to me like you have Drag Mode set to Shuffle L.
Look to the top right of the arrange window and you'll see Snap and Drag mode settings. The one you want to change is the drag mode. There are 5 settings but Shuffle L means that, if you change the length of a region, subsequent regions move to maintain the distance from the original. Try changing back to Overlap (or possibly no overlap, in which case other affected regions are trimmed but not moved and is a kind of slip mode, as you might commonly find in video editing).
Pete -
How to adjust the size of a region?
Hello, would anyone know how to adjust the size of a region size?
Thanks for your replies!Checkout an interesting article called " Oracle9iAS Portal Best Practices: Regions" to understand resizing region.
http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/OTN_CONTENT/MAINPAGE/PUBLISH_CONTMGMT/TECHNOTE_REGIONS_0.HTML -
Generalized Component Resizing
Hey people,
I wrote a "Component Resizer" which takes care of resizing components. Any component as opposed to just a window or a dialog.
One problem I noticed while resizing dialogs for example was that when I resize the dialog, the internal panes do not get adjust themselves to the new contained size. Now this happens even if I am using say GridBagLayout or GridLayout.
Another problem I noticed is that then a component inside a container is resized, the new size is retained until the parent container for this component itself is resized. Then it goes back to its original size. I guess this is because of the layout manager but then, this happens even when I use null layout. I have posted the code here (it's really long).
Any suggestions?
thanx,
-vijai.
Main resize handler:
* Copyright (c) 2004,
* Vijayaraghavan Kalyanapasupathy
* [email protected]
* See accompanying project license for license terms and agreement.
* The use of the intellectual property contained herein is subject
* to the terms of the license agreement. If no license agreement
* can be found at the locations from where you obtained this
* sofwtare/file/code fragment contact the author for the license.
* Contributors: Vijayaraghavan Kalyanapasupathy
* Created : 4:03:42 AM, Dec 2, 2004
* Project : SwingComponents
package org.swingcomponents.components;
import java.awt.Component;
import java.awt.Cursor;
import java.awt.Dimension;
import java.awt.event.MouseAdapter;
import java.awt.event.MouseEvent;
import java.awt.event.MouseListener;
import java.awt.event.MouseMotionListener;
import javax.swing.JComponent;
import org.apache.log4j.Logger;
/**<p>
* A configurable listener which can resize any component that can generate mouse drag and mouse events.
* </p>
* <p>
* General model for this is that <br/>
* <ul>
* <li> On demand resizing region margin
* <li> On demand resizing directions modification
* </ul>
* </p>
* @author Vijayaraghavan Kalyanapasupathy
public class ComponentResizer extends MouseAdapter
implements MouseListener,
MouseMotionListener {
static final int DEFAULT_MARGIN = 8;
* The sensitivity on the left side within which a mouse drag is interpreted as a resize action.
static int c_leftmargin = DEFAULT_MARGIN;
* The sensitivity on the right side within which a mouse drag is interpreted as a resize action.
static int c_rightmargin = DEFAULT_MARGIN;
* The sensitivity on the top within which a mouse drag is interpreted as a resize action.
static int c_topmargin = DEFAULT_MARGIN;
* The sensitivity on the bottom within which a mouse drag is interpreted as a resize action.
static int c_bottommargin = DEFAULT_MARGIN;
* Sets the default margins for all newly generated resizers.
* @param p_top The new top margin
* @param p_left The new left side margin
* @param p_bottom The new bottom margin
* @param p_right The new right side margin
public static void setDefaultMargins(int p_top,int p_left,int p_bottom,int p_right) {
c_logger.debug("Attempting to change application wide margins to: ("+p_top+","+p_left+","+p_bottom+","+p_right+")");
c_leftmargin = p_left > 0 ? p_left : c_leftmargin;
c_rightmargin = p_right > 0 ? p_right : c_rightmargin;
c_topmargin = p_top > 0 ? p_top : c_topmargin;
c_bottommargin = p_bottom > 0 ? p_bottom : c_bottommargin;
c_logger.debug("Changed application wide margins to: ("+c_topmargin+","+c_leftmargin+","+c_bottommargin+","+c_rightmargin+")");
* Retrieves the default application wide left margin used for newly created resizers.
* @return The default left margin
public static int getDefaultLeftMargin() {
return c_leftmargin;
* Retrieves the default application wide top margin used for newly created resizers.
* @return The default top margin
public static int getDefaultTopMargin() {
return c_topmargin;
* Retrieves the default application wide right margin used for newly created resizers.
* @return The default right margin
public static int getDefaultRightMargin() {
return c_rightmargin;
* Retrieves the default application wide bottom margin used for newly created resizers.
* @return The default bottom margin
public static int getDefaultBottomMargin() {
return c_bottommargin;
* The standard log4j logger that all instances of this class use
* to log messages.
static Logger c_logger = Logger.getLogger(ComponentResizer.class);
/* The cursors for each direction */
/** The top resize cursor */
static final Cursor c_topcursor = Cursor.getPredefinedCursor(Cursor.N_RESIZE_CURSOR);
/** The left side resize cursor */
static final Cursor c_leftcursor = Cursor.getPredefinedCursor(Cursor.W_RESIZE_CURSOR);
/** The right side resize cursor */
static final Cursor c_rightcursor = Cursor.getPredefinedCursor(Cursor.E_RESIZE_CURSOR);
/** The bottom resize cursor */
static final Cursor c_bottomcursor = Cursor.getPredefinedCursor(Cursor.S_RESIZE_CURSOR);
/** The topleft resize cursor */
static final Cursor c_topleftcursor = Cursor.getPredefinedCursor(Cursor.NW_RESIZE_CURSOR);
/** The topright resize cursor */
static final Cursor c_toprightcursor = Cursor.getPredefinedCursor(Cursor.NE_RESIZE_CURSOR);
/** The bottomleft resize cursor */
static final Cursor c_bottomleftcursor = Cursor.getPredefinedCursor(Cursor.SW_RESIZE_CURSOR);
/** The bottomright resize cursor */
static final Cursor c_bottomrightcursor = Cursor.getPredefinedCursor(Cursor.SE_RESIZE_CURSOR);
* Method that performs initialization stuff.
protected void InitializeResizer() {
c_logger.debug("Initializing resizer: ");
m_leftmargin = c_leftmargin;
m_rightmargin = c_rightmargin;
m_bottommargin = c_bottommargin;
m_topmargin = c_topmargin;
c_logger.debug("Initialized default margins from application wide settings: ("+m_topmargin+","+m_leftmargin+","+m_bottommargin+","+m_rightmargin+")");
c_logger.debug("Setting default resize options: ");
m_allowTopLeftResize = m_allowTopRightResize = true;
m_allowBottomLeftResize = m_allowBottomRightResize = true;
m_allowLeftResize = m_allowRightResize = true;
m_allowTopResize = m_allowBottomResize = true;
c_logger.debug("Getting component default cursor: ");
m_componentcursor = m_component.getCursor();
/** The resizer specific left side margin */
int m_leftmargin;
/** The resizer specific top margin */
int m_topmargin;
/** The resizer specific right side margin */
int m_rightmargin;
/** The resizer specific bottom margin */
int m_bottommargin;
/** Indicates that top side resizing should be allowed. */
boolean m_allowTopResize;
/** Indicates that bottom side resizing should be allowed. */
boolean m_allowBottomResize;
/** Indicates that left side resizing should be allowed. */
boolean m_allowLeftResize;
/** Indicates that right side resizing should be allowed. */
boolean m_allowRightResize;
/** Indicates that top left resizing should be allowed. */
boolean m_allowTopLeftResize;
/** Indicates that top right resizing should be allowed. */
boolean m_allowTopRightResize;
/** Indicates that bottom left resizing should be allowed. */
boolean m_allowBottomLeftResize;
/** Indicates that bottom right resizing should be allowed. */
boolean m_allowBottomRightResize;
/** The component that we are focussing on */
Component m_component = null;
/** The layout key for the component */
String m_layoutkey = null;
* Creates a new component resizer that attaches itself as a mouse listener and
* as a mouse motion listener to the given component.
* @param p_component The component to attach the listener to.
* @param p_layoutkey The key used in the layout manager of the component's parent for this object.
public ComponentResizer(Component p_component,String p_layoutkey) {
super();
m_component = p_component;
m_layoutkey = p_layoutkey;
if(m_component != null) {
c_logger.debug("Initializing resizer for: "+m_component);
InitializeResizer();
m_component.getToolkit().setDynamicLayout(true);
m_component.addMouseListener(this);
m_component.addMouseMotionListener(this);
}else {
c_logger.warn("Component is null: ");
* Sets the resizer specific bottom margin.
* @param p_bottommargin The bottommargin to set.
public void setBottomMargin(int p_bottommargin) {
c_logger.debug("Attempting to set top margin to: "+p_bottommargin);
m_bottommargin = p_bottommargin > 0 ? p_bottommargin : m_bottommargin;
c_logger.debug("Bottom margin set to: "+m_bottommargin);
* Sets the resizer specific left side margin.
* @param p_leftmargin The leftmargin to set.
public void setLeftMargin(int p_leftmargin) {
c_logger.debug("Attempting to set left margin to: "+p_leftmargin);
m_leftmargin = p_leftmargin > 0 ? p_leftmargin : m_leftmargin;
c_logger.debug("Left margin set to: "+m_leftmargin);
* Sets the resizer specific right side margin.
* @param p_rightmargin The rightmargin to set.
public void setRightMargin(int p_rightmargin) {
c_logger.debug("Attempting to set right margin to: "+p_rightmargin);
m_rightmargin = p_rightmargin > 0 ? p_rightmargin : m_rightmargin;
c_logger.debug("Right margin set to: "+m_rightmargin);
* Sets the resizer specific top margin.
* @param p_topmargin The topmargin to set.
public void setTopMargin(int p_topmargin) {
c_logger.debug("Attempting to set top margin to: "+p_topmargin);
m_topmargin = p_topmargin > 0 ? p_topmargin : m_topmargin;
c_logger.debug("Top margin set to: "+m_topmargin);
* Returns the bottom margin.
* @return Returns the bottommargin.
public int getBottomMargin() {
return m_bottommargin;
* Returns the left margin.
* @return Returns the leftmargin.
public int getLeftMargin() {
return m_leftmargin;
* Returns the right margin.
* @return Returns the rightmargin.
public int getRightMargin() {
return m_rightmargin;
* Returns the top margin.
* @return Returns the topmargin.
public int getTopMargin() {
return m_topmargin;
* @return Returns the allowBottomLeftResize.
public boolean isAllowBottomLeftResize() {
return m_allowBottomLeftResize;
* @return Returns the allowBottomResize.
public boolean isAllowBottomResize() {
return m_allowBottomResize;
* @return Returns the allowBottomRightResize.
public boolean isAllowBottomRightResize() {
return m_allowBottomRightResize;
* @return Returns the allowLeftResize.
public boolean isAllowLeftResize() {
return m_allowLeftResize;
* @return Returns the allowRightResize.
public boolean isAllowRightResize() {
return m_allowRightResize;
* @return Returns the allowTopLeftResize.
public boolean isAllowTopLeftResize() {
return m_allowTopLeftResize;
* @return Returns the allowTopResize.
public boolean isAllowTopResize() {
return m_allowTopResize;
* @return Returns the allowTopRightResize.
public boolean isAllowTopRightResize() {
return m_allowTopRightResize;
* @param p_allowBottomLeftResize The allowBottomLeftResize to set.
public void setAllowBottomLeftResize(boolean p_allowBottomLeftResize) {
c_logger.debug("Setting bottom left resizing to: "+p_allowBottomLeftResize);
m_allowBottomLeftResize = p_allowBottomLeftResize;
* @param p_allowBottomResize The allowBottomResize to set.
public void setAllowBottomResize(boolean p_allowBottomResize) {
c_logger.debug("Setting bottom resizing to: "+p_allowBottomResize);
m_allowBottomResize = p_allowBottomResize;
* @param p_allowBottomRightResize The allowBottomRightResize to set.
public void setAllowBottomRightResize(boolean p_allowBottomRightResize) {
c_logger.debug("Setting bottom right resizing to: "+p_allowBottomRightResize);
m_allowBottomRightResize = p_allowBottomRightResize;
* @param p_allowLeftResize The allowLeftResize to set.
public void setAllowLeftResize(boolean p_allowLeftResize) {
c_logger.debug("Setting left resizing to: "+p_allowLeftResize);
m_allowLeftResize = p_allowLeftResize;
* @param p_allowRightResize The allowRightResize to set.
public void setAllowRightResize(boolean p_allowRightResize) {
c_logger.debug("Setting right side resizing to: "+p_allowRightResize);
m_allowRightResize = p_allowRightResize;
* @param p_allowTopLeftResize The allowTopLeftResize to set.
public void setAllowTopLeftResize(boolean p_allowTopLeftResize) {
c_logger.debug("Setting top left resizing to: "+p_allowTopLeftResize);
m_allowTopLeftResize = p_allowTopLeftResize;
* @param p_allowTopResize The allowTopResize to set.
public void setAllowTopResize(boolean p_allowTopResize) {
c_logger.debug("Setting top side resizing to: "+p_allowTopResize);
m_allowTopResize = p_allowTopResize;
* @param p_allowTopRightResize The allowTopRightResize to set.
public void setAllowTopRightResize(boolean p_allowTopRightResize) {
c_logger.debug("Setting top right resizing to: "+p_allowTopRightResize);
m_allowTopRightResize = p_allowTopRightResize;
* Following are the methods that do all the real stuff.
/* We define constants that allow us to determine where the cursor is. */
static final int TOP = 0x0001;
static final int BOTTOM = 0x0002;
static final int LEFT = 0x0100;
static final int RIGHT = 0x0200;
static final int TOPLEFT = 0x0101;
static final int TOPRIGHT = 0x0201;
static final int BOTTOMLEFT = 0x0102;
static final int BOTTOMRIGHT = 0x0202;
static final int UNKNOWN = 0x0000;
protected int whereX(int p_x) {
// check if on left side
if(p_x >= 0 &&
p_x <= m_leftmargin) {
c_logger.debug("Cursor is on LEFT");
return LEFT;
// check if on right side
if(p_x <= m_component.getWidth() &&
p_x >= m_component.getWidth()-m_rightmargin) {
c_logger.debug("Cursor is on RIGHT");
return RIGHT;
return UNKNOWN;
protected int whereY(int p_y) {
// check if on top side
if(p_y >= 0 &&
p_y <= m_topmargin) {
c_logger.debug("Cursor is on TOP");
return TOP;
// check if on bottom side
if(p_y <= m_component.getHeight() &&
p_y >= m_component.getHeight()-m_bottommargin) {
c_logger.debug("Cursor is on BOTTOM");
return BOTTOM;
return UNKNOWN;
protected int where(int p_x,int p_y) {
c_logger.debug("Determining pointer location: ");
int l_composite = (whereX(p_x) | whereY(p_y));
switch(l_composite) {
case LEFT:
c_logger.debug("Left");
break;
case RIGHT:
c_logger.debug("Right");
break;
case BOTTOM:
c_logger.debug("Bottom");
break;
case TOP:
c_logger.debug("Top");
break;
case TOPLEFT:
c_logger.debug("Top left");
break;
case TOPRIGHT:
c_logger.debug("Top right");
break;
case BOTTOMLEFT:
c_logger.debug("Bottom left");
break;
case BOTTOMRIGHT:
c_logger.debug("Bottom right");
break;
return l_composite;
* The component's default cursor.
Cursor m_componentcursor;
boolean m_resizingcursor;
boolean m_dragready;
protected void changeCursor(int p_where) {
c_logger.debug("Changing cursor: ");
m_resizingcursor = true;
switch(p_where) {
case LEFT:
if(m_allowLeftResize) {
m_component.setCursor(c_leftcursor);
}else {
m_resizingcursor = false;
break;
case RIGHT:
if(m_allowRightResize) {
m_component.setCursor(c_rightcursor);
}else {
m_resizingcursor = false;
break;
case TOP:
if(m_allowTopResize) {
m_component.setCursor(c_topcursor);
}else {
m_resizingcursor = false;
break;
case BOTTOM:
if(m_allowBottomResize) {
m_component.setCursor(c_bottomcursor);
}else {
m_resizingcursor = false;
break;
case TOPLEFT:
if(m_allowTopLeftResize) {
m_component.setCursor(c_topleftcursor);
}else {
m_resizingcursor = false;
break;
case TOPRIGHT:
if(m_allowTopRightResize) {
m_component.setCursor(c_toprightcursor);
}else {
m_resizingcursor = false;
break;
case BOTTOMLEFT:
if(m_allowBottomLeftResize) {
m_component.setCursor(c_bottomleftcursor);
}else {
m_resizingcursor = false;
break;
case BOTTOMRIGHT:
if(m_allowBottomRightResize) {
m_component.setCursor(c_bottomrightcursor);
}else {
m_resizingcursor = false;
break;
default:
c_logger.debug("Reverting to default component cursor: ");
m_resizingcursor = false;
m_component.setCursor(m_componentcursor);
break;
protected void modifyBounds(int p_newx,int p_newy,int p_newwidth,int p_newheight) {
m_component.setBounds(p_newx,p_newy,p_newwidth,p_newheight);
m_component.setSize(p_newwidth,p_newheight);
/*if(m_component.getParent() != null) {
LayoutManager l_manager = m_component.getParent().getLayout();
if(l_manager != null) {
l_manager.removeLayoutComponent(m_component);
l_manager.addLayoutComponent(m_layoutkey,m_component);
if(m_component instanceof JComponent) {
((JComponent) m_component).setPreferredSize(new Dimension(p_newwidth,p_newheight));
m_component.repaint();
protected void resizeLeft(MouseEvent p_e) {
c_logger.debug("Resizing left side: ");
if(p_e.getX() <= m_component.getWidth()-m_leftmargin-m_rightmargin-4) {
int l_newx = m_component.getX();
int l_newwidth = m_component.getWidth();
c_logger.debug("Eligible for leftward resize: ");
if(p_e.getX() <= 0) {
c_logger.debug("Leftward drag: ");
l_newx = p_e.getX()+m_component.getX();
l_newwidth = m_component.getWidth()-p_e.getX();
}else {
c_logger.debug("anti-Leftward drag: ");
l_newx = m_component.getX()-p_e.getX();
l_newwidth = m_component.getWidth()-p_e.getX();
c_logger.debug("Component new X: "+l_newx);
c_logger.debug("Component new W: "+l_newwidth);
modifyBounds(l_newx,m_component.getY(),l_newwidth,m_component.getHeight());
protected void resizeBottom(MouseEvent p_e) {
c_logger.debug("Resizing bottom side: ");
if(p_e.getY() >= m_topmargin+m_bottommargin+4) {
c_logger.debug("Eligible for bottom side resize: ");
int l_newheight = p_e.getY();
c_logger.debug("Component new H: "+l_newheight);
modifyBounds(m_component.getX(),m_component.getY(),m_component.getWidth(),l_newheight);
protected void resizeRight(MouseEvent p_e) {
c_logger.debug("Resizing right side: ");
if(p_e.getX() >= m_leftmargin+m_rightmargin+4) {
c_logger.debug("Eligible for right side resize: ");
int l_newwidth = p_e.getX();
c_logger.debug("Component new W: "+l_newwidth);
modifyBounds(m_component.getX(),m_component.getY(),l_newwidth,m_component.getHeight());
protected void resizeTop(MouseEvent p_e) {
c_logger.debug("Resizing top side: ");
if(p_e.getY() <= m_component.getHeight()-m_topmargin-m_bottommargin-4) {
int l_newy = m_component.getY();
int l_newheight = m_component.getHeight();
c_logger.debug("Eligible for top side resize: ");
if(p_e.getY() <= 0) {
c_logger.debug("Topward drag: ");
l_newy = m_component.getY()+p_e.getY();
l_newheight = m_component.getHeight()-p_e.getY();
}else {
c_logger.debug("anti-Topward drag: ");
l_newy = m_component.getY()+p_e.getY();
l_newheight = m_component.getHeight()-p_e.getY();
c_logger.debug("Component new Y: "+l_newy);
c_logger.debug("Component new H: "+l_newheight);
modifyBounds(m_component.getX(),l_newy,m_component.getWidth(),l_newheight);
protected void resizeBottomLeft(MouseEvent p_e) {
c_logger.debug("Resizing southwest...");
resizeBottom(p_e);
resizeLeft(p_e);
protected void resizeBottomRight(MouseEvent p_e) {
c_logger.debug("Resizing southeast...");
resizeBottom(p_e);
resizeRight(p_e);
protected void resizeTopLeft(MouseEvent p_e) {
c_logger.debug("Resizing northwest...");
resizeTop(p_e);
resizeLeft(p_e);
protected void resizeTopRight(MouseEvent p_e) {
c_logger.debug("Resizing northeast...");
resizeTop(p_e);
resizeRight(p_e);
/* (non-Javadoc)
* @see java.awt.event.MouseMotionListener#mouseDragged(java.awt.event.MouseEvent)
public void mouseDragged(MouseEvent p_e) {
c_logger.debug("Dragged at: "+p_e.getX()+","+p_e.getY());
if(m_resizingcursor) {
c_logger.debug("Resizing... ");
switch(m_component.getCursor().getType()) {
case Cursor.E_RESIZE_CURSOR:
resizeRight(p_e);
break;
case Cursor.SE_RESIZE_CURSOR:
resizeBottomRight(p_e);
break;
case Cursor.N_RESIZE_CURSOR:
resizeTop(p_e);
break;
case Cursor.NE_RESIZE_CURSOR:
resizeTopRight(p_e);
break;
case Cursor.S_RESIZE_CURSOR:
resizeBottom(p_e);
break;
case Cursor.SW_RESIZE_CURSOR:
resizeBottomLeft(p_e);
break;
case Cursor.NW_RESIZE_CURSOR:
resizeTopLeft(p_e);
break;
case Cursor.W_RESIZE_CURSOR:
resizeLeft(p_e);
break;
/* (non-Javadoc)
* @see java.awt.event.MouseMotionListener#mouseMoved(java.awt.event.MouseEvent)
public void mouseMoved(MouseEvent p_e) {
c_logger.debug("Moved at: "+p_e.getX()+","+p_e.getY());
changeCursor(where(p_e.getX(),p_e.getY()));
/* (non-Javadoc)
* @see java.awt.event.MouseListener#mouseClicked(java.awt.event.MouseEvent)
public void mouseClicked(MouseEvent p_e) {
c_logger.debug("Clicked at: "+p_e.getX()+","+p_e.getY());
/* (non-Javadoc)
* @see java.awt.event.MouseListener#mouseEntered(java.awt.event.MouseEvent)
public void mouseEntered(MouseEvent p_e) {
c_logger.debug("Entered at: "+p_e.getX()+","+p_e.getY());
/* (non-Javadoc)
* @see java.awt.event.MouseListener#mouseExited(java.awt.event.MouseEvent)
public void mouseExited(MouseEvent p_e) {
c_logger.debug("Exited at: "+p_e.getX()+","+p_e.getY());
if(!m_dragready) {
changeCursor(UNKNOWN);
/* (non-Javadoc)
* @see java.awt.event.MouseListener#mousePressed(java.awt.event.MouseEvent)
public void mousePressed(MouseEvent p_e) {
c_logger.debug("Pressed at: "+p_e.getX()+","+p_e.getY());
if(m_resizingcursor) {
m_dragready = true;
/* (non-Javadoc)
* @see java.awt.event.MouseListener#mouseReleased(java.awt.event.MouseEvent)
public void mouseReleased(MouseEvent p_e) {
c_logger.debug("Released at: "+p_e.getX()+","+p_e.getY());
m_dragready = false;
}Test file:
* Copyright (c) 2004,
* Vijayaraghavan Kalyanapasupathy
* [email protected]
* See accompanying project license for license terms and agreement.
* The use of the intellectual property contained herein is subject
* to the terms of the license agreement. If no license agreement
* can be found at the locations from where you obtained this
* sofwtare/file/code fragment contact the author for the license.
* Contributors: Vijayaraghavan Kalyanapasupathy
* Created : 4:55:08 AM, Dec 2, 2004
* Project : SwingComponents
package org.swingcomponents.tests;
import java.awt.Color;
import java.awt.Dimension;
import javax.swing.JDialog;
import javax.swing.JFrame;
import javax.swing.JPanel;
import javax.swing.JTextArea;
import javax.swing.border.LineBorder;
import org.netbeans.lib.awtextra.AbsoluteConstraints;
import org.netbeans.lib.awtextra.AbsoluteLayout;
import org.swingcomponents.components.ComponentResizer;
* @author Vijayaraghavan Kalyanapasupathy
public class TestComponentResizer {
public static void testUndecoratedDialog() {
try {
JDialog.setDefaultLookAndFeelDecorated(false);
JDialog l_dialog = new JDialog(new JFrame());
JDialog.setDefaultLookAndFeelDecorated(true);
l_dialog.setUndecorated(true);
l_dialog.setLocation(400,500);
l_dialog.setSize(300,300);
l_dialog.setVisible(true);
l_dialog.setDefaultCloseOperation(JDialog.EXIT_ON_CLOSE);
l_dialog.setBackground(Color.BLACK);
JPanel l_panel = new JPanel();
l_panel.setBorder(LineBorder.createGrayLineBorder());
l_dialog.getContentPane().add(l_panel);
ComponentResizer l_resizer = new ComponentResizer(l_dialog,null);
l_dialog.pack();
l_dialog.show();
}catch (Throwable t) {
t.printStackTrace(System.err);
public static void testJTextArea() {
try {
JFrame l_frame = new JFrame("Test DropDownDialog") {
public Dimension getPreferredSize() {
return new Dimension(800,600);
JTextArea l_area = new JTextArea(10,40);
ComponentResizer l_resizer = new ComponentResizer(l_area,null);
l_frame.getContentPane().setLayout(new AbsoluteLayout());
l_frame.getContentPane().add(l_area, new AbsoluteConstraints(300,400,300,300));
l_frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
l_frame.pack();
l_frame.show();
}catch(Throwable t) {
t.printStackTrace(System.err);
public static void main(String[] args) {
testJTextArea();
//testUndecoratedDialog();
}Apologies,
I have left out the AbsoluteLayout and AbsoluteConstraints, but the same effect can supposedly be achieved using null layout and absolute positioning. This doesn't work for me, so if you would like those files (from netBeans) I will post them as well.
thanx,
-vijai. -
Using JAvaFX 2.2 I have implemented a custom control. To figuring out the internal proportions this control needs to be resizable. However after these internals are sorted out, the control should no longer change it's size. What's the best way to do that, besides overriding the isResizable method to return the value false, after the internals are sorted out?
Below is a stacktrace, showing the call hierarchy of the first unwanted size change.
this.boundsInParentProperty().addListener(new ChangeListener<Bounds>(){
@Override
public void changed(ObservableValue<? extends Bounds> arg0,
Bounds arg1, Bounds arg2) {
System.out.println("New bounds of Pagination: "+arg2);
new Exception("Cause for Bounds change").printStackTrace();
java.lang.Exception: Cause for Bounds change
at ch.sahits.game.javafx.control.Pagination$5.changed(Pagination.java:118)
at ch.sahits.game.javafx.control.Pagination$5.changed(Pagination.java:1)
at com.sun.javafx.binding.ExpressionHelper$SingleChange.fireValueChangedEvent(ExpressionHelper.java:196)
at com.sun.javafx.binding.ExpressionHelper.fireValueChangedEvent(ExpressionHelper.java:100)
at javafx.scene.Node$LazyBoundsProperty.invalidate(Node.java:7555)
at javafx.scene.Node$MiscProperties.invalidateBoundsInParent(Node.java:4980)
at javafx.scene.Node.invalidateBoundsInParent(Node.java:2730)
at javafx.scene.Node.transformedBoundsChanged(Node.java:3349)
at javafx.scene.Node.localBoundsChanged(Node.java:3333)
at javafx.scene.Node.impl_geomChanged(Node.java:3321)
at javafx.scene.Parent.impl_geomChanged(Parent.java:1705)
at javafx.scene.Parent.childBoundsChanged(Parent.java:1729)
at javafx.scene.Node.notifyParentOfBoundsChange(Node.java:3382)
at javafx.scene.Node.transformedBoundsChanged(Node.java:3351)
at javafx.scene.Node.localBoundsChanged(Node.java:3333)
at javafx.scene.Node.impl_geomChanged(Node.java:3321)
at javafx.scene.Parent.impl_geomChanged(Parent.java:1705)
at javafx.scene.layout.Region.access$900(Region.java:104)
at javafx.scene.layout.Region$3.invalidated(Region.java:423)
at javafx.beans.property.DoublePropertyBase.markInvalid(DoublePropertyBase.java:129)
at javafx.beans.property.DoublePropertyBase.set(DoublePropertyBase.java:163)
at javafx.scene.layout.Region.setWidth(Region.java:442)
at javafx.scene.layout.Region.resize(Region.java:1312)
at javafx.scene.Node.resizeRelocate(Node.java:2667)
at javafx.scene.control.Control.layoutChildren(Control.java:892)
at javafx.scene.Parent.layout(Parent.java:1018)
at javafx.scene.Parent.layout(Parent.java:1028)
at javafx.scene.Scene.layoutDirtyRoots(Scene.java:516)
at javafx.scene.Scene.doLayoutPass(Scene.java:487)
at javafx.scene.Scene.preferredSize(Scene.java:1489)
at javafx.scene.Scene.impl_preferredSize(Scene.java:1516)
at javafx.stage.Window$9.invalidated(Window.java:716)
at javafx.beans.property.BooleanPropertyBase.markInvalid(BooleanPropertyBase.java:127)
at javafx.beans.property.BooleanPropertyBase.set(BooleanPropertyBase.java:161)
at javafx.stage.Window.setShowing(Window.java:779)
at javafx.stage.Window.show(Window.java:794)
at javafx.stage.Stage.show(Stage.java:229)
at ch.sahits.game.graphic.display.dialog.OpenPaticianTestApplicationWindow.start(OpenPaticianTestApplicationWindow.java:59)
at com.sun.javafx.application.LauncherImpl$5.run(LauncherImpl.java:319)
at com.sun.javafx.application.PlatformImpl$5.run(PlatformImpl.java:215)
at com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:179)
at com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:176)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.javafx.application.PlatformImpl$4.run(PlatformImpl.java:176)
at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:76)
at com.sun.glass.ui.gtk.GtkApplication._runLoop(Native Method)
at com.sun.glass.ui.gtk.GtkApplication$3$1.run(GtkApplication.java:82)
at java.lang.Thread.run(Thread.java:724)Let me reformulate the question:
If I implement the control as non resizable:
public boolean isResizable() {
return false;
What else to I have to implement? How can I ensure that the component has the correct dimensions? The width and height properties are read only. -
"Mouse Over" issues in Logic Pro - Mountain Lion
Hi,
Since I upgraded to Mountain Lion, I spotted an issue with Logic Pro (Logic 9).
In the Arrange window, when pointing the mouse at the end of a region, the pointer icon doesn't change to the looping (upper right corner of the region) or resize (lower right corner) icon.
As a result, those functionalities (looping and resizing regions) are gone.
Anyone having the same issue?
Is there a way to solve this or do we need to wait for a Logic Pro update to get these back?
Thanks in advance,
A nice day everyone,
VinceVlvl wrote:
As it's the only problem I have noticed since the upgrade, and as I mentioned in my last post, looking like a minor problem to me, I will keep Mountain Lion.
But anyway, thanks for the advice, Ivan.
Vince
No problem, as a professional musician using Logic I learned that lesson the hard way first time around. Hard as it was to not have the toys I soon learned that stability ruled the day.... -
Button in custom component not showing
I made a very simple custom component with a TextField and Button but when I add multiple instances of it to a Layout, only the first Button shows up while the other show only when I focus the corresponding TextField. I'm quite new to fx and I'm not sure I did everything correctly but I don't see any obvious error in my code.
The component:
public class TestComponent extends BorderPane {
@FXML
private Button browseButton;
@FXML
private TextField textField;
public TestComponent() {
FXMLLoader fxmlLoader = new FXMLLoader(getClass().getResource("TestComponent.fxml"));
fxmlLoader.setRoot(this);
fxmlLoader.setController(this);
try {
fxmlLoader.load();
} catch (IOException exception) {
throw new RuntimeException(exception);
The fxml
<?xml version="1.0" encoding="UTF-8"?>
<?import java.lang.*?>
<?import javafx.scene.control.*?>
<?import javafx.scene.layout.HBox?>
<fx:root type="javafx.scene.layout.BorderPane" xmlns:fx="http://javafx.com/fxml/1"
xmlns="http://javafx.com/javafx/2.2">
<center>
<TextField fx:id="textField" prefWidth="200.0" />
</center>
<right>
<Button fx:id="browseButton" mnemonicParsing="false" maxHeight="-Infinity"
minHeight="-Infinity" prefHeight="${textField.height}" text="Browse"
textAlignment="CENTER" />
</right>
</fx:root>
and the test code
@Override
public void start(Stage primaryStage) {
VBox box = new VBox(5);
box.setPadding(new Insets(5));
TestComponent a = new TestComponent();
TestComponent b = new TestComponent();
TestComponent c = new TestComponent();
box.getChildren().addAll(a, b, c);
Scene scene = new Scene(box);
primaryStage.setScene(scene);
primaryStage.show();
I'm running on Ubuntu with jdk-8-ea-bin-b111-linux-i586-10_oct_2013. I tested with jdk 1.7.0_40 and the buttons don't show.
I'd include screenshots but the button to add images is disabled.
Thanks for the helpThe issue is with the bind definition in the FXML, if you remove that definition, the buttons will display.
prefHeight="${textField.height}"
I think the binding is working, but when there is some kind of error (bug) in the layout process such that the scene is not automatically laid out correctly when the binding occurs.
You can get exactly the same behaviour by removing the binding definition in FXML and placing it in code after the load.
browseButton.prefHeightProperty().bind(textField.heightProperty());
When the scene is initially displayed, the height of all of the text fields is 0, as they have not been laid out yet, and the browser button prefHeight gets set to 0 through the binding.
That's OK and expected.
Then the scene is shown and a layout pass occurs, which sets the height of the text fields to 26 and the prefHeight of all of the browser buttons adjust correctly.
That's also OK and expected.
Next the height of one of the buttons is adjusted via a layout pass.
That's also OK and expected.
But the height of the other buttons is not adjusted to match their preferred height (probably because a layout pass is not run on them).
That is not OK and not expected (and I think a bug).
If you manually trigger a layout pass on one of the components which did not render completely, the button will be displayed - but that should not be necessary.
You can file a bug against the Runtime project at:
https://javafx-jira.kenai.com/
You will need to sign up at the link on the login page, but anybody can sign up and log a bug.
Here is some sample code.
import javafx.application.Application;
import javafx.geometry.Insets;
import javafx.scene.Scene;
import javafx.scene.layout.VBox;
import javafx.stage.Stage;
public class ComponentTestApp extends Application {
@Override
public void start(Stage primaryStage) {
VBox box = new VBox(5);
box.setPadding(new Insets(5));
TestComponent a = new TestComponent();
TestComponent b = new TestComponent();
TestComponent c = new TestComponent();
box.getChildren().addAll(a, b, c);
Scene scene = new Scene(box);
primaryStage.setScene(scene);
primaryStage.show();
b.requestLayout(); // I don't understand why this call is necessary -> looks like a bug to me . . .
public static void main(String[] args) {
launch(args);
import javafx.beans.value.ChangeListener;
import javafx.beans.value.ObservableValue;
import javafx.fxml.FXML;
import javafx.fxml.FXMLLoader;
import javafx.scene.control.Button;
import javafx.scene.control.TextField;
import javafx.scene.layout.BorderPane;
import java.io.IOException;
public class TestComponent extends BorderPane {
private static int nextComponentNum = 1;
private final int componentNum = nextComponentNum;
@FXML
private TextField textField;
@FXML
private Button browseButton;
public TestComponent() {
nextComponentNum++;
FXMLLoader fxmlLoader = new FXMLLoader(getClass().getResource("TestComponent.fxml"));
fxmlLoader.setRoot(this);
fxmlLoader.setController(this);
try {
fxmlLoader.load();
browseButton.prefHeightProperty().bind(textField.heightProperty());
System.out.println(componentNum + " " + browseButton + " prefHeight " + browseButton.getPrefHeight());
textField.heightProperty().addListener(new ChangeListener<Number>() {
@Override
public void changed(ObservableValue<? extends Number> observable, Number oldValue, Number newValue) {
System.out.println(componentNum + " " + textField + " height " + newValue);
browseButton.prefHeightProperty().addListener(new ChangeListener<Number>() {
@Override
public void changed(ObservableValue<? extends Number> observable, Number oldValue, Number newValue) {
System.out.println(componentNum + " " + browseButton + " prefHeight " + newValue);
browseButton.heightProperty().addListener(new ChangeListener<Number>() {
@Override
public void changed(ObservableValue<? extends Number> observable, Number oldValue, Number newValue) {
System.out.println(componentNum + " " + browseButton + " height " + newValue);
new Exception("Not a real exception - just a debugging stack trace").printStackTrace();
} catch (IOException exception) {
throw new RuntimeException(exception);
<?xml version="1.0" encoding="UTF-8"?>
<?import java.lang.*?>
<?import javafx.scene.control.*?>
<?import javafx.scene.layout.HBox?>
<fx:root type="javafx.scene.layout.BorderPane" xmlns:fx="http://javafx.com/fxml/1"
xmlns="http://javafx.com/javafx/2.2">
<center>
<TextField fx:id="textField" prefWidth="200.0" />
</center>
<right>
<Button fx:id="browseButton" mnemonicParsing="false" maxHeight="-Infinity"
minHeight="-Infinity" text="Browse"
textAlignment="CENTER" />
<!--<Button fx:id="browseButton" mnemonicParsing="false" maxHeight="-Infinity"-->
<!--minHeight="-Infinity" prefHeight="${textField.height}" text="Browse"-->
<!--textAlignment="CENTER" />-->
</right>
</fx:root>
Here is the output of the sample code:
1 Button[id=browseButton, styleClass=button]'Browse' prefHeight 0.0
2 Button[id=browseButton, styleClass=button]'Browse' prefHeight 0.0
3 Button[id=browseButton, styleClass=button]'Browse' prefHeight 0.0
1 Button[id=browseButton, styleClass=button]'Browse' prefHeight 26.0
1 TextField[id=textField, styleClass=text-input text-field] height 26.0
2 Button[id=browseButton, styleClass=button]'Browse' prefHeight 26.0
2 TextField[id=textField, styleClass=text-input text-field] height 26.0
3 Button[id=browseButton, styleClass=button]'Browse' prefHeight 26.0
3 TextField[id=textField, styleClass=text-input text-field] height 26.0
2 Button[id=browseButton, styleClass=button]'Browse' height 26.0
java.lang.Exception: Not a real exception - just a debugging stack trace
at testcomponent.TestComponent$3.changed(TestComponent.java:69)
at testcomponent.TestComponent$3.changed(TestComponent.java:65)
at com.sun.javafx.binding.ExpressionHelper$Generic.fireValueChangedEvent(ExpressionHelper.java:347)
at com.sun.javafx.binding.ExpressionHelper.fireValueChangedEvent(ExpressionHelper.java:80)
at javafx.beans.property.ReadOnlyDoubleWrapper$ReadOnlyPropertyImpl.fireValueChangedEvent(ReadOnlyDoubleWrapper.java:177)
at javafx.beans.property.ReadOnlyDoubleWrapper.fireValueChangedEvent(ReadOnlyDoubleWrapper.java:143)
at javafx.beans.property.DoublePropertyBase.markInvalid(DoublePropertyBase.java:113)
at javafx.beans.property.DoublePropertyBase.set(DoublePropertyBase.java:146)
at javafx.scene.layout.Region.setHeight(Region.java:915)
at javafx.scene.layout.Region.resize(Region.java:1362)
at javafx.scene.layout.BorderPane.layoutChildren(BorderPane.java:583)
at javafx.scene.Parent.layout(Parent.java:1063)
at javafx.scene.Parent.layout(Parent.java:1069)
at javafx.scene.Scene.doLayoutPass(Scene.java:564)
at javafx.scene.Scene$ScenePulseListener.pulse(Scene.java:2341)
at com.sun.javafx.tk.Toolkit.firePulse(Toolkit.java:329)
at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:479)
at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:460)
at com.sun.javafx.tk.quantum.QuantumToolkit$13.run(QuantumToolkit.java:327)
at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:95)
java.lang.Exception: Not a real exception - just a debugging stack trace
at testcomponent.TestComponent$3.changed(TestComponent.java:69)
at testcomponent.TestComponent$3.changed(TestComponent.java:65)
at com.sun.javafx.binding.ExpressionHelper$Generic.fireValueChangedEvent(ExpressionHelper.java:347)
at com.sun.javafx.binding.ExpressionHelper.fireValueChangedEvent(ExpressionHelper.java:80)
at javafx.beans.property.ReadOnlyDoubleWrapper$ReadOnlyPropertyImpl.fireValueChangedEvent(ReadOnlyDoubleWrapper.java:177)
at javafx.beans.property.ReadOnlyDoubleWrapper.fireValueChangedEvent(ReadOnlyDoubleWrapper.java:143)
at javafx.beans.property.DoublePropertyBase.markInvalid(DoublePropertyBase.java:113)
at javafx.beans.property.DoublePropertyBase.set(DoublePropertyBase.java:146)
at javafx.scene.layout.Region.setHeight(Region.java:915)
at javafx.scene.layout.Region.resize(Region.java:1362)
at javafx.scene.layout.BorderPane.layoutChildren(BorderPane.java:583)
at javafx.scene.Parent.layout(Parent.java:1063)
at javafx.scene.Parent.layout(Parent.java:1069)
at javafx.scene.Scene.doLayoutPass(Scene.java:564)
at javafx.scene.Scene$ScenePulseListener.pulse(Scene.java:2341)
at com.sun.javafx.tk.Toolkit.firePulse(Toolkit.java:329)
at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:479)
at com.sun.javafx.tk.quantum.QuantumToolkit.pulse(QuantumToolkit.java:460)
at com.sun.javafx.tk.quantum.QuantumToolkit$13.run(QuantumToolkit.java:327)
at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:95)
1 Button[id=browseButton, styleClass=button]'Browse' height 26.0 -
Re-sizing the window question...
Hello,
I have just purchased GB3 as part of the iLife '06 package - Wonderful stuff!
My only issue is simply this...
I cannot for the life in me, work out how to re-size the window of GB. It is just a little too large for my screen here. The three small diagonal lines at the bottom right hand corner of the window don't work as they do in all other Applications.
I am doing something wrong or am I being an advanced muppet? ( again! )
Thanks in advance.
Regards
IanHello Ian,
This below is from Apple so it is suppose to resize as the other versions.
GB 3.0 help
If it is not working as it is meant to maybe this update will help " correct other minor issues"
http://www.apple.com/support/downloads/garageband302update.html
it appears you can also resize the regions are these perhaps in need of being resized first before the entire browser can be resized ?
Resize Regions
"You can resize regions by either shortening or lengthening them.
When you shorten a region, only the visible part of the loop plays.
When you lengthen a region, you add silence (blank space) to its beginning or end.
To resize a region:
1. Move the pointer over the lower half of either edge of the region. The pointer changes to a resize pointer, with an arrow pointing away from the region.
2. Drag the edge of the region to shorten it or lengthen it.
3. Resizing a region by lengthening adds silence to the region. This can be useful if you want to make copies of the region, each lasting for a certain number of beats."
Hth some, Enjoy it sounds fun~!!
Regards,
Eme;~{) -
Honeymoon is over, spaces is driving me nutz
well i've been using 10.5 and spaces for a few months now.
on the whole, i need "spaces" and can't work without it... but...
it needs a few things fixed...
#1- i am using "spaces" in combination with "side-by-side" display to a projector in a working meeting. and the 2 features just don't work well together... they have different models for how the programs work that are not entirely compatible from either a software perspective or a user perspective...
first, is the problem that some software just gets confused about where show the open window, either on the external or internal display. i expect this is more of a problem with the 3rd party software... however, it creates havoc when trying to open windows and get them the right size to display on an overhead projector in a meeting... sometimes clicking on the green resize button makes the window jump from the overhead screen to the internal display. sometimes trying to grab the window resize region in the bottom right corner of the window, the window won't go any bigger than the labtop sized instead of the overhead projector size... then there is the periodic problem that the window opens actually bigger that the actual display area so it is impossible to either get the green resize button or the manual resize handle on the bottom corner of the window because both are off the edge of the display and there's no way get to it...
now throw in the fact that programs also get confused with spaces and that some of the options for spaces and the side by side displays conflict, and it really gets like a circus...
with spaces active only, i can grab the open window and shove it off the right or left of the display and spaces automatically switches to the next space and transfers the window i'm dragging to that space. however, with the side by side displays for the internal display and overhead projector, dragging a window only moves it between those windows and not between spaces... also since the hot corners are on the side corners to turn on expose and spaces and screen savers, sometime trying to move between the internal or external display will activate one of those. or when trying to active space by moving the cursor to a hot corner, then it only transfers between the internal/external display and won't actually start the tbumbnail for the spaces... then when i use F8, the spaces thumbnail show up on both the internal monitor and external projector. so to transfer a window between spaces and then put it up on the external projector, the display is swiping back and forth, the expose is popping on and off and the audience is of course looking at me like i'm a mad man, which of course they are right...
unfortunately, the best way i've been able to use an overhead projector with spaces is to use "mirror display" in the "display" control panel. this defeats the great option of being able to work on windows on my laptop that i can only see and not distract the meeting audience with finding email messages, finder windows to open and other file, typing myself a reminder note to do something for our next meeting, etc...
#2- then another pain, is that spaces and the doc don't seem quite so friendly to each other. in 10.4, i used to use a shareware program called "desktop manager". it had it's limitations, but also some improvements over spaces... for example, if i had a window minimized to the doc and i clicked on it, the window would open into whatever space i'm working in. in spaces, unfortunately, when i click on a minimized window, spaces transfers to whatever space that window was last open in and displays the window there. then i have to transfer the window back to the space i was working in. when all this is going on with an overhead projector thrown in, it is horribly confusing... and i've been doing it a couple months... with side-by-side displays, then the projector is swiping back and forth while my internal display is swiping back and forth. and it really confuses people, including me...
i know, it's again time for more "apple feedback"... but i'm blowing off a little steam since the feedback won't change anything for a long time (maybe the next os at best)...
my feedback suggestion that i sent to apple when i first ran into this is to integrate "spaces" and "display" so that when spaces is running and the side-by-side display option is selected for an external projector/monitor, just make the external projector appear as another "space" in spaces, and let the user "set" one of the spaces to be the external projector. then use the standard "spaces" interface handle all the screen manipulation and transfers.
what i'm learning to make this work better is close all programs and windows i don't need before dealing with a projector to make it as simple as possible and minimize all the autoswitching that can happen with spaces and programs... it is also helpful to restart, because sometimes spaces has behaved a little strangely when everything has been running a long time (weeks of putting the computer to sleep but no restarts)...
i did stumble across something nice that i hadn't realized about spaces until i stumbled across it by accident... if i click on a program in the doc with windows open in more than one space, spaces cycles thru each space with an open window for that program and skips the spaces that don't have any windows for that program. i normally use 4 spaces. (3 spaces are dedicated to specific tasks and projects. the forth is for spill over for anything else) so if i have email messages open in 2 of the 4 spaces, spaces only toggles between the 2 spaces when i cycle thru the windows by clicking on the mail program icon in the doc... very nice... the down side to this however is that if i want to open a window in a space with a running program that doesn't already have a window open in this space, it transfers me to the other space then i have to transfer the window back to the space i want. some programs have an option from the pop-up window from the doc to open a new window which opens it in the space i'm working in. but others, like mail, doesn't work this way. when replying to a message in mail will often make spaces transfer to another window and hide the reply window behind another window. obviously a bug...
well, see ya around-sorry, been away for a while...
for me, many years ago, when computers couldn't run many programs simultaneously, multiple workspaces was not very important. but today, the computers are capable of running so many programs and having so many windows upon simultaneously that the functionality of spaces is needed in many circumstances... just my opinion...
actually i used "desktop manager" in 10.4 for a couple years before spaces... there was another program too, that i could never get to work. since i've had so many tasks going on at the same time on my computer, desktop manager became a utility i couldn't live without on my work computer. home is simple, so don't need spaces in that environment... "desktop manager" had it's quirks which made me long to move to spaces when 10.5 came out... in my opinion spaces fixes some things that desktop manager didn't/couldn't hand well (largely since desktop manager was a "patch" to the windowing system). but spaces does need some improvement...
around the 1990 timeframe, i was running a heterogeneous network with many suns, macs, windows, x-windows, etc... SunOS had a feature it called "common desktop environment" which included "spaces" functionality. it work very well and behaved quite predictably, as i recall (it was a long time ago now)... i recall it was simpler, and didn't let you assign a program to a particular space. you just selected the space you wanted to work in then started the program... i think the extra bells and whistles of spaces trying to manage things across the workspaces is where "spaces" is trying to do a lot more and doesn't yet have all the kinks worked out...
my biggest problem is when i'm using an external projector. otherwise spaces other quirks tolerable, thought less than ideal... i completely agree that would rather not have a whole application assigned to a space, but instead have finer granularity, like you suggest to assign particular files to a workspace... although i wish spaces were better, given that this is apple's 1st attempt, i think it is understandable that spaces is not perfect and needs better optimization. however, i do hope that spaces gets some polishing because it does need it, IMHO... i only hope that apple has the resources needed to address all this issues it has between the mac HW, mac SW, iPods, iPhones, it's web business, etc... in it's history, apple has allowed some of it's technology die on the vine... (newton anyone??) it has it's hands full with the iPhone issues as well as 10.5 issues... so it may take a while before we see some progress...
anyway, just my opinion...
thanks for your message- -
I have encountered several regions while using Logic that won't let me resize them. It will let me resize them to a certain point (let's say I am grabbing the beginning of the region) and then no matter how far I move the beginning of the region to the right its length simply won't change. It's driving me crazy. As I move the pointer to the top left of the region it changes to the resize tool. It will allow me to grab and drag but when I let go of the mouse there is no change to the length of the region.
The region I'm working with currently that has this problem is about 8 measures long, so I know that I'm not trying to make it "too short" or something like that. I'm hoping the solution is just something simple that I'm missing. Thanks in advance.Sonther - yes I was referring to the start point only.
Samuel - there is a fundamental difference between audio regions and MIDI regions.
Audio regions are simply a "window" onto a larger entity - the audio file itself.
MIDI regions are not windows onto some other data type, they actually contain the MIDI events themselves, therefore they have to be able to encompass the events they contain.
Now, you can reduce the length, because internally Logic has a "length" value. Therefore a region can contain events lasting 8 bars but can have a display in the arrange of 2 bars. However, you can't have events before the start of a region, because Logic doesn't differentiate a "MIDI data starts here for this region" value and a "display the region starting here" value.
It's just the way Logic is currently programmed.
That is why events can go on for longer than the region displays, but not be placed before the region starts. -
How to resize the Region's width
Dear all,
i am using apex 4.2.2 , oracle database 11g R2, internet explorer 9.
i have created a region in HOME Tab for navigation menu.
but its width is covering the width of whole page.
how could i resize the width of the navigation region?
Thank you so much.Hi Maahjoor ,
you can set height with same code,
just check with the different style properties
in Region attributes put the below code.
style="width:300px;height:200px;"
Regards,
Jitendra -
Unable to allocate memory for mutex; resize mutex region
I have BDB on linux. I am trying to run my app, but I am getting this when it tries to set up the environment. Do I need to set any environment variable or something?
Here is my setting.
<property name="allowCreate" value="true"/>
<property name="cacheSize" value="65535000"/>
<property name="cacheCount" value="30"/>
<property name="initializeCache" value="true"/>
<property name="initializeLocking" value="true"/>
<property name="transactional" value="true"/>
Thanks.
------------- Standard Error -----------------
unable to allocate memory for mutex; resize mutex region
Testcase: testRunService took 1.842 sec
Caused an ERROR
Cannot allocate memory
java.lang.OutOfMemoryError: Cannot allocate memory
at com.sleepycat.db.internal.db_javaJNI.DbEnv_open(Native Method)
at com.sleepycat.db.internal.DbEnv.open(DbEnv.java:262)
at com.sleepycat.db.EnvironmentConfig.openEnvironment(EnvironmentConfig.java:908)
at com.sleepycat.db.Environment.<init>(Environment.java:30)
Edited by: user635741 on Oct 23, 2008 9:19 AMHello,
Based on the error, unable to allocate memory for mutex; resize mutex region,
have you tried increasing the mutex region?
The documentation on the setMaxMutexes method is at:
http://www.oracle.com/technology/documentation/berkeley-db/db/java/com/sleepycat/db/EnvironmentConfig.html#setMaxMutexes(int)
You can run db_stat -x
to display the mutex subsystem statistics.
You'll see the information for statistics like:
Mutex region size
The number of region locks that required waiting (0%)
Mutex alignment
Mutex test-and-set spins
If that does not look to be the problem, just let me know.
Thanks,
Sandra -
Fluid grid template - editable region - resize not possible
Hi,
After quitting DW the first resizing problem was gone.
Now I saved the page as a template and inserted an editable region.
Then it wasn't possible anymore to recize the divs.
The lines are know yellow dotted.
Do I have to make editable regions in a different way?
See: http://www.ifacilityservices.nl/index.html
Thanks again.
CarlaHi Nancy,
Thanks voor your reply!
Is it now not possible anymore?
I deleted the editable regions, but it stays with the yellow lines.
Carla
Van: Nancy O. [email protected]
Verzonden: zaterdag 24 augustus 2013 21:59
Aan: Carla Leliveld
Onderwerp: fluid grid template - editable region - resize not possible
Re: fluid grid template - editable region - resize not possible
created by Nancy O. <http://forums.adobe.com/people/Nancy+O.> in Dreamweaver CC - View the full discussion <http://forums.adobe.com/message/5623512#5623512 -
How do I resize mutex regions....
I'm getting the following error, but can't figure out how to resize the region. Is this something I should set in DB_CONFIG?
MutexStats:
st_mutex_align=4
st_mutex_tas_spins=1
st_mutex_cnt=1346
st_mutex_free=9
st_mutex_inuse=1337
st_mutex_inuse_max=1346
st_region_wait=0
st_region_nowait=17142
st_regsize=73728
com.sleepycat.dbxml.XmlException: Error: Not enough space, errcode = DATABASE_ERROR
about to delete manager
XmlManager closed
unable to allocate memory for mutex; resize mutex regionHi,
Using the search box (left column on the forum page) would be a nice thing to try before posting the question. Using that feature, you can find threads like these:
How to set the size of mutex region?
Re: Error message "Not Enough Space"
Re: Problem: unable to allocate memory for mutex; resize mutex region
The same question was addressed in the threads above.
If you are still having problems in allocating a bigger number of mutexes, just let me know.
Bogdan Coman
Maybe you are looking for
-
How do I sync my iPhoto library on my mac to my iPad
How do I sync photos from my Iphoto library to my iPad 2? Any help would be great!
-
Extracting audio from many clips at a time
I have to extract some audio from many many video clips, so I was attempting to do it in one step, but Logic extract only from one clip at a time So I'm thinking to use Audio Converter (it can extract audio from many clips in one step), but it ask m
-
CC Premiere Pro keeps failing on installation
I just received a Brand New iMac at work and I am trying to install CC applications, but premiere and after effects keep failing on installation. When i click More Details, it just tells me to try again in a few seconds. What am I supposed to do?
-
This new itunes is not syncing properly...
When I change or edit the names of songs/ albums, it doesn't sync to my iPhone5 even tho it says it is. This new itunes *****!! These are all purchased songs through iTunes. Not downloaded..... Ive done this in the past MANY times before i stupidly u
-
Hi all, i want to know the main advantage of ASO in essbase,why we are using ASO,i heared mainly from ASO cube we will get the reports ,could you please give some clarity on this . Regards Ravi