Window drawing Woes!

I just had a major crash while using Zend Studio on OSX, which I think it is a Java application. Now, I have this heavy black bordered box drawn around every window element I focus the mouse or keyboard on in every application window, even after rebooting twice and cleaning my system with Yasu.
The crash must have changed a window behavior but I have no idea where or how to recover from this without reinstalling...
How can I fix this?
Please help!

That was the ticket... How a Zend Studio crash turned those settings on, I'll never know...
But thank you very much for the helpful replies. You hit it right on the nail. And man was that fast...
Way to go.
Thanks,
Steve

Similar Messages

Why miltiple paints on initial window draw.

Hello all;
I have an application that has the quirky bug of issuing TWO
paint calls on the initial window draw.
If I collapse/minimize the window after the first (two) paints
and then restore it only one paint command message is issued.
Since there is a lot of graphics data being drawn this is a
severe performance problem.
Rather than include a ton of code I thought I'd ask for a few
high level pointers. This is simpy a JFrame window with no controls
or panels in it at the moment. There is only one show() call in
the constructor. No calls to paint() or repaint() anywhere.
Is there an easy way to figure out who is issuing the duplicate
message?
Thanks much!
/Steve

If you put
new Throwable("Why am I here?").printStackTrace()
in your paint() method you can see who called it

Open a new window, draw boxes in the window, and communicate between the two windows

I'm going to research this, but figured I'd jump start here in case someone can give me a quick link or point me in the right direction on how to do this while I'm looking. This is an area of Flex I haven't hit on yet.
Basically I need to have my flex app (AIR Application) open a new window, allow the user to draw a box on that new window, and then pass the info of the box (X and Y, Width and Height) back to the main window.
I've never done any of that and am going to try to find out how, but if someone could point me here before I find it online, that would help a great deal, kind of in a time crunch.... thanks.

You can open the new window as a TitleWindow popup. You can pass info back to the main app using mx.core.Application.application.
In main app:
public var windowInfo:Object;
In popup:
import mx.core.Application.application;
private var app:Object = mx.core.Application.application;
app.windowInfo.x = this.x;
app.windowInfo.y = this.y;
app.windowInfo.otherOne = this.otherProp;
Looking ahead, it is best to pass information between the main app and components using custom components. Below systemManager, popups and the main app are in different display lists, so add event listeners for custom events to systemManager. My Flex Cookbook post on custom events shows this:
http://www.adobe.com/cfusion/communityengine/index.cfm?event=showdetails&productId=2&postI d=11246
http://livedocs.adobe.com/flex/3/html/help.html?content=layouts_12.html
If this post answers your question or helps, please mark it as such.

System.Windows.Drawing not working on server Environment (Windows 2008 and 2012 server) ?

HI All,
I am facing a problem from past few days on server environment. I have created the code for taking the screen shot of the windows as follow...This code is perfectly working in Run time environment. While running and debugging the application it is working
fine.
But once i configured this website on Windows server 2008 or Server 2012 it is not working it hangs out the application at the method graphics.CopyFromScreen().
I am unable to find out the solution for this from last few day's. please help me to fix it. The code is as follow.
Bitmap bitmap = new Bitmap(600, 500);
Graphics graphics = Graphics.FromImage(bitmap as System.Drawing.Image); // The application hangs at this pt
graphics.CopyFromScreen(160, 235, 0, 0, bitmap.Size);
string mappath = Server.MapPath("~/dimurl/image/");
bitmap.Save(mappath + "myfile.jpeg", System.Drawing.Imaging.ImageFormat.Jpeg);
Please help me to resolve this.
Vaibhav Bhutkar, Jr. .Net Developer, Pune India.

Hello Vaibhav,
Welcome to MSDN forum.
Your issue is out of support range of VS General Question forum which mainly discusses
the usage of Visual Studio IDE such as WPF & SL designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System
and Visual Studio Editor.
If your issue is on ASP.NET website, I suggest that you can consult your issue on ASP.NET forum:
http://forums.asp.net/
for better solution and support.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Need help with window drawing thing

