V. 2.2.1.00.04 Possible minor bug with breadcrumbs

Hello,
I have 'ORA-06502: PL/SQL: numeric or value error: character string buffer too small' error in Breadcrumbs section of Page Definition page when total length of breadcrumb string is more than 84 chars

Edward,
Thanks, this seems to work okay in 3.0. You can check it on apex.oracle.com, if you like.
Scott

Similar Messages

Possible minor bug when selecting inverse with OpenGL enabled

When I make a selection (like a rectangle selection in the middle of the canvas) and then inverse it (Shift-Command-I), the marching ants only appear on the right and bottom of the canvas. This seems to occur only with OpenGL enabled. I haven't noticed any part of the layer missing or being affected by this when I cut/copy. Has anyone else noticed this?
Command-A or manually selecting the whole canvas results in marching ants on all sides.
Mac OS 10.5.6
CS4 11.0.1
2 GB RAM
256 MB VRAM

Thanks, hiding/revealing doesn't seem to change it, but changing the screen mode definitely does. It only seems to be a problem with a floating window (meaning that if I start with the floating window and hit F three times, it doesn't "refresh" to display the missing ants).

Possible strange bug with parallel loops in LV2010

I have a specific code which does not execute correctly in parallel, but making almost any small change to the code causes it to work. Even more bizarre, I can change it so that it sometimes works correctly, and somtimes doesn't. Interested? Read on...
I have a relatively simple VI (to compute 2D Wavelet Denoising on planes of a 3D array) with the following block diagram (debugging not allowed):
The parallel loop is set to 8 automatically-partitioned instances, and I've tested this on 2-core and 8-core machines. When the #cores wired into the loop is not one, several of the iterations do not compute (for example 4 out of 24). I can check this by putting a break in the VI called inside the loop and counting how many times it is called.
I can do a number of things to make all iterations run:
- put an indicator inside the loop on the iteration number, or anything else (except the P node)
- wire the iteration number outside the loop to an indicator
- remove the case structure
- remove the loop in the other case (it's at the moment identical except for a call to a different VI which uses Discrete WT instead of Undecimated WT -- if I change the other case to match this one, the other case runs fine but this one still fails)
- change code outside the loop
- turn on debugging!
- change the loop setup to another number of instances other than 8
- change the loop setup to set the number of partitions
I can also do a number of things that do not solve the problem:
- rewriting the loop from scratch
- copying the loop from the other case
- saving for LV2009 (in which everything runs as expected) and then reloading (and presumably recompiling) in 2010
Stranger still, if I replace the called VI with a dummy VI (which simply adds one to the input 2D array so I can tell if it executes), then as long as the other wires are still wired in, it sometimes executes all iterations, and sometimes doesn't (roughly 50% split)!!! Any other changes and it always works fine.
I've managed to replace as much as possible with dummy code and still keep the results the same (i.e. sometimes executing all iterations and sometimes not).
If you want to check it out (on a multicore machine with LV2010), run LoopTest.vi, and the results at the index shown should sometimes be 13 and sometimes 14. Changing #cores to 1 will always give a result of 14, changing WT to DWT always gives 14, even though the code inside both cases is identical!
Hope it's not just me, otherwise I'll be sure that LV hates me!
Attachments:
LoopTest.zip ‏355 KB

OK, here's a new version that exhibits the same behaviour, but is hopefully simpler to understand.
The expected result is to add one to the whole array, however sometimes not all of the parallel iterations are executed. Run ParallelLoopTest.vi from the attached ZIP file on a multi-core machine to verify. This screenshot shows that sometimes it works correctly, and sometimes not:
The code in the other case is identical (created by duplicating the case) but always works correctly.
Attachments:
ParallelLoopTest.zip ‏63 KB

Minor bug with Connections node in SQL Dev. 2.1 EA1

This is minor compared to some of the other issues found with EA1.
When I expand the Connections node by clicking on the "+" I cannot collapse it when clicking on the "-". This happens both when migrating settings from 1.5.5 and when starting clean without migrating settings and then creating new connections. (I deleted the "system2.1.0.62.61" folder between tests.) I tried this by running "+<install_dir>+\sqldeveloper\sqldeveloper.exe" and "+<install_dir>+\sqldeveloper\sqldeveloper\bin\sqldeveloper.exe" to get a console window. (The only messages I saw in the console window occurred when I opened a connection.)
Here are the "About" and "Version" info:
About
Oracle SQL Developer 2.1.0.62
Version 2.1.0.62
Build MAIN-62.61
Copyright © 2005,2009 Oracle. All Rights Reserved.
IDE Version: 11.1.1.2.36.54.96
Product ID: oracle.sqldeveloper
Product Version: 11.1.1.62.61
Version
Component Version
========= =======
Java(TM) Platform 1.6.0_14
Oracle IDE 2.1.0.62.61
Versioning Support 2.1.0.62.61
FWIW, I can collapse and expand the Connections node in 1.5.5 without any problem.
Ed. H.

Thanks the bug is that the +/- is even being shown. I put something in there to prevent the collapsing of that since there's nothing when it's collapse.
-kris

A minor bug with Application Bulider menu in 2.2.1

I have two apex instances which are used primarily for development and periodicaly synchronized via application exports. After some time of such activity I lost my application in the application builder menu on the first instance (still have access to the application by clicking Application Builder icon and choosing from the application list). On the second instance I lost section with Export, Import submenus inside this menu. Now just see two separators sticked together without these items between them.

Edward,
I lost my application in the application builder menuI'm not exactly sure what you mean. If you mean the history of the most recently edited applications that you see at the bottom of the Application Builder drop-down list (zero to four application IDs and names), this history will be nullified for applications that you import as the import action clears the audit trail.
About the Export menus, I don't know what you mean, maybe you could post a screenshot.
Scott

Possible iPhone bug with custom recurring day schedule? Need help.

In Microsoft Outlook I have a 64 day schedule that is set up as single all day recurring events each day. Each day of the 64 day schedule recurrs every 64 days. Day 1 recurrs every 64 days, day 2 recurrs every 64 days, etc., etc.
When I synced this to an iPhone, each day had an incorrect custom recurring day set at every 18 days. This, of course threw off the whole schedule. After doing some testing, I found out that a custom recurr of 45 days worked, a custom recurr of 46 days told the iPhone it recurred every 1 day. 47 day recurr did the same thing. 48 day recurr told the iPhone it recurred every 2 days, 49 day recurr became 3 days, 50 became 4 days, 51 became 5 days...64 became 18 days.
Is this indeed a bug with iPhone or is there something I can do for a single 1 day event recurr every 64 days? And, why is there no custom setting when setting up an event on the iPhone?

ICKIER wrote:
Is this too complicated for a reply?!
Apparently, no one has a solution for you. It may be a bona fide bug. You can let Apple know about that:
http://www.apple.com/feedback/iphone.html.

NI DC Soft Front Panel, minorbug, minor bug with PXI-4110

Hi
The NI DC Soft Front Panel V14.0, with the PXI-4110, the negative voltage scroll, works as expected to -10V, but then rolls over to 0. If one changes in -1V steps, it goes.... -8, -9, -10, -1, -2 ..... instead of -8, -9, -10, -11, -12 ...
While at it, a simple thing I miss is a on/off button for all three voltages.
(Also, imo, it would be logical to get negative voltages with the down arrow, not up).
My 2C
Solved!
Go to Solution.

Hello Janaf,
I fully agree with both of your statements, I have filed a Correction Action Report which you can monitor in next releases of DCPower to see if this is fixed with the SFP. Number of CAR: 512257
I added notes that only manual insertion of numbers less than -10 works and that it was not logical to use increment arrow or up arrow to decrease the voltage output.
Best Regards
Jonas Mäki
Applications Engineering
National Instruments

Minor bug with editing when there are multiple pages of reports on the list

When I edit a report and save the changes, I am returned to a different page on the list of reports than I started from.
Steps to reproduce:
1. Sort reports by Type
2. On the first page on the list of reports, find a custom report I created
3. click Edit, then click Save
4. I am returned to page 2 of the reports instead of page 1.
5. If I click Cancel instead of Save, I'm returned to page 1 as expected.
Depending on which page I started from I may be returned to some other seemingly random page, i.e. starting from page 4 I might be returned to page 3.
Expected behavior - it should either return me to the first page, or else return me to the page I started from.
This topic first appeared in the Spiceworks Community

Make sure your logo is not overlapped with any window... and i guess, your smartform has two page formats...
Identify the next page attribute of you first page and do the amendments as stated above.
Regards,
SaiRam

Cluster VI Reference Minor Bug

Over on LAVA PJM_labview posted a video of a bug found in LabVIEW 2013 SP1. It is a minor bug with the block diagram when showing a cluster constant with a VI reference constant in it. Here is the video of how to reproduce the bug.
http://screencast.com/t/gfKwlvMcCsHI
And here is the original thread on LAVA.
http://lavag.org/topic/18297-cool-little-lv-2013-sp1-bug/#entry109757
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

I played with this and filed it as a CAR (#479432). Intriguingly, there are a couple workarounds:
Option 1
On block diagram:
1. Create cluster constant containing refnum with auto-sizing set as arranged (vertical or horizontal)
2. Create typedef
3. Unlink from type def
4. Change auto-sizing to desired value
5. Recreate typedef
Option 2
On front panel:
1. Create cluster containing refnum control
2. Create typedef
On block diagram:
3. Create constant from cluster typedef on block diagram.
4. Unlink constant from typedef, change auto-sizing as desired, recreate typedef
Christopher S. | Applications Engineer
Certified LabVIEW Developer
"If in doubt... flat out." - Colin McRae

Possible Keyword Bug

Okay,
I think I have found a possible bug with keywords, or maybe just an incositancy. It's kind of a messy situation so I'm hoping someone can help me out or maybe point me in the right direction to send this feedback to Apple.
I had a bunch of jpeg files from my older cameras that had already been tagged with keywords (in the IPTC keyword field I believe). Once I imported all of these into Aperture I stripped the keywords from all the images. That worked fine.
Before I get into the actual issue let me give a little bit of information on my Aperture library layout: I have folders created by year, then 1 project per month. So I have something like this:
2002
01 Janurary
02 Feburary
2003
01 Janurary
What's weird is if I create a new smart album at the folder level, the keywords listed in the search box are appropriate (only those actually added to images). However if I click on Library and create a new smart album (so that it searches the whole library) it lists all of my current keywords, plus all of those that I had removed (from the original files).
Anyone else run across this? Anyone know how to fix it? It's just a minor inconvience, but it does make it a bit of a pain to have a whole ton of keywords to select from in the search box (most of them no longer having any images associated with them).
Also I have searched for images that match the old keywords and it doesn't find any.
Thanks,
Mark

She suggests..
"Go to Window > Show Keywords HUD, and see if they are there. If so, you should be able to delete them from there."
Hopefully, they will then disappear from the Library list.
if not, it does seem like a bug.
Message was edited by: notorious

Help, experiencing minor bugs in program

this is supposed to use rectangles and you should be able to load and save and they have colors and do a few more things with them, the loading is where it doesn't work.
*-------------------------------------------------------------- 80 columns ---|
* This is the main class for the application. It is built along the same
* lines as the Editor class of project 1. It has a constructor, two instance
* methods, and a static main() that kicks the whole thing off.
* The two instance methods are a menu creation method, and a menuItems
* initialisation method. The constructor instantiates the window
* and sets up its internals by creating and installing the drawing canvas,
* toolbar, and menus. All of the code works correctly as is and should
* require no changes.
* @version 1.1 15/04/01
* @author Julie Zelenski
* @author Restructured by Ian A. Mason
* @see javax.swing.JFrame
* @see javax.swing.JMenuBar
* @see javax.swing.JMenuItem
* @see javax.swing.JMenu
import java.awt.*;
import javax.swing.*;
import java.awt.event.*;
public class JavaDraw extends JFrame {
 final Toolbar toolbar = new Toolbar();
 final DrawingCanvas canvas = new DrawingCanvas(toolbar, 350, 350);
 final int menuMask = Toolkit.getDefaultToolkit().getMenuShortcutKeyMask();
 final JMenuBar mb = new JMenuBar();
 final String[]
 fileMenuItems = {"Clear all", "Load file", "Save to file", "Quit"};
 final int[] fileKeyCodes = {KeyEvent.VK_N, KeyEvent.VK_O, KeyEvent.VK_S, KeyEvent.VK_Q};
 final ActionListener[] fileActionListeners = {
 new ActionListener() {
 public void actionPerformed(ActionEvent e) {
 canvas.clearAll();}},
 new ActionListener() {
 public void actionPerformed(ActionEvent e) {
 canvas.loadFile();}},
 new ActionListener() {
 public void actionPerformed(ActionEvent e) {
 canvas.saveToFile();}},
 new ActionListener() {
 public void actionPerformed(ActionEvent e) {
 System.exit(0);}}
 final String[] editMenuItems = {"Cut", "Copy", "Paste", "Delete"};
 final int[] editKeyCodes = {KeyEvent.VK_X, KeyEvent.VK_C, KeyEvent.VK_V, KeyEvent.VK_BACK_SPACE};
 final int[] editMenuMasks = {menuMask, menuMask, menuMask, 0};
 final ActionListener[] editActionListeners = {
 new ActionListener() {
 public void actionPerformed(ActionEvent e) { canvas.cut();}},
 new ActionListener() {
 public void actionPerformed(ActionEvent e) { canvas.copy();}},
 new ActionListener() {
 public void actionPerformed(ActionEvent e) { canvas.paste();}},
 new ActionListener() {
 public void actionPerformed(ActionEvent e) { canvas.delete();}}
 final String[] layeringMenuItems = {"Bring to front", "Send to back"};
 final int[] layeringKeyCodes = {KeyEvent.VK_F, KeyEvent.VK_B};
 final ActionListener[] layeringActionListeners = {
 new ActionListener() {
 public void actionPerformed(ActionEvent e) {
 canvas.bringToFront();}},
 new ActionListener() {
 public void actionPerformed(ActionEvent e) {
 canvas.sendToBack();}}
 private JavaDraw(){
 super("JavaDraw!");
 toolbar.setCanvas(canvas);
 getContentPane().add(toolbar, BorderLayout.SOUTH);
 getContentPane().add(canvas, BorderLayout.CENTER);
 createMenus();
 setJMenuBar(mb);
 setLocation(100, 20);
 pack();
 setVisible(true);
 static public void main(String[] args){
 JavaDraw javaDraw = new JavaDraw();
 private void initMenus(JMenu m,
 String miLabel,
 int keyCode,
 int menuMask,
 ActionListener al){
 JMenuItem mi = new JMenuItem(miLabel);
 m.add(mi);
 mi.addActionListener(al);
 mi.setAccelerator(KeyStroke.getKeyStroke(keyCode, menuMask));
 private void createMenus(){
 JMenu m;
 m = new JMenu("File");
 for(int i = 0; i < fileMenuItems.length; i++)
 initMenus(m,
 fileMenuItems,
 fileKeyCodes[i],
 menuMask,
 fileActionListeners[i]);
 mb.add(m);
 m = new JMenu("Edit");
 for(int i = 0; i < editMenuItems.length; i++)
 initMenus(m,
 editMenuItems[i],
 editKeyCodes[i],
 editMenuMasks[i],
 editActionListeners[i]);
 mb.add(m);
 m = new JMenu("Layering");
 for(int i = 0; i < layeringMenuItems.length; i++)
 initMenus(m,
 layeringMenuItems[i],
 layeringKeyCodes[i],
 menuMask,
 layeringActionListeners[i]);
 mb.add(m);
*-------------------------------------------------------------- 80 columns ---|
* The DrawingCanvas class a small extension of JComponent
* @version 1.1 15/04/01
* @author Julie Zelenski
* @author (touched up by Ian A. Mason)
* @see javax.swing.JComponent
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import javax.swing.event.*;
import java.util.*;
public class DrawingCanvas extends JComponent{
static final int DRAG_NONE = 0;
static final int DRAG_CREATE = 1;
static final int DRAG_RESIZE = 2;
static final int DRAG_MOVE = 3;
// list of all shapes on canvas
protected Vector allShapes;
// currently selected shape (can be null at times)
protected Rect selectedShape;
// reference to toolbar to message for tool&color settings
protected Toolbar toolbar;
protected Rect clipboard=null;
/* These are the unimplemented menu commands. The menus are already
* set up to send the correct messages to the canvas, but the
* method bodies themselves are currently completely empty. It will
* be your job to fill them in!
public void cut() {
 copy();
 delete();
public void copy() {
 int x=(int)selectedShape.getBounds().getX();
 int y=(int)selectedShape.getBounds().getY();
 Point p=new Point(x,y);
 clipboard=new Rect(p,this);
 clipboard.setBounds(selectedShape.getBounds());
public void paste() {
 if(clipboard==null)
 return;
 allShapes.add(clipboard);
 setSelectedShape(clipboard);
 copy();
 this.repaint();
public void delete() {
 if(selectedShape==null)
 return;
 else{
 int num=allShapes.indexOf(selectedShape);
 allShapes.remove(num);
 selectedShape=null;
 this.repaint();
public void clearAll() {
 allShapes.removeAllElements();
 this.repaint();
public void loadFile() {
 Load load=new Load(this);
 load.setSize(250,200);
 load.validate();
 load.setVisible(true);
public void done(Vector vect){
 allShapes.removeAllElements();
 for(int i=0;i<vect.size();i++){
 allShapes.add(vect.elementAt(i));
 this.repaint();
public void saveToFile() {
 Save save=new Save(allShapes);
 save.setSize(250,200);
 save.validate();
 save.setVisible(true);
public void bringToFront() {
 if(selectedShape==null)
 return;
 int size=allShapes.size();
 int index=allShapes.indexOf(selectedShape);
 for(int i=index+1;i<=size-1;i++){
 allShapes.set(i-1,allShapes.elementAt(i));
 allShapes.set(size-1,selectedShape);
 this.repaint();
public void sendToBack() {
 if(selectedShape==null)
 return;
 int index=allShapes.indexOf(selectedShape);
 for(int i=index-1;i>=0;i--){
 allShapes.remove(allShapes.elementAt(i+1));
 allShapes.add(i+1,allShapes.elementAt(i));
 allShapes.remove(allShapes.elementAt(0));
 allShapes.add(0,selectedShape);
 this.repaint();
* Constructor for creating a new empty DrawingCanvas. We set up
* our size and background colors, instantiate an empty vector of shapes,
* and install a listener for mouse events using our inner class
* CanvasMouseHandler
public DrawingCanvas(Toolbar tb, int width, int height){
 setPreferredSize(new Dimension(width, height));
 setBackground(Color.white);
 toolbar = tb;
 allShapes = new Vector();
 selectedShape = null;
 CanvasMouseHandler handler = new CanvasMouseHandler();
 addMouseListener(handler);
 addMouseMotionListener(handler);
* All components are responsible for drawing themselves in
* response to repaint() requests. The standard method a component
* overrides is paint(Graphics g), but for Swing components, the default
* paint() handler calls paintBorder(), paintComponent() and paintChildren()
* For a Swing component, you override paintComponent and do your
* drawing in that method. For the drawing canvas, we want to
* clear the background, then iterate through our shapes asking each
* to draw. The Graphics object is clipped to the region to update
* and we use to that avoid needlessly redrawing shapes outside the
* update region.
public void paintComponent(Graphics g){
 Rectangle regionToRedraw = g.getClipBounds();
 g.setColor(getBackground());
 g.fillRect(regionToRedraw.x, regionToRedraw.y,
 regionToRedraw.width, regionToRedraw.height);
 Iterator iter = allShapes.iterator();
 while (iter.hasNext())
 ((Rect)iter.next()).draw(g, regionToRedraw);
* Changes the currently selected shape. There is at most
* one shape selected at a time on the canvas. It is possible
* for the selected shape to be null. Messages the shape to
* change its selected state which will in turn refresh the
* shape with the knobs active.
protected void setSelectedShape(Rect shapeToSelect) {
 // if change in selection
 if (selectedShape != shapeToSelect) {
 // deselect previous selection
 if (selectedShape != null)
 selectedShape.setSelected(false);
 // set selection to new shape
 selectedShape = shapeToSelect;
 if (selectedShape != null) {
 shapeToSelect.setSelected(true);
* A hit-test routine which finds the topmost shape underneath a
* given point.We search Vector of shapes in back-to-front order
* since shapes created later are added to end and drawn last, thus
* appearing to be "on top" of the earlier ones. When a click comes
* in, we want to select the top-most shape.
protected Rect shapeContainingPoint(Point pt){
 for (int i = allShapes.size()-1; i >= 0; i--) {
 Rect r = (Rect)allShapes.elementAt(i);
 if (r.inside(pt)) return r;
 return null;
* The inner class CanvasMouseHandler is the object that handles the
* mouse actions (press, drag, release) over the canvas. Since there is
* a bit of state to drag during the various operations (which shape,
* where we started from, etc.) it is convenient to encapsulate all that
* state with this little convenience object and register it as the
* handler for mouse events on the canvas.
protected class CanvasMouseHandler
 extends MouseAdapter implements MouseMotionListener {
 Point dragAnchor;
 // variables using to track state during drag operations
 int dragStatus;
 /** When the mouse is pressed we need to figure out what
 * action to take. If the tool mode is arrow, the click might
 * be a select, move or reisze. If the tool mode is one of the
 * shapes, the click initiates creation of a new shape.
 public void mousePressed(MouseEvent event){
 Rect clicked = null;
 Point curPt = event.getPoint();
 // first, determine if click was on resize knob of selected shape
 if (toolbar.getCurrentTool() == Toolbar.SELECT) {
 if (selectedShape != null &&
 (dragAnchor = selectedShape.getAnchorForResize(curPt))
 != null) {
 // drag will resize this shape
 dragStatus = DRAG_RESIZE;
 } else if ((clicked = shapeContainingPoint(curPt)) != null) {
 // if not, check if any shape was clicked
 setSelectedShape(clicked);
 // drag will move this shape
 dragStatus = DRAG_MOVE;
 dragAnchor = curPt;
 } else {
 // else this was a click in empty area,
 // deselect selected shape,
 setSelectedShape(null);
 // drag does nothing in this case
 dragStatus = DRAG_NONE;
 } else {
 Rect newShape = new Rect(curPt, DrawingCanvas.this);
 // create rect here
 allShapes.add(newShape);
 setSelectedShape(newShape);
 dragStatus = DRAG_CREATE;
 // drag will create (resize) this shape
 dragAnchor = curPt;
 /** As the mouse is dragged, our listener will receive periodic
 * updates as mouseDragged events. When we get an update position,
 * we update the move/resize event that is in progress.
 public void mouseDragged(MouseEvent event){
 Point curPt = event.getPoint();
 switch (dragStatus) {
 case DRAG_MOVE:
 selectedShape.translate(curPt.x - dragAnchor.x,
 curPt.y - dragAnchor.y);
 // update for next dragged event
 dragAnchor = curPt;
 break;
 case DRAG_CREATE: case DRAG_RESIZE:
 selectedShape.resize(dragAnchor, curPt);
 break;
 public void mouseMoved(MouseEvent e) {}
/** A little helper routine that will be useful for the load & save
* operations. It brings up the standard JFileChooser dialog and
* allows the user to specify a file to open or save. The return
* value is the full path to the chosen file or null if no file was
* selected.
protected String filenameChosenByUser(boolean forOpen){
 JFileChooser fc = new JFileChooser(System.getProperty("user.dir") +
 java.io.File.separator + "Documents");
 int result = (forOpen? (fc.showOpenDialog(this)) :
 fc.showSaveDialog(this));
 java.io.File chosenFile = fc.getSelectedFile();
 if (result == JFileChooser.APPROVE_OPTION && chosenFile != null)
 return chosenFile.getPath();
 return null;
 // return null if no file chosen or dialog cancelled
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
import java.util.Vector;
import java.io.*;
class Load extends JFrame implements ActionListener, Serializable{
 Container contentPane;
 JTextField jtf;
 JButton jb;
 Object obj=null;
 Load load;
 Thread thread;
 DrawingCanvas draw;
 public Load(DrawingCanvas dc){
 draw=dc;
 contentPane=getContentPane();
 contentPane.setLayout(new FlowLayout());
 jtf=new JTextField(20);
 jb=new JButton("Load");
 jb.addActionListener(this);
 contentPane.add(jtf);
 contentPane.add(jb);
 public void actionPerformed(ActionEvent e){
 String text=jtf.getText();
 SimpleObjectReader reader=SimpleObjectReader.openFileForReading(text+".shp");
 if(reader==null){
 System.out.println("Couldn't open file!");
 return;
 obj=reader.readObject();
 reader.close();
 draw.done((Vector)obj);
 this.setVisible(false);
import javax.swing.*;
import java.awt.event.*;
import java.awt.*;
import java.util.Vector;
import java.io.*;
class Save extends JFrame implements ActionListener, Serializable{
 Container contentPane;
 JTextField jtf;
 Vector shapes;
 JButton jb;
 public Save(Vector shapeVector){
 shapes=shapeVector;
 contentPane=getContentPane();
 contentPane.setLayout(new FlowLayout());
 jtf=new JTextField(20);
 jb=new JButton("Save");
 jb.addActionListener(this);
 contentPane.add(jtf);
 contentPane.add(jb);
 public void actionPerformed(ActionEvent e){
 String text=jtf.getText();
 SimpleObjectWriter writer=SimpleObjectWriter.openFileForWriting(text+".shp");
 if(writer==null){
 System.out.println("Couldn't open file!");
 return;
 writer.writeObject(shapes);
 writer.close();
 this.setVisible(false);
*-------------------------------------------------------------- 80 columns ---|
* The RectShape class defines a simple rectangular shape object.
* It tracks its bounding box, selected state, and the canvas it is being
* drawn in. It has some basic methods to select, move, and resize the
* rectangle. It has methods that draw the shape in the selected or unselected
* states and updates the canvas whenever the state or bounds of the rectangle
* change. The code that is there works properly, but you will need to extend
* and change the code to support additional features.
* @version 1.1 15/04/01
* @author Julie Zelenski
* @author (touched up by Ian A. Mason)
import java.awt.*;
import java.io.*;
public class Rect implements Serializable{
protected Rectangle bounds;
protected boolean isSelected;
public Color color;
public DrawingCanvas canvas;
protected static final int KNOB_SIZE = 6;
protected static final int NONE = -1;
protected static final int NW = 0;
protected static final int SW = 1;
protected static final int SE = 2;
protected static final int NE = 3;
/** The constructor that creates a new zero width and height rectangle
* at the given position in the canvas.
public Rect(Point start, DrawingCanvas dcanvas){
 canvas = dcanvas;
 bounds = new Rectangle(start);
 color=canvas.toolbar.getCurrentColor();
/** The "primitive" for all resizing/moving/creating operations that
* affect the rect bounding box. The current implementation just resets
* the bounds variable and triggers a re-draw of the union of the old &
* new rectangles. This will redraw the shape in new size and place and
* also "erase" if bounds are now smaller than before. It is a good
* design to have all changes to a critical variable bottleneck through
* one method so that you can be sure that all the updating that goes
* with it only needs to be implemented in this one place. If any of your
* subclasses have additional work to do when the bounds change, this is
* the method to override. Make sure that any methods that change the
* bounds call this method instead of directly manipulating the variable.
protected void setBounds(Rectangle newBounds){
 Rectangle oldBounds = bounds;
 bounds = newBounds;
 updateCanvas(oldBounds.union(bounds));
/** The resize operation is called when first creating a rect, as well as
* when later resizing by dragging one of its knobs. The two parameters
* are the points that define the new bounding box. The anchor point
* is the location of the mouse-down event during a creation operation
* or the opposite corner of the knob being dragged during a resize
* operation. The end is the current location of the mouse. If you
* create the smallest rectangle which encloses these two points, you
* will have the new bounding box. Use the setBounds() primitive which
* is the bottleneck we are using for all geometry changes, it handles
* updating and redrawing.
public void resize(Point anchor, Point end){
 Rectangle newRect = new Rectangle(anchor);
 // creates smallest rectange which
 // includes both anchor & end
 newRect.add(end);
 // reset bounds & redraw affected areas
 setBounds(newRect);
public Rectangle getBounds(){
 return bounds;
/** The translate operation is called when moving a shape by dragging in
* the canvas. The two parameters are the delta-x and delta-y to move
* by. Note that either or both can be negative. Create a new rectangle
* from our bounds and translate and then go through the setBounds()
* primitive to change it.
public void translate(int dx, int dy){
 Rectangle newRect = new Rectangle(bounds);
 newRect.translate(dx, dy);
 setBounds(newRect);
/** Used to change the selected state of the shape which will require
* updating the affected area of the canvas to add/remove knobs.
public void setSelected(boolean newState){
 isSelected = newState;
 // need to erase/add knobs
 // including extent of extended bounds
 updateCanvas(bounds, true);
/** The updateCanvas() methods are used when the state has changed
* in such a way that it needs to be refreshed in the canvas to properly
* reflect the new settings. The shape should take responsibility for
* messaging the canvas to properly update itself. The appropriate AWT/JFC
* way to re-draw a component is to send it the repaint() method with the
* rectangle that needs refreshing. This will cause an update() event to
* be sent to the component which in turn will call paint(), where the
* real drawing implementation goes. See the paint() method in
* DrawingCanvas to see how it is implemented.
protected void updateCanvas(Rectangle areaOfChange, boolean enlargeForKnobs){
 Rectangle toRedraw = new Rectangle(areaOfChange);
 if (enlargeForKnobs)
 toRedraw.grow(KNOB_SIZE/2, KNOB_SIZE/2);
 canvas.repaint(toRedraw);
protected void updateCanvas(Rectangle areaOfChange){
 updateCanvas(areaOfChange, isSelected);
/** When the DrawingCanvas needs a shape to draw itself, it sends a draw
* message, passing the graphics context and the current region being
* redrawn. If the shape intersects with that region, it must draw itself
* doing whatever it takes to properly represent itself in the canvas
* (colors, location, size, knobs, etc.) by messaging the Graphics object.
public void draw(Graphics g, Rectangle regionToDraw){
 if (!bounds.intersects(regionToDraw))
 return;
 g.setColor(color);
 g.fillRect(bounds.x, bounds.y, bounds.width, bounds.height);
 if (isSelected) { // if selected, draw the resizing knobs
 // along the 4 corners
 Rectangle[] knobs = getKnobRects();
 for (int i = 0; i < knobs.length; i++)
 g.fillRect(knobs[i].x, knobs[i].y,
 knobs[i].width, knobs[i].height);
/** When the DrawingCanvas needs to determine which shape is under
* the mouse, it asks the shape to determine if a point is "inside".
* This method should returns true if the given point is inside the
* region for this shape. For a rectangle, any point within the
* bounding box is inside the shape.
public boolean inside(Point pt){
 return bounds.contains(pt);
/** When needed, we create the array of knob rectangles on demand. This
* does mean we create and discard the array and rectangles repeatedly.
* These are small objects, so perhaps it is not a big deal, but
* a valid alternative would be to store the array of knobs as an
* instance variable of the Shape and and update the knobs as the bounds
* change. This means a little more memory overhead for each Shape
* (since it is always storing the knobs, even when not being used) and
* having that redundant data opens up the possibility of bugs from
* getting out of synch (bounds move but knobs didn't, etc.) but you may
* find that a more appealing way to go. Either way is fine with us.
* Note this method provides a nice unified place for one override from
* a shape subclass to substitute fewer or different knobs.
protected Rectangle[] getKnobRects(){
 Rectangle[] knobs = new Rectangle[4];
 knobs[NW] = new Rectangle(bounds.x - KNOB_SIZE/2,
 bounds.y - KNOB_SIZE/2, KNOB_SIZE, KNOB_SIZE);
 knobs[SW] = new Rectangle(bounds.x - KNOB_SIZE/2,
 bounds.y + bounds.height - KNOB_SIZE/2,
 KNOB_SIZE, KNOB_SIZE);
 knobs[SE] = new Rectangle(bounds.x + bounds.width - KNOB_SIZE/2,
 bounds.y + bounds.height - KNOB_SIZE/2,
 KNOB_SIZE, KNOB_SIZE);
 knobs[NE] = new Rectangle(bounds.x + bounds.width - KNOB_SIZE/2,
 bounds.y - KNOB_SIZE/2,
 KNOB_SIZE, KNOB_SIZE);
 return knobs;
/** Helper method to determine if a point is within one of the resize
* corner knobs. If not selected, we have no resize knobs, so it can't
* have been a click on one. Otherwise, we calculate the knob rects and
* then check whether the point falls in one of them. The return value
* is one of NW, NE, SW, SE constants depending on which knob is found,
* or NONE if the click doesn't fall within any knob.
protected int getKnobContainingPoint(Point pt){
 // if we aren't selected, the knobs
 // aren't showing and thus there are no knobs to check
 if (!isSelected) return NONE;
 Rectangle[] knobs = getKnobRects();
 for (int i = 0; i < knobs.length; i++)
 if (knobs[i].contains(pt))
 return i;
 return NONE;
/** Method used by DrawingCanvas to determine if a mouse click is starting
* a resize event. In order for it to be a resize, the click must have
* been within one of the knob rects (checked by the helper method
* getKnobContainingPoint) and if so, we return the "anchor" ie the knob
* opposite this corner that will remain fixed as the user drags the
* resizing knob of the other corner around. During the drag actions of a
* resize, that fixed anchor point and the current mouse point will be
* passed to the resize method, which will reset the bounds in response
* to the movement. If the mouseLocation wasn't a click in a knob and
* thus not the beginning of a resize event, null is returned.
public Point getAnchorForResize(Point mouseLocation){
 int whichKnob = getKnobContainingPoint(mouseLocation);
 // no resize knob is at this location
 if (whichKnob == NONE)
 return null;
 switch (whichKnob) {
 case NW: return new Point(bounds.x + bounds.width,
 bounds.y + bounds.height);
 case NE: return new Point(bounds.x, bounds.y + bounds.height);
 case SW: return new Point(bounds.x + bounds.width, bounds.y);
 case SE: return new Point(bounds.x, bounds.y);
 return null;
import java.io.*;
* SimpleObjectReader is a small class to wrap around the usual ObjectStream
* to shield you from the exception handling which we haven't yet gotten
* to in class.
* It has just three methods of note: one to open a new file for reading,
* one to read an object from an open file, and one to close the file when done.
* Any object that you attempt to read must properly implement the Serializable
* interface. Here is a simple example that shows using the SimpleFileReader to
* to rehydrate objects from a file and print them:
* <PRE>
* SimpleObjectReader reader = SimpleObjectReader.openFileForReading("shapes");
* if (reader == null) {
* System.out.println("Couldn't open file!");
* return;
* Object obj;
* while ((obj = reader.readObject()) != null)
* System.out.println(obj);
* reader.close();
* </PRE>
* You are free to edit or extend this class, but we don't expect that
* you should need to make any changes.
* @version 1.1 15/04/01
* @author Julie Zelenski
* @author (touched up by Ian A. Mason)
public class SimpleObjectReader {
private ObjectInputStream ois;
* Opens a new file for reading. The filename can either be a relative
* path, which will be relative to the working directory of the program
* when started, or an absolute path. If the file exists and can be
* opened, a new SimpleObjectReader is returned. If the file cannot be
* opened (for any reason: wrong name, wrong path, lack of permissions, etc.)
* null is returned.
public static SimpleObjectReader openFileForReading(String filename){
 try {
 return new SimpleObjectReader(new ObjectInputStream(new FileInputStream(filename)));
 } catch(IOException e) {
 return null;
* Reads a single object from the file and returns it. If there are
* no more objects in the file (i.e, we have reached the end of file),
* null is returned null is returned. null is also
* returned on any I/O error.
public Object readObject (){
 try {
 return ois.readObject();
 } catch (IOException e) {
 e.printStackTrace();
 return null;
 } catch (ClassNotFoundException e) {
 e.printStackTrace();
 return null;
* Closes the file when done reading. You should close a reader when
* you are finished to release the OS resources for use by others.
public void close (){
 try {
 ois.close();
 catch (IOException e) {}
* Constructor is private so that only means to create a new reader
* is through the static method which does error checking.
private SimpleObjectReader(ObjectInputStream ois){
 this.ois = ois;
import java.io.*;
* SimpleObjectWriter is a small class to wrap around the usual
* ObjectOutputStream to shield you from the exception handling
* which we haven't yet gotten to in class.
* It has just three methods of note: one to open a new file for writing,
* one to write an object to the file, and one to close the
* the file when done.
* Here is a simple example that shows using the SimpleObjectWriter
* to create a new file and write some objects into it:
* <PRE>
* SimpleObjectWriter writer =
* SimpleObjectWriter.openFileForWriting("objects");
* if (writer == null) {
* System.out.println("Couldn't open file!");
* return;
* writer.writeObject("Here is a string");
* writer.writeObject("And another one.");
* writer.writeObject(new Date());
* writer.close();
* </PRE>
* You are free to edit or extend this class, but we don't expect that
* you should need to make any changes.
* @version 1.1 15/04/01
* @author Julie Zelenski
* @author (touched up by Ian A. Mason)
public class SimpleObjectWriter {
private ObjectOutputStream oos;
* Opens a new file for writing. The filename can either be a relative
* path, which will be relative to the working directory of the program
* when started, or an absolute path. If the file can be created, a
* new SimpleObjectWriter is returned. If the file already exists, this
* will overwrite its content

I'm not reading that either, but to help you for next time:
- use more than 1 sentence to describe your problem
- only post the RELEVANT code, or a small test program with the same problem if possible.
At least you formatted it, I'll give you that.
Cheers,
Radish21
PS. I think in this case, posting another (better worded) thread might be a good idea, because no one is going to read this one. In general though, don't :)

Is there a way to answer the 5c without swiping? It really is a pain and hard to do at times one handed. Maybe allow favorites to be answered with a click of the home button or possibly all calls with a home button push

Is there a way to answer the 5c without swiping? It really is a pain and hard to do at times one handed. Maybe allow favorites to be answered with a click of the home button or possibly all calls with a home button push. First smart phone I have owned and the old flip phone was much easier to answer.....just press one button.

Is there a way to answer the 5c without swiping? It really is a pain and hard to do at times one handed. Maybe allow favorites to be answered with a click of the home button or possibly all calls with a home button push. First smart phone I have owned and the old flip phone was much easier to answer.....just press one button.

Premiere Pro cc 2014 do not import After Effects composition. Inside Premiere Pro CC 2014 is not possible call back After Effects, is not possible to work with After Effects. Thank you

Premiere Pro cc 2014 do not import After Effects composition. Inside Premiere Pro CC 2014 is not possible call back After Effects, is not possible to work with After Effects. Thank you

You haven't given us much to go on here. What exactly are you doing and what exactly happens when you try? Which specific version of each program are you using? (Go to Help>About...)
On a side note, a simple, brief thread title is all that's needed. Something like "After Effects Issue" would be fine. You don't need the full question there.

F110 - credit note - No pymt possible because items with with a debit balance

Hi All,
we have credit note & invoice for same vendor. When doing payment run, below error message is coming.
No pymt possible because items with with a debit balance.
when we click on Reallocate & give payment method & house bank, below error mesage come:-
Enter a payment method for incoming payments
Message no. FZ010
Diagnosis
The balance of the items to be paid requires a payment method for incoming payments. You specified a payment method that is defined for outgoing payments.
System Response
The payment method is rejected.
Procedure
Enter a payment method for incoming payments.
Please advise.
Regards
Deepak

Hi Garg,
In this case, one of the option is that you can do the partial clearing or residual clearing, lets say Residual clearing, in this case system will clear the original items and open new item 700 as payable.
You can clear credit memo 1800 against two invoices 1500 and 1000, out of 1000 you need take 300 and for clearing (1000-300=-700) and -700 will be your payable amount, go to F-44.
Amount 700 will be new payable amount:
F110:
Regards
Javed

Error message: No pymt possible because items with a debit

Folks,
My vendor line items are
Rs 1000- credit memo dated 05/25/2006 pay terms net 30
Rs 50- credit memo dated 06/10/2006 pay terms net 30
Rs 300- credit memo dated 08/10/2006 pay terms net 30
Rs 5000 invocie dated 09/01/2006 pay terms net 30
getting error in F110 when run on 10/07/2006 :No pymt possible because items with a debit

Hi
Please check the grouping key on the vendor master record.
It could be just that the line items are grouped according to due date and are not able to offset each other.
The grouping key is on the automatic payment transactions block.
Hope this helps.

V. 2.2.1.00.04 Possible minor bug with breadcrumbs

Similar Messages

Maybe you are looking for