Hi all,
This program moves a circle around a screen. It used to work, even in the full screen mode that I have made it in. However, the contents of windowClass that set the attributes of the window (size, full screen, etc) used to be in the run() method of the main class. When I moved them to the windowClass class to tidy up the code, the program for some reason no longer paints the contents of the 'artwork' object to the screen. The KeyEvents still work, and everything. I can't figure out why, because this change was the only one I made between the program working and not working - I have not changed anything relating to the container or artwork at all.
In case you have not figured out yet this is an application, not an applet.
Sorry about the lack of programming notes, this program was just intended as a quick test and while I was writing it I did not see the need. (from the name you can see it started off as a test of KeyEvents but went a little further) If nobody can follow then I will put them in, but I would rather not because that takes time.
Thank you!
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
public class TryEvents extends Thread implements KeyListener
 boolean left = false;
 boolean right = false;
 boolean up = false;
 boolean down = false;
 static Toolkit theKit = Toolkit.getDefaultToolkit();
 static Dimension screenSize = theKit.getScreenSize();
 public static int xWin = screenSize.width;
 public static int yWin = screenSize.height;
 private static TryEvents theApp;
 private static JFrame window;
 private static theArtwork artwork;
 private static Container content;
 private static GraphicsEnvironment environment =
 GraphicsEnvironment.getLocalGraphicsEnvironment();
 private static GraphicsDevice device = environment.getDefaultScreenDevice();
 public static void main(String[] args)
 Thread theApp = new TryEvents();
 theApp.start();
 public void run()
 window = new windowClass("Trying Events", device);
 content = window.getContentPane();
 artwork = new theArtwork();
 content.add(artwork);
 window.addKeyListener(this);
 while(true)
 if(left == true && right == false)
 artwork.moveLeft();
 if(right == true && left == false)
 artwork.moveRight();
 if(up == true && down == false)
 artwork.moveUp();
 if(up == false && down == true)
 artwork.moveDown();
 try
 Thread.sleep(15);
 catch(InterruptedException e) {}
 public void keyPressed(KeyEvent e)
 int key = e.getKeyCode();
 if(key == KeyEvent.VK_LEFT)
 left = true;
 if(key == KeyEvent.VK_RIGHT)
 right = true;
 if(key == KeyEvent.VK_UP)
 up = true;
 if(key == KeyEvent.VK_DOWN)
 down = true;
 if(key == KeyEvent.VK_ESCAPE)
 System.exit(0);
 public void keyReleased(KeyEvent e)
 int key = e.getKeyCode();
 if(key == KeyEvent.VK_LEFT)
 left = false;
 if(key == KeyEvent.VK_RIGHT)
 right = false;
 if(key == KeyEvent.VK_UP)
 up = false;
 if(key == KeyEvent.VK_DOWN)
 down = false;
 public void keyTyped(KeyEvent e) {}
class windowClass extends JFrame
 private static GraphicsDevice device;
 public windowClass(String title, GraphicsDevice device)
 this.device = device;
 setTitle(title);
 setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
 setUndecorated(true);
 setResizable(false);
 device.setFullScreenWindow(this);
class theArtwork extends JPanel
 int xPoint = 0;
 int yPoint = 0;
 int xcircleSize = 30;
 int ycircleSize = 30;
 int movement = 7;
 public void paintComponent(Graphics g)
 super.paintComponent(g);
 g.setColor(Color.white);
 g.fillRect(0,0,TryEvents.xWin, TryEvents.yWin);
 g.setColor(Color.blue);
 g.fillOval(xPoint, yPoint, xcircleSize, ycircleSize);
 public void update(Graphics g)
 paint(g);
 public boolean canMove()
 boolean canMove = true;
 if(xPoint < 0 | yPoint < 0)
 canMove = false;
 if(xPoint + xcircleSize > TryEvents.xWin)
 canMove = false;
 if(yPoint + ycircleSize > TryEvents.yWin)
 canMove = false;
 return canMove;
 public void moveRight()
 xPoint += movement;
 if(canMove())
 repaint();
 else
 xPoint -= movement;
 public void moveLeft()
 xPoint -= movement;
 if(canMove())
 repaint();
 else
 xPoint += movement;
 public void moveDown()
 yPoint += movement;
 if(canMove())
 repaint();
 else
 yPoint -= movement;
 public void moveUp()
 yPoint -= movement;
 if(canMove())
 repaint();
 else
 yPoint += movement;
}Thank you again!

Okay, just figured out why now, the call to method:
device.setFillScreenWindow(...)
makes the frame visible, so changes to the content pane are not updated automatically, you have to do a content.validate() to make sure that the changes are applied if it is already visible. By resetting the window's content pane content.validate() must be called...
So you could do several things:
1) do the window.setContentPane(content); like I did before,
2) do a content.validate(); after you add drawing to it...
3) move device.setFullScreenWindow(...) from the constructor to run
method after you set up the content pane...

X201s Windows Backup woes

I set up the Windows Backup, but when I attempt to backup, I get a message that the backup did not complete successfully. A message appears that states: "Windows backup encountered a problem while determining additional locations of one of the users included in the backup. Details: the parameter is incorrect." "Error Code: 0x8100038"
The options given are to retry and to change backup settings; I have done both to no avail. I am backing up to a Samsung G2 portable drive. Does anyone know what I am doing wrong? The help files are not illuminating. Thanks.

Welcome to the forums!
Microsoft has a resolution for this.But only use this method if you are comfortable on working with the registry.
1. Login as the user
2. Run -> regedit.exe
3. Navigate to HKEY_CURRENT_USER\Sofware\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
4. Observe the value of Appdata and LocalAppdata.
If it has an empty value or a value of the type %Appdata%, this is the culprit.
If so, the workaround is the following:
 a. Open a command prompt
 b. Type set Appdata / LocalAppdata depending on which registry entry has the wrong value. If Appdata is wrong, type set Appdata and if Local Appdata is wrong, type set LocalAppdata.
 c. Copy the value after the = sign. Example if the output is: APPDATA=C:\Users\John\Appdata\Roaming, copy the value C:\Users\John\Appdata\Roaming
 d. Paste the value in the wrong registry value. Either replace the %<<<>>>% value or fill the empty value.
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

Windows 8 woes on bootcamp/partitioning/help please!

So, I ordered a copy of windows 8 OEM edition 64bit. I'm on a late 2012 macbook pro 13 inch with mac os x 10 mountain lion.
I recieved it, started up bootcamp did as it said and then when i came to installing windows the partitioned hard drive I'd created (100gb) for windows wasn't useable. Windows 8 said "can't use *bootcamp partition I forget the exact name/perhaps partition 4*. Windows gave me the option to format the drive. So i did. And the drive was then obviously no longer boot camp and has turned into a standard NTFS drive (I'm not that clued up on this go easy on the terminology for me!). In short, I then continued to install windows 8 on a none bootcamp partition.
This installation doesn't have the drivers needed (probably from bootcamp) for use of the macbooks dvd drive or the volume/media/keyboard light buttons it doesn't recognise the wifi card or anything..
So i guess I need to know these things:
1) how do I uninstall windows 8 from that partition and then restore that partition to recreate the whole, original volume? Is there a way of uninstalling windows that means I can use it again (i.e. I don't want to be paying another £60 for the privilage of a new license)
2) how do I do the PROPER bootcamp installation? and what happens if I hit that bit where windows 8 doesn't like the bootcamp partition i created?(i know not to format the hard drive now!)
Thanks for any help guys, much appreciated!

Welcome to the Apple Support Communities
First of all, Boot Camp isn't compatible with Windows 8 because Apple hasn't released Boot Camp drivers for it, so do it at your own risk. If you don't want to break the Mac, install Windows 7.
SlugsForBrows wrote:
1) how do I uninstall windows 8 from that partition and then restore that partition to recreate the whole, original volume? Is there a way of uninstalling windows that means I can use it again (i.e. I don't want to be paying another £60 for the privilage of a new license)
If you didn't erase OS X, press X key while your Mac is starting to start into OS X, open Boot Camp Assistant and follow the steps to erase the Boot Camp volume.
SlugsForBrows wrote:
2) how do I do the PROPER bootcamp installation? and what happens if I hit that bit where windows 8 doesn't like the bootcamp partition i created?(i know not to format the hard drive now!)
Thanks for any help guys, much appreciated!
Open Boot Camp Assistant and follow the steps to install Windows. When you are on the partitioning screen, format only the BOOTCAMP volume and install Windows on it.
Boot Camp Assistant will ask you to download the drivers, but now they are useless for Windows 8

XFCE4 Window drawing problem

Greetings again,
I have this problem with XFCE4, from [extra] (look at the toolbar): http://xs313.xs.to/xs313/07136/toolbar.png
My xorg.conf is as follows:
# File generated by xorgconfig.
# Copyright 2004 The X.Org Foundation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
# Refer to the xorg.conf(5) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# SubSection "extmod"
# Option "omit xfree86-dga" # don't initialise the DGA extension
# EndSubSection
# This loads the font modules
# Load "type1"
Load "freetype"
Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"
EndSection
# Files section. This allows default font and rgb paths to be set
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# RgbPath "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
# FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/lib/modules"
EndSection
# Server flags section.
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# Input devices
# Core keyboard's InputDevice section
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "gb"
EndSection
# Core Pointer's InputDevice section
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
Section "Monitor"
Identifier "S700"
Option "DPMS"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 30-69
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 59-85
EndSection
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "prosavage"
Driver "savage"
BusID "PCI:1:0:0"
#VideoRam 16384
# Insert Clocks lines here if appropriate
EndSection
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "prosavage"
Monitor "S700"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
Can anyone help me? Thank you.

It was with all themes, the problem's fixed now. I had to add this line into my xorg.conf
load extmod
Under modules. Thanks though.

How to draw dynamic table in SAP Script !

Hi,
I like to draw a table in the main window, the table height should depends on number of rows displayed on it.
Could any one please help on this.
Thank you,
Senthil

HI senthil
you have to use the BOX command in the SAPSCRIPT using which you can draw the table in script.
in the starting of the MAIN WINDOW draw a horizontal line and then display your vairables
in end again draw a horizontal line to close the table.
the height of the vertical line will the number of records in the internal table.
the vertical line can be drwan uisng
BOX XPOS 10 YPOS 20 width 0 CH hieght <rowcount> CH.
regards
kishore
regards
kishore

SAPScript box drawing

Hi Guys,
I'm facing difficulties on drawing a box with records in SAPScript. Im using below for box drawing:
1. Draw main box
/: BOX WIDTH 280 MM HEIGHT 130 MM FRAME 10 TW
2. Draw vertical line to separate each different COLUMN
/: BOX XPOS 15 CH WIDTH 0 CH HEIGHT 130 MM FRAME 10 TW
3. Draw horizontal line to separate each different RECORD
/: BOX YPOS 4 CH WIDTH 280 MM HEIGHT 0 CH FRAME 10 TW
Problems:
1. For drawing horizontal line to seprate each record, basically i fix a static incremental counter for YPOS xxx CH.
For eg:
1st line -> /: BOX YPOS 4 CH WIDTH 280 MM HEIGHT 0 CH FRAME 10 TW
2nd line -> /: BOX YPOS 6 CH WIDTH 280 MM HEIGHT 0 CH FRAME 10 TW
3rd line -> /: BOX YPOS 8 CH WIDTH 280 MM HEIGHT 0 CH FRAME 10 TW
... and so on, until the end of the box
The output LINE for first few records still ok, but for the rest it is overlapping with the records.
---> Please comment the right way to overcome above.
2. The code for drawing horizontal line is a lot, is there a better to perform the drawing?
> Please comment
Thanks in advance.

Hi,
My problem solved by using LN as below:
:/ BOX YPOS 4 LN WIDTH 280 MM HEIGHT 0 CH FRAME 10 TW
But right now, im using command SIZE to draw a box for me automatically by following the actual window size. I did that with no problem.
But im facing problem when im drawing Vertical line(column separator)within the box. Im intend to draw a line without specific the height for Vertical line(because my 2nd page's height is larger than 1st page and thus i do not want to harcode the height). Below is my code:
/:SIZE WINDOW -->Draw main box
/:BOX FRAME 10 TW -->Draw main box
/:BOX XPOS 15 CH FRAME 10 TW --> Draw vertical line
The result returned with problem, there are 2 vertical line being draw out. 1st line is draw at position 15 ch as instructed by the command, but there is 2nd line draw out of my main box on right, this is not expected.
Please comment on how should i fix the code.
Thanks in advance.

Issue with active window

Hello you, problem solver!
I have a little issue with active/inactive windows
For exemple when I use GIMP, this software is on 3 different windows... so my problem is:
when I'm on the image window drawing lines and I want to switch the pen..
I have to click on the tools window to active it then select the pen
And to go back on the image window and draw I have to click on the image window to active it then clic again to use the pen...
Is there a way to bypass the "Click to active the window" step?
Like click to draw, click to select a new tools and click back on the image window to draw...
Thanks for your help!

Welcome to the discussions.
This might be better answered at GIMP forums or FAQ as it looks like a UI issue with GIMP. Here is a link that you might want to visit. http://www.gimp.org/develop/
Also this is a good place http://gimp-brainstorm.blogspot.com/ where you can tell them your ideas.
Message was edited by: Meherally

Draw table with sapscript

Hi all,
My requirement is to draw a table with 4 rows and 5 columns.
I tried to code like this :
/E BOX
/:BOX HEIGHT '0.5' CM FRAME 10 TW
/:BOX XPOS '.48' CM WIDTH 0 TW HEIGHT '0.5' CM FRAME 10 TW
/:BOX XPOS '.78' CM WIDTH 0 TW HEIGHT '0.5' CM FRAME 10 TW
/:BOX HEIGHT '1.0' CM FRAME 10 TW
/:BOX XPOS '.48' CM YPOS '0.5' CM WIDTH 0 TW HEIGHT '0.5' CM FRAME 10 TW
/:BOX XPOS '.78' CM YPOS '0.5' CM WIDTH 0 TW HEIGHT '0.5' CM FRAME 10 TW
/:BOX HEIGHT '1.5' CM FRAME 10 TW
/:BOX XPOS '.48' CM YPOS '1.0' CM WIDTH 0 TW HEIGHT '0.5' CM FRAME 10 TW
/:BOX XPOS '.78' CM YPOS '1.0' CM WIDTH 0 TW HEIGHT '0.5' CM FRAME 10 TW
However my output is not the same as what I seen in the preview and real printout.
Preview
http://i566.photobucket.com/albums/ss106/wkw510/pic12.jpg
Printout
http://i566.photobucket.com/albums/ss106/wkw510/pic13.jpg
Can someone please guide me how to resolve this?
Or provide me some code or reference how to get the above requirement?
Many thanks!

Hi,
In WINDOW draw a horizontal line in the starting and in end again draw a horizontal line to close the table and the height with the vertical line.
or.
BOX XPOS '3' CM WIDTH 0 TW HEIGHT '8.2' CM FRAME 10 TW.
Regards,
jaya

K7T266 Pro R and Geforce 2 GTS problem

Hello everyone. I have been experiencing a problem for some time now regarding lockups and crashes caused by my video card, which vary in severity depending on the driver version used. Since I'm using an MSI K7T266 Pro Raid mobo (version 1) I thought I'd post my question here.
The exact problem depends on the driver version. Using any Nvidia Detonator drivers at version 40 or newer, my system becomes extremely unstable. On first booting everything seems fine, however if I try to open my Geforce display properties the Windows freezes during the redraw of the display properties window, which goes blank. Sometimes I can call up Close Programs Dialog, which shows DDHELP in the list, and [not responding]. I've never actually gotten an error message from DDHELP or any other error message -- perhaps the computer jams too hard for Windows to get one up. I've seen reports around the Net about DDHELP problems from things like DirectX 8.1, but they're never quite like my problem. The problem is identical on DirectX 8.0, 8.1, and on 9.0.
No matter what I try to do in Windows with these drivers installed, the computer will lock up in seconds. For example, if I then open IE 5.5, I might be able to get as far as a page or two before the similar thing happens: during the window redraw the computer locks up (usually with a blank or partially-redrawn window), sometimes causing the mouse to lock and sometimes not, and then if I can get the Close Program Dialog open DDHELP has appeared and is Not Responding.
The most stable driver version I've found so far is 29.42, which does not cause the lockup above and never causes DDHELP to appear. However, it is quite unstable as well, and causes Windows to lock up sporadically during 2D window redraws in various programs. For example, when calling up a Save Document dialog or when opening a pulldown menu the program will lock either before any of the redraw becomes visible on screen or when the new dialog box is "skeletal", only partially drawn. Sometimes the crash is severe enough that I have to do a cold restart on my system.
The other problem is that sporadically garbage blocks will appear in portions of my screen, like old windows and color bands popping up that do not refresh. This often happens to me in Photoshop 6, and happens usually when I'm scrolling down a window or something.
These problems with version 29.42 all appear to be 2d window-drawing related. I do not have any problems with 3d games with 29.42. However, the new reference drivers are so unstable on my system that I can't even try to open them.
With 29.42, the most stable drivers I've found so far, some kind of lockup due to redrawing windows almost always occurs within an hour (sometimes minutes) of booting up.
For what it's worth, dxdiag tests just fine.
I was hoping someone could help me figure out what's causing the trouble, what driver I should use, and how to resolve it. If possible, I'd really like to use the newer drivers as I've been told they're much faster. In any event, I hate having such an unstable system where lockups could occur at any moment!
Here's the lowdown of my system:
-MSI K7T266 Pro Raid [1] mobo (MS-6380)
AMIBIOS date: 5/1/2001
VIA 4in1 drivers version 4.45
ACPI power management disabled
PnP Aware OS enabled
-256 meg PC2100 SDRAM with 266 mhz FSB
2.5 cas latency
-AMD Athlon 1.33 gb with 266 mhz FSB
-Asus AGP-V7700 (Geforce 2 GTS) 32 mb
AGP 4X, Fast Write enabled, Aperture size 128 mb
current drivers: Nvidia reference 29.42 (also 40+)
on IRQ11 (shares with my Ethernet card)
BIOS version 2.15.01.14
-Windows 98SE
-DirectX 9.0 (also tried 8.1 etc)
-Soundblaster Live! 5.1 on slot 3, drivers from 5/2002
-Viewsonic PF790 monitor
-C drive is 30gb Western Digital 7200rpm, FAT32
-D drive is Raid 0 striped array, pair of 40gb 7200rpm
-Network Everywhere Fast Ethernet Adapter on slot 5
-no memory resident programs on loadup except for WinPoET, Explorer, Systray
If there's anything I've left out that could help, let me know!
Thanks to anyone in advance,
Raphael Tehan

Quote
Originally posted by backwoodz
You should post this in the VIA forums........If was me I would first swap the nic card to a differnt slot and try to stop the sharing of videos irq.....secondly try relaxing your memory timings to the most laxed setting
Thanks, I realized after posting this was the incorrect forum. I've put it in the VIA Socket A boards area, and also am trying the Via Arena forums.
Are you talking about my mainboard or graphics card memory?
Here's what I've got set under Advanced Chipset:
Configue SDRAM timing by: SPD
SDRAM Frequency: HCLK
SDRAM CAS# Latency: 2.5
SDRAM Bank Interleave: disabled
SDRAM 1T command: enabled
AGP mode: 4x
AGP comp driving: auto
Manual AGP comp. driving: CB
AGP Fast Write: enabled
AGP Read Synchronization: disabled
AGP aperture size: 128 mb
Do any of these settings seem problematic to you?
Thanks.

K7T266 Pro Raid and Geforce 2 GTS problem

(Originally posted to wrong group)
Hello everyone. I have been experiencing a problem for some time now regarding lockups and crashes caused by my video card, which vary in severity depending on the driver version used. Since I'm using an MSI K7T266 Pro Raid mobo (version 1) I thought I'd post my question here.
The exact problem depends on the driver version. Using any Nvidia Detonator drivers at version 40 or newer, my system becomes extremely unstable. On first booting everything seems fine, however if I try to open my Geforce display properties the Windows freezes during the redraw of the display properties window, which goes blank. Sometimes I can call up Close Programs Dialog, which shows DDHELP in the list, and [not responding]. I've never actually gotten an error message from DDHELP or any other error message -- perhaps the computer jams too hard for Windows to get one up. I've seen reports around the Net about DDHELP problems from things like DirectX 8.1, but they're never quite like my problem. The problem is identical on DirectX 8.0, 8.1, and on 9.0.
No matter what I try to do in Windows with these drivers installed, the computer will lock up in seconds. For example, if I then open IE 5.5, I might be able to get as far as a page or two before the similar thing happens: during the window redraw the computer locks up (usually with a blank or partially-redrawn window), sometimes causing the mouse to lock and sometimes not, and then if I can get the Close Program Dialog open DDHELP has appeared and is Not Responding.
The most stable driver version I've found so far is 29.42, which does not cause the lockup above and never causes DDHELP to appear. However, it is quite unstable as well, and causes Windows to lock up sporadically during 2D window redraws in various programs. For example, when calling up a Save Document dialog or when opening a pulldown menu the program will lock either before any of the redraw becomes visible on screen or when the new dialog box is "skeletal", only partially drawn. Sometimes the crash is severe enough that I have to do a cold restart on my system.
The other problem is that sporadically garbage blocks will appear in portions of my screen, like old windows and color bands popping up that do not refresh. This often happens to me in Photoshop 6, and happens usually when I'm scrolling down a window or something.
These problems with version 29.42 all appear to be 2d window-drawing related. I do not have any problems with 3d games with 29.42. However, the new reference drivers are so unstable on my system that I can't even try to open them.
With 29.42, the most stable drivers I've found so far, some kind of lockup due to redrawing windows almost always occurs within an hour (sometimes minutes) of booting up.
For what it's worth, dxdiag tests just fine.
I was hoping someone could help me figure out what's causing the trouble, what driver I should use, and how to resolve it. If possible, I'd really like to use the newer drivers as I've been told they're much faster. In any event, I hate having such an unstable system where lockups could occur at any moment!
Here's the lowdown of my system:
-MSI K7T266 Pro Raid [1] mobo (MS-6380)
AMIBIOS date: 5/1/2001
VIA 4in1 drivers version 4.45
ACPI power management disabled
PnP Aware OS enabled
-256 meg PC2100 SDRAM with 266 mhz FSB
2.5 cas latency
-AMD Athlon 1.33 gb with 266 mhz FSB
-Asus AGP-V7700 (Geforce 2 GTS) 32 mb
AGP 4X, Fast Write enabled, Aperture size 128 mb
current drivers: Nvidia reference 29.42 (also 40+)
on IRQ11 (shares with my Ethernet card)
BIOS version 2.15.01.14
-Windows 98SE
-DirectX 9.0 (also tried 8.1 etc)
-Soundblaster Live! 5.1 on slot 3, drivers from 5/2002
-Viewsonic PF790 monitor
-C drive is 30gb Western Digital 7200rpm, FAT32
-D drive is Raid 0 striped array, pair of 40gb 7200rpm
-Network Everywhere Fast Ethernet Adapter on slot 5
-no memory resident programs on loadup except for WinPoET, Explorer, Systray
If there's anything I've left out that could help, let me know!
Thanks to anyone in advance,
Raphael Tehan

Quote
Originally posted by backwoodz
You should post this in the VIA forums........If was me I would first swap the nic card to a differnt slot and try to stop the sharing of videos irq.....secondly try relaxing your memory timings to the most laxed setting
Thanks, I realized after posting this was the incorrect forum. I've put it in the VIA Socket A boards area, and also am trying the Via Arena forums.
Are you talking about my mainboard or graphics card memory?
Here's what I've got set under Advanced Chipset:
Configue SDRAM timing by: SPD
SDRAM Frequency: HCLK
SDRAM CAS# Latency: 2.5
SDRAM Bank Interleave: disabled
SDRAM 1T command: enabled
AGP mode: 4x
AGP comp driving: auto
Manual AGP comp. driving: CB
AGP Fast Write: enabled
AGP Read Synchronization: disabled
AGP aperture size: 128 mb
Do any of these settings seem problematic to you?
Thanks.

Radeon 9800 pro 256mb hanging on blue screen

I'm deep in the waters of frustration right now, and am hoping someone here might have the answer.
About 3 months ago I was looking for a video card for me to run motion. I saw the 9800 mac special edition with 128mb video ram had rave reviews. At that time ATI was not making them. So I turned to eBay...
I purchased a card that was advertised as a Mac 9800 pro special editing 128mb. I later found out it was a flashed pc card. The ebay seller told me the card worked fine on all his mac's that he tested it on.
The problem I was having was the machine boots up, I see the grey screen with the Apple logo and spinning wheel. I see the blue screen where normally I see the login progress bar loading the OS. But with this card I only see the blue screen. I hear the hard drive churning, so I am assuming it is still loading the OS, but I cannot see anything. I can reboot in safe mode and the video card works fine.
Well... I assumed it was the fault of the card and that it was flashed. I returned the card to the ebay seller, who sent me another one, same results with that one. I returned the card to the seller and he refunded my money.
I put the money toward the just released Radeon 9800 Pro Mac Edition 256mb card. I just got it a couple days ago and am experiencing the same problems. I have tried everything... everything I know and still can't get the card to work? Here is a list of what I have done:
With the flashed card:
1. Shut off computer and unplugged it. Removed OEM video card and installed ATI 9800 card. Plugged the power supply cable for the card into the computer power supply cable and hard drive.
Problem Occurs: When starting up, the grey screen comes up with the Apple on it, then the screen turns blue, where I typically would see the progress bar of the system loaded up before the user login screen. I only see a blue screen at this point but can hear the hard drive working for about a min.
2. Restarted the computer in safe mode.
3. Logged in as Admin user and opened the ATI preference pane to verify it sees the card.
When the ATI preference pane was loaded the following error message occured:
A startup problem has occured.
Cannot connect to ATI TVOut Kernal Extension. Some features are not available.
Clicked OK and the ATI preference pane appears.
4. Close the preference pane and reinstalled ATI Displays 4.5.6. Restarted computer.
Problem Occurs
5. Restarted computer holding down AppleOption+PR to clear PRAM. Cleared the PRAM 4 times in a row, by allowing the chime to happen 4 times.
Problem Occurs
6. Shut computer down. Disconnected the DVI plug for the cinema display and connected a VGA CRT monitor. Started computer.
Problem Occurs
7. Shut computer down, disconnected the VGA CRT monitor. Reconnected DVI plug and restarted computer.
Problem Occurs
8. Started the computer in safe mode. Logged into admin account. Opened the ATI Preference pane.
When the ATI preference pane was loaded the following error message occured:
A startup problem has occured.
Cannot connect to ATI TVOut Kernal Extension. Some features are not available.
Closed preference pane.
Went to ATI site and downloaded:
aug2005-radeo-universal-rom-update.dmg
Ran the updater.
Restarted computer.
Problem Occurs.
9. Restarted the computer in safe mode. Changed the login preference pannel to automatically log into the administrator account. Restarted computer, waited for the blue screen, then walked away for about 2 hours with the computer on blue screen, hoping the system was loading or doing something.
Problem Occurs.
10. Put in the TechTools Pro CD, hoping to run some tests on the video card from the cd. When booting from the CD OS...
Problem Occurs.
11. Enabled Root user. Logged in as root and installed ATI Displays 4.5.6 from there. Restarted computer.
Problem Occurs.
12. Shut down computer and installed old video card.
13. On an internal hard drive in the computer. Wiped the drive and formatted it. Installed 10.4.1 on the drive. booted up into the drive, installed ATI drivers, shut down computer, installed 9800 pro video card, booted up.
Problem Occurs.
With the new 9800 for Mac ATI card with 256mb:
With original card, install drivers, repairpermissions, shut down, install new card
Set to restart in single user, give 5 min to see if ATI monitor startup item in user starteputems loads
Hooked VGA & DVIt in together, both showed blue screen
Reset NVRAM via open firmware
Reset cuda button
Take battery out, wait at least 10 min, re-install new battery, press cuda button
Reinstall ATI update 4.5.6
Reset nvram from open firmware
In ATI control panel, selected 'Force Single Display Operation'
Change display scaling to 50%
Download latest Mac OS update from apple & reinstall
Help?

I get dizzy just thinking about it.
I have tried installed a brand new OS, 3 different times on a different Hard Drive, still the card doesn't work.
I had one person suggest that it may be the card is not communicating with the OS Window Drawing module? (excuse my ignorance of what that is really called. I just know there is some program, possibly in the kernel, that is responsible for drawing out the OS windows.)
How can we rule out that it is a bad AGP slot?
•The slot works fine with my 9000.
•It works in safe mode with the 9800.
•I have installed a brand new OS, three different times, still doesn't work.
•I have used Apple Hardware test to test my hardware, the AGP slot didn't report any problems.
I am assuming that the AGP slot is working. Although I worry about it a bit, because by now I have swapped cards in it about 50 times in my troubleshooting.
Here is a link to a complete list of everything I have tried:
http://www.macosx.com/help/qview.php?questionid=19554#54138

Window drawing Woes!

Similar Messages

Maybe you are looking for