Bizzarre non-deterministic run-time behavior.
This is an attempt to coninue a thread that fell into the Archived Forums category after a year of inactivity. That thread can no longer be updated.
This post is merely to note that the bug encountered in
http://forum.java.sun.com/thread.jspa?threadID=463092
was finally fixed by the JDK 1.4.2_06 . This fact is also documenter here:
http://java.sun.com/j2se/1.4.2/ReleaseNotes.html
BugID: 4917709: SEGV in MapLoops test
Java release version: 1.4.2_06, all platforms
Duh! I now see that this fact is available in the Bug Parade.
Similar Messages
-
How to display "Non-Fatal Run-Time Error In Function Panel" dialog?
I'm learning how to develop an IVI-C specific driver using LabWindows/CVI. When I run my function from its function panel and it returns an error, I would like to display a dialog with both the error code and error message (as opposed to simply returning an error code on the function panel). This would save the user from having to call Prefix_error_message() to translate the error code to its error message. NI-DCPower driver is a good example of this behavior (see attached error dialog). How do I show the "Non-Fatal Run-Time Error In Function Panel" dialog? Any help is greatly appreciated. Thanks!
Attachments:
ErrorDialog.png 8 KBHi Shawn,
Thank you for replying to my post. The checkErr is just an error handling macro defined in ivi.h to goto Error: tag when the function returns a non-zero value. I have been using the checkErr macro (as well as viCheckErr and other macros) in my driver.
Using the same hp34401a specific driver as an example, please allow me to explain my question in more details:
Let's take the hp34401a_close function as an example. It is a simple function with only a few lines of code:
When the hp34401a_close function is run from its front panel using an invalid session handle (e.g. "8" in this screen capture):
You will get three "Non-Fatal Run-Time Error" popup dialogs, one from each of the IVI library functions that it calls: Ivi_LockSession, Ivi_UnlockSession, and Ivi_Dispose. However, there is no "Non-Fatal Run-Time Error" popup dialog from the hp34401a_close itself.
My IVI-C specific driver is behaving identical to the hp34401a specific driver.
In comparison, if run niDCPower_close function from its front panel using an invalid session handle (using the same "8" in this screen capture):
You will only get one "Non-Fatal Run-Time Error In Function Panel" from the niDCPower_close function itself:
I think the behavior of niDCPower driver is much better than the hp34401a driver. It replaces the three "Non-Fatal Run-Time Error" popup dialogs from the IVI library with a single "Non-Fatal Run-Time Error In Function Panel" popup dialog from the driver function itself. I would like to do the same thing with my driver but have not figured out how to display a "Non-Fatal Run-Time Error In Function Panel" dialog. Thanks in advance for your help! -
Strange Run-time behavior of message mapping
Dear All,
This is very urgent
I have 2 step mapping in my synchronous(ABAP proxy to HTTP_AAE) interface, first step is graphical mapping and second step is java mapping. After both the mapping I am able to get my desired structure by bank(third party), below is what I am getting in testing tab in Operation mapping after 2 step mapping, which is expected.
strXmldata=<?xml version="1.0" encoding="UTF-8"?><PaymentInfoMessage><PaymentInfoRequest><CompanyCode>TEST</CompanyCode><BankCode>RIBLSARI</BankCode><StartDate>2014-01-21T00:00:00</StartDate><EndDate>2014-01-21T00:00:00</EndDate><TransactionType>940</TransactionType></PaymentInfoRequest></PaymentInfoMessage>
However, bank is receiving in reverse, I mean the string strXmldata is coming at last. see the below
<?xml version="1.0" encoding="UTF-8"?><PaymentInfoMessage><PaymentInfoRequest><CompanyCode>TEST</CompanyCode><BankCode>RIBLSARI</BankCode><StartDate>2014-01-21T00:00:00</StartDate><EndDate>2014-01-21T00:00:00</EndDate><TransactionType>940</TransactionType></PaymentInfoRequest></PaymentInfoMessage>=strXmldata
When I check the trace in SXMB_MONI in the pipelines trace under "request message mapping" it has been reversed by system at runtime.
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_Request_MT940_</Trace>
<Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
<Trace level="3" type="T">Document start</Trace>
<Trace level="3" type="T">Start tag [MT_HTTPReq_MT940]</Trace>
<Trace level="3" type="T">Put value [<?xml version="1.0" encoding="UTF-8"?><PaymentInfoMessage><PaymentInfoRequest><CompanyCode>TEST</CompanyCode><BankCode>RIBLSARI</BankCode><StartDate>2014-01-21T00:00:00</StartDate><EndDate>2014-01-21T00:00:00</EndDate><TransactionType>940</TransactionType></PaymentInfoRequest></PaymentInfoMessage>=strXmldata]</Trace>
Could anyone please let me know why this reversing and putting the string strXmldata at last.
Please this is very urgent, please help me as soon as you can.
Thanks,
FarhanHi Farhan,
The issue is because of run time behavior but you can try to deploy the java or XSLT map in server and use in receiver adapter (as adapter module).
How to Create Modules for the J2EE Adapter Engine (NW 2004)
regards,
Harish -
Newbie question NON-FATAL RUN-TIME ERROR IN TUTORIAL (PlotY)
I'm a first time user, following the tutorial and when when I click on Acquire I get the following error "NON-FATAL RUN-TIME ERROR: "sample1.c", line 85, col 13, thread id 0x00000D54: Library function error (return value == -10 [0xfffffff6]). The control is not the type expected by the function"
Code is as follows (line 85 is PlotY......:
case EVENT_COMMIT:
srand (time(NULL));
amp = rand ()/32767.0;
SinePattern (100, amp, 180.0, 2.0, sine);
PlotY (panelHandle, PANEL_Waveform, sine, 100, VAL_DOUBLE, VAL_THIN_LINE, VAL_EMPTY_SQUARE, VAL_SOLID, 1, VAL_RED);
break;
Its not obvious why it crashes on this line, any help would be appreciated.
Thanks
JeffHappy to hear that you have solved your problem.
Just to be clear, there is no problem in using lowercase letters for control ID, but since the usual CVI behaviour is to use uppercase letters I was wondering if you created the control by yourself and if it could be a wrong one.
CVI does not really address controls by name: if you see in the include file associated to the UIR you'll see that PANEL_CONTROL is really a macro with an associated value, which is the one the program really uses (see my first post to understand how PlotY operates; the same happens for all functions that operate on control like Get/SetCtrlVal or GetSetCtrlAttribute for example).
Neither CVI operates any cross check between the panel handle and the control you are addressing: that's why I pointed you to the panel handle value, to be sure that you are not operating on a control using the handle of a different panel, a situation that may happen if you are using more than one panel at a time.
These are the reasons that may rise an 'incorrect control type' error.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos? -
Non-Fatal Run-time Error "%%s"
This was shown yesterday by an non-debug program written with CVI 9.01 and run-time 9.1 (the current "428" build) on the target.
I was trying to fix "-12: Out of memory" popups (maybe a race condition inside ProcessSystemEvents/GetUserEvent?) and now this.
Any idea what this is?
/* Nothing past this point should fail if the code is working as intended */A couple updates:
From all indications, this dialog should only be shown if your binary (exe) is built in release mode. If you build in debug mode, you should be able to see the error message that is trying to display. Also, if our preliminary investigation is correct, the error should be in your release mode exe, and not any loaded dlls.
From all indications, this dialog should only be shown if your binary (exe) is built in release mode and loads dlls that are build in debug mode. If you build your dependencies in release mode, no dialog should be displayed at all (because this is a non-fatal error).
Are you able to verify these statements?
Thanks -
NickB
National Instruments -
Time Machine only shows the current copy of the file I am trying to restore. There is none of the time machine backup histories shown. I am running OSX 10.7.5. I see the backup files on my external Time Machine hard drive in the Backups.backupdb folder.
Time Machine does show the history of my Macintosh HD, but when I try to navigate to the folder I wish to restore the backup history disappears. I've been searching for answers and I have not found one that works for me.Time Machine only shows the current copy of the file I am trying to restore. There is none of the time machine backup histories shown. I am running OSX 10.7.5. I see the backup files on my external Time Machine hard drive in the Backups.backupdb folder.
Time Machine does show the history of my Macintosh HD, but when I try to navigate to the folder I wish to restore the backup history disappears. I've been searching for answers and I have not found one that works for me. -
Applying/Removing Behavior at Run-Time. (Or the "pass" command)
I know it must be possible to do this, but I can't figure out
how. I need a
particular sprite to have a behavior either applied or
removed at run-time.
I tried using the "pass" command to get mouse-input to click
through the
object if certain conditions are not true, but it doesn't
seem to work.
Here's a sample of the script:
on mouseWithin me
if (someConditions) then
if the mouseDown then
<do a bunch of stuff>
end if
else
pass
end if
end
Technically, if the conditions are FALSE, it should skip
right past the rest
and pass the mouse input down to lower sprites, but it
doesn't. I've tried
a whole bunch of different things, adding the "pass" to
mouseDown and
mouseUp events, but most of the things in this game are
controlled by
mouseWithn/if the mouseDown, allowing you to click and drag
over multiple
sprites to record a down-click on all of them. (Also tried
using
mouseEnter, but that didn't work either.) I'm guessing that
the "pass"
command only works on explicit "mouseUp" and "mouseDown"
events, and doesn't
apply to other cases. If that's true, then I need to simply
have this whole
behavior not be there if those conditions are FALSE. Any
help?Never mind, I got it.
-
LabVIEW 2010 Window Size/Panel Size Run-Time VI properties - unexpected behavior
I have used the VI Properties Windows Run-Time Position - Panel Size and VI Properties - Window Size to set the desired display size for use on the application PC.
A strange thing happens, when I first open the application window, it is smaller than the specified Window Size and Panel Size (both set to 1064 x 728). However, if I click on a horizontal border the window's vertical size snaps instantly to the 728 pixel value and the horizontal size in unchanged, still smaller than the 1064 value specified. When I click on a vertical border, the horizontal size changes to the specified value.
I don't believe this is how these properties were intended to work. They should open the application in a window sized as specified.
Is this a known problem? Is there a workaround.I regret that I cannot post my employers' proprietary code. I have tried to duplicate the problem with a publicly distributed VI and been unable to do so.
I believe now that it is possible my VI was "straddling" two monitors when I made the initial changes.
Later compilations were made using different VI properties and do not show this problem.
I have attached a file showing the relevant VI property settings used in the aberrant VI compilation.
Attachments:
vi properties used.JPG 58 KB -
Installing the run-time engine as a non-administrator
I want to distribute a stand-alone application to end-users that are not administrator of their computer. When they try to install the RTE without administrator privileges, the installer cannot continue because it cannot write to the C:\ base directory. How can I fix the run-time engine installer to work without administrator privileges?
On the second screen of the installer, the user can choose an alternative target location. Have you tried that?
(sorry, I don't know how well this will work). What is the runtime version?
(For your reference, this document describes planned changes in the folder structure for future LabVIEW versions.)
LabVIEW Champion . Do more with less code and in less time . -
"open vi reference" with run time menue
Hello,
I met some problems with "open vi reference" in labview.i can't parallel run this vi with the run time menue.i can't load the any vi then the run time menue has activation.(the "open vi reference" can run after the run time menue release.). it's means labview is serial running for this both function.but now i want to parallel running in the program.so would you give the some idear?Now I see what you are talking about. What you are trying to do is expected behavior. If you click on the menu while any state is running that doesn't lock the front panel, then the menu will halt the VI execution until you choose a menu item.
You should check the option in the event to "Lock front panel until event case for this event completes" Then you will not be able to click on the system menu until tthe VI is launched and running. If you wire a True like I suggested before, then you will fall out of the case pretty quickly in non-hoghlight mode, and the user most likely will not notice. If the VI you are trying to open is quite large, it will take a little bit of time for LV to load the VI into memory.
In highlight-mode, you just have to wait for the event to process before you select the menu.
Message Edited by Matthew Kelton on 12-03-2007 10:56 PM
Attachments:
edit events.png 27 KB -
How to choose RT System at Run Time
Variations of this question have been asked, but I'm not sure if they've been answered.
We use LabVIEW RT to do a variety of behavior tests. We have multiple experimenters using the same hardware, and each has his/her own set of "What I want to do" requirements.
Originally, we used LabVIEW 7.0 (i.e. Before Project) to develop a Host and Remote (PXI) application. The Host application was built as an .EXE, while the Remote was saved as an .LLB, copied to the PXI, and "invoked" at Run Time by calls to VI Server. Note that this means that the code on the Remote might (is?) not be as compact, efficient, or optimized as if we had built an .EXE. But we definitely can have Bob's Experiment, Jane's Experiment, and Joe's Experiment on the PC (as separate executables), and each could respectively call Bob's RT, Jane's RT, or Joe's RT on the PXI at run time. No need to have LabVIEW (or LabVIEW expertise) on this system, and Bob, Jane, and Joe can be "ordinary users".
"Modern LabVIEW" takes a slightly different (and probably better) view towards Real-Time -- both the Host and Remote programs are built as Executables (the RT is built as an .RTEXE). We can "pre-deploy" the RT code to the PXI, and set it to run at Startup. This makes getting the RT side "running" semi-automatic -- all you need to do (if it isn't running) is reboot the PXI.
But what if you want Bob, Jane, and Joe's version, selectable by running (on the Host) Bob, Jane, or Joe's Host application?
I'm playing with the following algorithm, which seems to work. I'm presenting it here to get feedback, especially if there is a "better way" to do this.
The key to this method is that there is an .INI file on the Remote, C:\ni-rt.ini, that contains, among other things, the RT Target's Startup Application path (by default, this is C:\ni-rt\startup\startup.rtexe).
Consider three Projects, Project Bob, Project Jane, and Project Joe. Within each Project, a Host executable is built having a name like "UI Bob" (or "Jane" or "Joe"), while the Target executable is given the name "RT Bob" (or "Jane" or "Joe"). The three .RTEXE files are copied to the Target and placed in the Startup folder, C:\ni-rt\startup.
Now run one of the Host executables. It does the following:
FTP a copy of C:\ni-rt.ini from the Target to itself.
Get the name of the Startup .RTEXE.
If it is the "appropriate" name (i.e. if the Host program is UI Bob.exe, the Remote should be RT Bob.rtexe), do nothing, as the Target is already running the right code.
Otherwise, we need to force the Target to run the correct Target code. We can do this by changing the Startup entry in the .INI file to the Remote code we need (for example, RT Bob.rtexe), then tell the Remote to Reboot. When it comes back, it will be running the appropriate RT code.
The Host now goes ahead and tries to connect to the Remote. If a connection cannot be established (for example, the Remote code might have stopped), a Reboot of the Remote might fix things up.
Short of trying to write a single enormous program that encompasses every experimental scenario and situation (i.e. have a big Case Statement with a Bob, Jane, or Joe "choice", and a single executable that had everyone's code in it), this seemed to be a fairly simple way to have the robustness of compiled executables on both the Host and Remote machines, yet maintain the flexibility to let the (non-LabVIEW-guru) User choose which executable to run.
I haven't fully deployed this system -- I'm currently at "Proof-of-Concept" stage, but I've got the various "pieces" working. Does this seem like a sensible appropach? Are there other, simpler, ways to accomplish this?
Bob SchorHey Bob.
So I assume you're -completely- working with built executables? You're not going to work in the editor environment to modify your projects at all?
If this is the case, then having a generic deployment phase at the beginning of the executable (with a "setting up hardware for your app" splash screen) isn't a bad idea -
Check the binary on the target, ensure it matches the binary you have on the host machine (in case you ever decide to update).
If they don't match, FTP the new file down to replace the old one.
FTP the ni-rt.ini file, ensure the startup exe is enabled and is pointing to the correct location.
If it's not enabled or not pointing to the correct startup file, modify the .INI file and FTP back to the target.
If you had to update the INI file, ask target to reboot itself. Wait 30 seconds, and wait for target to become available again.
Connect to the target. If you cannot connect, reboot target. If the target comes back and you still cannot connect to the app, notify user.
That's almost exactly how we handle installation and deployment via MAX.
The big assumption here is that the built executables were all built with the same version of LabVIEW Real-Time. If not, you'd need a system replication step in there to make sure the proper version of LabVIEW is on the target before launching the built .rtexe.
-Danny -
Our problem is that we currently use a 2D array to store CAN data on a Real-time Target. The array is 20 elements of 3 byte elements as so:
0 1 2
0 [byte] [byte] [byte]
19 [byte] [byte] [byte]
These values are passed between a Deterministic Timed (DT) loop where they are set and a Non-Deterministic Timed (NDT) loop where they are read and passed into a Network Published Shared Variable (NPSV) for communication across the network to a Host PC. I have insrted an image for illustration, pardon the size.
Currently to pass the data between the DT and NDT loop we are using a Global Variable (GV). To improve the system we have attempted to replace these GVs with Single Process Shared Variables (SPSV) with an RT FIFO enabled.
To create the shared variable I simply right clicked the GV of interest and selected create Shared Variable Node form the drop downs. At this point LabVIEW presented me with a 2D NPSV within a new Library hosted on the RT Target. I then selected this new NPSV from the Project, changed it to a SPSV, and enabled a single element FIFO. This variable was initialized with a default value for the size described above and then used in our code for the DT to NDT communication, and conversion to a corresponding NPSV for sending to the Host.
When I went to run the code I noticed that the variable was in fact 2D, however its size was only 2 elements of three bytes each, in other words only two of the row indices were populated and the other appeared as uninitialized. in addition, this data had no resemblance to the set initilazation value. This was also how the variable was presented on the host side of the network after tranfer into a NPSV.
The peculiar part is that If I change this SPSV to a NPSV and then try to change it back, I receive an error saying the type is not supported for SPSV with an RT FIFO enabled. I have to disable the FIFO (which defeats the entire purpose) in order to successfully compile! I am unclear as to what is the bug in this case. Should I not be allowed to create the original 2D SPSV with a single element RT FIFO enabled without receiving an error? Or if this is okay how do I fix the problems associated with the variable after being allowed to create it?
I have found the following discussion in which a user states “The only limitations for custom controls is the ability to use it with RT FIFO enabled on a network-published shared variable”. Is this also true for SPSV? I have not found any documentation explicitely stating this for SPSV, though it is stated for the NPSVs.Martin,
RT FIFOs don't support Multi-Dimensional Arrays, which would corroborate the issues you're seeing. You can break up the 2D array into 1D arrays by reshaping the array, then you'll be able to use the RT FIFO enabled variable, just set the array size to the total number of elements (20*3 = 60).
You can also pass the 2D array via pre-allocated queue, or using a Functional Global. We have a reference example for a circular buffer using Functional Globals here. -
OK, more on the non-standard behavior of Image Controls (in LV 2009 SP1 at least)...
Having had to deal with the fact that one cannot detect a user right click in an Image Control, I figured that maybe I could at least build my own shortcut menu (the one that pops up when you right-click on an object). Not such luck without loosing some functionalities.
If you do so, you loose most items that are available by default at runtime (these are called the application items for any other controls):
- Palette
- Save Image...
- Clear ROI
- Zoom to Fit
I could rebuild all these functionalities in my custom menu, but:
1) why should I have to do that?
2) why do the items above not appear when one opens the default run-time shortcut menu? They do appear at run-time!
3) why do ALL other shortcut menu items available at edit time (some of which could be handy at run-time) not appear when one opens the default run-time shortcut menu?
4) At run-time, none of the menu items listed above are returned in the event structure when polling the Shortcut Menu Selection events (either App or User). Why????
Thanks for reading.VTHokie wrote:
Hi Xavier,
You can keep an eye out for CAR numbers in the known issues lists as they are published with software patches and releases, but especially in the bug fixes lists to see if a specific CAR has been remedied in that release.
- Greg J
Greg, neither of those lists contain references to issues within Vision Development Module...
If you are looking for a similar style list for Vision, the only location these are currently published is in the release notes for each release, such as here:
http://ftp.ni.com/support/softlib/vision/Vision%20Development%20Module/2010/readme.html
Also, I found reference to a VDM-specific known issues list here:
http://zone.ni.com/devzone/cda/tut/p/id/11942
Eric -
Error run time DYNPRO_FIELD_CONVERSION
I have a dump:
Errore run-time DYNPRO_FIELD_CONVERSION
Verific. il 28.11.2007 h 02:12:16
A conversion error occurred.
Causa dell'errore
The current screen processing was terminated, since a situation
occurred from which it could not continue processing.
This is probably due to an error in the current screen of the ABAP
program.
Possibili soluzioni
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Analisi errori
The program flow was interrupted and could not be resumed.
Program "SAPMM06B" tried to display fields on screen 0106. However, an
error occurred while this data was being converted.
Indic. per la correzione
A conversion error occurred while the program was trying to
display data on the screen.
The ABAP output field and the screen field may not have the
same format.
Some field types require more characters on the screen than
in the ABAP program. For example, a date field on a screen needs
two characters more than it would in the program. When attempting to
display the date on the screen, an error will occur that triggers the
error message.
Screen name.............. "SAPMM06B"
Screen number............ 0106
Screen field............. "EBAN-MENGE"
Error text............... "FX015: Sign lost."
Further data:
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
It is probably not possible to eliminate the system error
with ABAP alone.
If you have access to SAPnet, you can search for a relevant note
using the following keywords:
"DYNPRO_FIELD_CONVERSION" " "
"SAPMM06B" bzw. "MM06BO0R_RM06B-EPSTP"
"RM06B-EPSTP"
Ambiente sistema
SAP Release.............. "620"
Application server....... "assapoa"
Network address.......... "10.58.19.23"
Operating system......... "AIX"
Release.................. "5.2"
Hardware type............ "00CB585E4C00"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 26
Short dump setting....... "full"
Database server.......... "ars005sapdb"
Database type............ "ORACLE"
Database name............ "PRD"
Database owner........... "SAPR3"
Character set............ "it_IT.ISO8859-1"
SAP kernel............... "640"
Created on............... "Jul 16 2006 20:40:53"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "139"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Utente, transazione.....
Client.............. 300
User................ "CONSULENTI"
Language key........ "I"
Transaction......... "ME52 "
Program............. "SAPMM06B"
Screen.............. "SAPMM06B 0106"
Screen line......... 26
Informazioni punto di interr.
The termination occurred in the ABAP program "SAPMM06B" in "RM06B-EPSTP".
The main program was "SAPMM06B ".
The termination occurred in line 14 of the source code of the (Include)
program "MM06BO0R_RM06B-EPSTP"
of the source code of program "MM06BO0R_RM06B-EPSTP" (when calling the editor
140).
The program "SAPMM06B" was started as a background job.
Errore verificatosi durante un'elaborazione Batch-Input
Dettaglio cd. sorgente
000010 *eject
000020 *----
000030 * Positionstyp aufbereiten *
000040 *----
000050 MODULE RM06B-EPSTP OUTPUT.
000060
000070 CALL FUNCTION 'ME_ITEM_CATEGORY_OUTPUT'
000080 EXPORTING
000090 PSTYP = EBAN-PSTYP
000100 IMPORTING
000110 EPSTP = RM06B-EPSTP
000120 PTEXT = T163Y-PTEXT.
000130
ENDMODULE.
Contenuto campi sistema
Cmpo SY Contenuto.................... Cmpo SY Contenuto....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 1
SY-FDPOS 1 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY VU
SY-UCOMM
SY-TITLE Richiesta d'acquisto mod.: Riepilogo pos.
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Richiami/eventi attivi
N..... Tipo........ Nome..........................
Programma
Include Riga
Classe
1 MODULE (PBO) RM06B-EPSTP
SAPMM06B
MM06BO0R_RM06B-EPSTP 14
Variabili selezionate
1 MODULE (PBO) RM06B-EPSTP
SAPMM06B
MM06BO0R_RM06B-EPSTP 14
DIEN DIEN
4444
495E
EBAN-PSTYP 0
3
0
LIM LIM
4442
C9D0
RM06B-EPSTP
2
0
POTE TXP
5552
4800
T163Y-PTEXT Standard
57666676222222222222
341E4124000000000000
Chiamate applicazione
Il dump non riporta informazioni relative
Informazioni applicazione
Il dump non riporta informazioni relative
Note interne
The termination occurred in the function "dynpconv.c" of the SAP
Basis System, specifically in line 701 of the module
"//bas/640_REL/src/krn/dynp/dybas.c#4".
The internal operation just processed is "ENDM".
The internal session was started at 20071128021215.
Application server....... "assapoa"
Network address.......... "10.58.19.23"
Operating system ........ "AIX"
Release.................. "5.2"
Hardware type............ "00CB585E4C00"
Database server.......... "ars005sapdb"
Database type............ "ORACLE"
Database name............ "PRD"
Database user ID......... "SAPR3"
Rich. attivi nel nucleo SAP
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = unlimited
=> Core limit = 1073741312
=> File size limit = unlimited
=> Heap address = 0x11dd952a0
=> Stack address = 0xfffffffffffa920
=> Stack low = 0xfffffffffffa920
=> Stack high = 0xffffffffffff910
=> Stack Trace:
AixStack() at 0x1000206bc
CTrcStack2() at 0x1000207b4
rabax_CStackSave__Fv() at 0x1001520d4
ab_rabax() at 0x10014ef04
dyHandleError() at 0x1005a6850
dypcnvoXt() at 0x100cbd6cc
dynplend() at 0x1010cf268
dynpmcal() at 0x1010c6f60
dynppbo0() at 0x1010c5134
dynprctl() at 0x1010ce40c
dynpen00() at 0x100bd0c30
Thdynpen00() at 0x1000a1f7c
TskhLoop() at 0x1000a5298
tskhstart() at 0x1000bb0d8
DpMain() at 0x101579ca0
nlsui_main() at 0x10154d428
__start() at 0x1000002fc
!!! Invalid stack address encountered: 0x0
!!! Stack corrupted.
Lista dei programmi ABAP in oggetto
Tipo
Programma
DataGen Ora
Dim.car.
Prg
SAPMM06B
25.09.2007 16:07:55
514048
Prg
SAPMSSYD
05.06.2002 17:09:33
16384
Prg
SAPFSYSCALLS
14.02.2002 14:22:47
6144
Typ
T160
12.05.1997 15:22:15
2048
Prg
SAPFMMEX
18.11.2007 09:34:59
177152
Typ
TSTCT
14.02.1998 14:31:34
2048
Typ
TMED
27.08.1994 21:59:16
2048
Typ
TPRG
14.02.1998 14:06:12
2048
Typ
T160D
11.02.2000 14:20:36
5120
Typ
T160V
14.05.1998 22:44:11
6144
Typ
T168T
28.08.1997 09:05:04
2048
Prg
SAPLMEXF
18.11.2007 09:35:00
166912
Typ
T162
02.10.2001 13:56:13
2048
Prg
SAPLSTUP
17.06.2004 12:05:43
65536
Prg
SAPLCNDP
17.06.2004 15:06:47
163840
Prg
SAPFGUICNTL
09.01.2003 17:18:52
20480
Prg
SAPLOLEA
17.06.2004 15:12:42
78848
Prg
SAPLSGUI
09.01.2003 17:15:12
31744
Prg
SAPLSTTM
17.06.2004 15:08:30
75776
Prg
SAPLSBDC
07.01.2003 18:31:25
38912
Prg
SAPLSFES
17.06.2004 15:15:58
174080
Prg
SAPLURFC
17.06.2004 14:25:28
16384
Prg
SAPLSPLUGIN
14.02.2002 14:22:48
6144
Typ
SWCBCONT
15.11.2000 17:55:11
3072
Typ
OLE_VERBS
04.04.1995 16:02:20
2048
Typ
OLE_PA
04.04.1995 16:02:19
2048
Prg
SAPLSCNT
14.02.2002 14:22:47
24576
Prg
SAPSHDTV
17.06.2004 11:46:16
28672
Typ
EBANW
17.06.2004 15:55:16
21504
Prg
CL_CONTEXTFIELD_MM============CP
25.09.2007 16:07:49
9216
Prg
/1BCDWBEN/SAPLMEN0000
18.11.2007 09:35:16
237568
Prg
SAPLSENA
17.06.2004 14:19:40
28672
Typ
EBAN
13.11.2006 11:19:59
20480
Prg
CL_PROCESS_STATE_MM===========CP
25.09.2007 16:07:50
16384
Prg
SAPLSWUG
17.06.2004 14:22:25
53248
Typ
SWCONT
04.04.1995 16:18:01
2048
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Typ
SWOTOBJID
04.05.1995 15:20:52
2048
Typ
SWHACTOR
04.04.1995 16:18:07
2048
Prg
CL_GOS_MANAGER================CP
11.04.2001 13:02:00
17408
Prg
CL_GOS_VIEW_MANAGER===========CP
24.01.2002 20:31:22
22528
Typ
SIBFLPOR
15.11.2000 17:53:54
2048
Typ
SGOS_MVOBJ
24.07.2001 09:18:06
3072
Typ
BORIDENT
28.08.1997 08:38:50
2048
Prg
SAPLSUU1
17.06.2004 15:13:06
165888
Typ
USR02
17.06.2004 15:05:37
7168
Typ
USREFUS
07.01.2003 18:24:17
2048
Typ
SIBFLPORB
15.11.2000 17:53:55
2048
Prg
CL_GOS_TOOLBOX_MODEL==========CP
17.06.2004 15:04:37
38912
Typ
SGOS_MODL
24.07.2001 09:18:05
4096
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
SAPLSWOR
17.06.2004 15:08:55
270336
Typ
SWOTRI
03.01.1996 15:29:13
2048
Typ
SWOTRETURN
20.08.1998 10:59:29
3072
Prg
SAPLSWOH
14.02.2002 14:22:48
7168
Typ
SWOTENV
11.02.2000 14:20:34
4096
Typ
TOJTD
15.11.1995 03:08:46
2048
Prg
SAPLRHS0
14.02.2002 14:22:47
11264
Prg
SAPLSDIFRUNTIME
17.06.2004 14:20:44
82944
Typ
DFIES
09.11.2000 14:07:05
8192
Typ
X031L
15.11.2000 18:03:28
5120
Prg
SAPLSDNT
17.06.2004 12:06:43
199680
Prg
SAPLSUGS
21.11.2002 10:20:02
29696
Typ
TOJTD
15.11.1995 03:08:46
2048
Typ
TOJTB
14.02.1998 14:02:55
8192
Typ
SWOTLI
04.04.1995 17:30:59
2048
Typ
T100
28.08.1997 09:04:45
2048
Prg
CL_EXITHANDLER================CP
17.06.2004 15:04:37
26624
Prg
CL_ABAP_TYPEDESCR=============CP
17.06.2004 14:19:33
21504
Prg
CL_ABAP_ELEMDESCR=============CP
17.06.2004 14:19:13
18432
Prg
CL_ABAP_DATADESCR=============CP
17.06.2004 14:19:13
14336
Prg
CL_ABAP_REFDESCR==============CP
17.06.2004 14:19:33
16384
Prg
CL_ABAP_STRUCTDESCR===========CP
17.06.2004 14:19:33
19456
Prg
CL_ABAP_COMPLEXDESCR==========CP
17.06.2004 14:19:13
13312
Prg
CL_ABAP_TABLEDESCR============CP
17.06.2004 14:19:33
17408
Prg
CL_ABAP_CLASSDESCR============CP
17.06.2004 14:19:33
23552
Prg
CL_ABAP_OBJECTDESCR===========CP
17.06.2004 14:19:33
25600
Prg
CL_ABAP_INTFDESCR=============CP
17.06.2004 14:19:13
19456
Prg
CL_ABAP_SOFT_REFERENCE========CP
29.03.2001 16:42:12
7168
Prg
CL_ABAP_REFERENCE=============CP
14.02.2002 14:22:46
6144
Prg
IF_EX_GOS_SRV_SELECT==========IP
04.12.2000 16:22:18
4096
Prg
%_CABAP
07.01.2003 18:31:23
23552
Typ
SXS_INTER
30.11.1998 15:55:16
2048
Prg
SAPLSEXV
17.06.2004 15:04:40
106496
Prg
CL_BADI_FLT_DATA_TRANS_AND_DB=CP
17.06.2004 15:04:37
33792
Typ
SXS_ATTR
20.08.2001 12:23:27
4096
Typ
V_EXT_ACT
09.11.2000 14:27:05
2048
Typ
SXC_EXIT
09.11.2000 14:23:43
2048
Prg
CL_EX_GOS_SRV_SELECT==========CP
17.06.2004 15:04:37
13312
Prg
%_CSXRT
17.06.2004 15:04:37
11264
Prg
CL_EXIT_MASTER================CP
17.06.2004 15:04:37
13312
Typ
V_EXT_IMP
09.11.2000 14:27:05
2048
Typ
V_EXT_IMP
09.11.2000 14:27:05
2048
Prg
SAPLBDLS
17.06.2004 11:45:48
176128
Typ
T000
11.09.1997 10:17:18
4096
Typ
SWOTRTIME
14.02.1998 10:19:46
3072
Prg
%_CSWOB
14.02.2002 14:22:46
13312
Typ
SWOTINVOKE
14.02.1998 10:18:40
6144
Typ
SWOTLV
04.12.2000 14:59:45
10240
Prg
SAPLSWCD
17.06.2004 15:06:55
78848
Prg
RBUS2105
13.11.2006 11:20:02
57344
Prg
CL_GOS_PUBLICATION============CP
13.11.2000 16:31:37
15360
Prg
SAPLSGOSHIST
17.06.2004 14:23:50
46080
Typ
EBKN
16.06.2004 13:09:57
9216
Typ
T161
16.06.2004 13:14:35
5120
Typ
T161T
14.02.1998 10:55:58
2048
Typ
CMMDA
18.09.2001 10:02:31
4096
Prg
SAPLMMDA
04.09.2006 11:00:54
65536
Typ
TWLAD
13.08.1997 14:04:45
2048
Typ
TTXID
27.08.1999 17:40:33
3072
Prg
SAPLSTXD
17.06.2004 15:06:22
347136
Typ
STEXTNAME
18.09.2001 10:03:52
1024
Typ
STXDRID
26.02.1999 14:48:42
2048
Typ
STXDRLANG
26.02.1999 14:48:42
2048
Typ
STXDRNAME
26.02.1999 14:48:42
2048
Typ
STXDROBJ
26.02.1999 14:48:42
2048
Typ
THEAD
09.11.2000 14:15:08
6144
Prg
CL_ABAP_CHAR_UTILITIES========CP
07.01.2003 18:31:23
11264
Typ
STXH
17.06.2004 14:15:46
6144
Typ
TCATALOG
25.05.1998 12:19:20
3072
Typ
T168F
27.05.1992 20:16:27
3072
Typ
T168
27.05.1992 17:53:38
3072
Prg
SAPLMECCP
25.09.2007 16:07:53
39936
Prg
CL_BADI_MM====================CP
08.01.2003 16:43:11
9216
Prg
%_CCXTAB
14.02.2002 14:22:46
6144
Prg
SAPLEINH
25.09.2007 16:07:53
56320
Typ
T001W
16.06.2004 13:14:17
9216
Prg
SAPLVDAT
19.02.2002 12:59:51
25600
Typ
T163Y
28.08.1997 09:05:01
2048
Prg
SAPCNVE
14.02.2002 14:22:47
6144
Prg
SAPLOMCV
17.06.2004 10:54:26
16384
Prg
CL_EX_BADI_MATN1==============CP
17.06.2004 10:27:52
22528
Prg
IF_EX_BADI_MATN1==============IP
17.06.2004 10:53:59
4096
Typ
TMCNV
24.02.1999 03:33:25
3072
Typ
RM06B
17.06.1998 03:23:02
10240
Lista tabelle interne
Il dump non riporta informazioni relative
Indice delle tabelle applicative
Programma
Nome................ Contenuto..1.......2........3........4........5....+....
SAPMM06B
SYST |00000000000x010000000000000000
EBAN |300001100895000010NB B NB 1 Elena Varett20071
*EBAN | 00000 00000
EBKN | 0000000 00000000 000000x0C
AEBAN |3000011008950NB BBEUR |
EBANW |300001100895000010NB B NB 1 Elena Varett20071
RM06B | 00000000000000000010 00
*RM06B | 00000000000000000000 00
RM06E | 000000000000000 00000000 00000
TPRG |300IW2Formato settimana Sett. |
T001W |3006 PIATTAFORMA DI LEINI' 6 CEDI6 0000000
T023 |
T024 |
T160 |300ME52 VB B |
T160V |300C1XX A XX X X |
T161 |300BNB 000100102NBB NB 00000
T161T |300INB BRichiesta d'acquisto|
T168 |300B AB *** 1 106 0x0C0x0C0x0C0x0C|
T168F |300B AB XXX |
T168T |300IB0106002 |
TTXID |EBAN B04 X
T163K | |
T163Y | Standard |
T001L |
T160D | XXXXXXXXXXXXXXXXXXXXXX
T161E | |
SAPFMMEX
TMED |300BB |
SAPLMEXF
T161 |300BNB 000100102NBB NB 00000
T162 |300PT0B ...................................
SAPLSUU1
USR02 |300CONSULENTI ÷x9Fw'x97[æÆ0000000000000000A
USREFUS |300CONSULENTI
SAPLSWOR
TOJTB |BUS2105 XI RBUS2105
SWOTLV |BUS2105 EXISTENCECHECK M
TOJTD | |
SAPLBDLS
T000 |300Mandante produzione Arenzano EUR
SAPMM06B
*RM06E | 000000000000000 00000000 00000
MARA | 00000000 00000000
T006 | 00 00000000000000x0C 0
SAPLVDAT
TPRG |300IW2Formato settimana Sett. |
SAPLOMCV
TMCNV |300MATCONV 0x120000000x12
Directory delle tabelle applicative (inf. di gestione)
Programma
Nome.......................... tempo..........lungh....
SAPLOMCV
SYST 20010612125650 00002404
EBAN 20061113111959 00000892
*EBAN 20061113111959 00000892
EBKN 00000421
AEBAN 20000323224119 00000027
EBANW 00000896
RM06B 20000323224119 00000529
*RM06B 20000323224119 00000529
RM06E 20020124202505 00001154
TPRG 20000323231030 00000032
T001W 20040617141548 00000338
T023 20040616131428 00000102
T024 20040616131429 00000352
T160 00000035
T160V 00000050
T161 20040616131435 00000095
T161T 00000029
T168 00000035
T168F 00000044
T168T 00000013
TTXID 00000058
T163K 20000323230840 00000023
T163Y 00000026
T001L 20000323230832 00000069
T160D 00000069
T161E 20000323230840 00000025
SAPFMMEX
TMED 00000010
SAPLMEXF
T161 00000095
T162 00000234
SAPLSUU1
USR02 00000226
USREFUS 00000067
SAPLSWOR
TOJTB 00000453
SWOTLV 00000701
TOJTD 00000033
SAPLBDLS
T000 00000107
SAPMM06B
*RM06E 20020124202505 00001154
MARA 20071118093457 00001118
T006 20001109142345 00000080
SAPLVDAT
TPRG 00000032
SAPLOMCV
TMCNV 00000062
Blocchi di contr. CONT ABAP
Include Riga Codice sorg.
Ind. Nome FI Co Par01 Par2. Par3. Par4. Tab.
MM06BO0R_RM06B-EEIND 25 EXIT.
2502 BRAX 00
MM06BO0R_RM06B-EEIND 27 ENDSELECT.
2503 BRAX 00
2504 SQLS 08
MM06BO0R_RM06B-EEIND 31 ENDMODULE.
2505 ENDM 00
2506 -
MM06BO0R_RM06B-EPSTP 7 CALL FUNCTION 'ME_ITEM_CATEGOR
2507 FUNC 00
2508 FUNC 00
2509 PAR2 02 0336
2511 FUNC 10
2512 PAR2 01 03B9
2514 PAR2 01 03BA
2516 FUNC FF
MM06BO0R_RM06B-EPSTP 14 ENDMODULE.
>>>>> ENDM 00
2518 -
MM06BO0V_VRTKZ 6 CASE EBAN-VRTKZ.
2519 BREL 04
MM06BO0V_VRTKZ 7 WHEN '1'.
2520 when 00 02 0090
2522 BRAN 02
2523 BRAX 00
MM06BO0V_VRTKZ 8 RM06B-MKNTW = '3 '. "3 Nachkom
2524 MOVL 00 02 0136
MM06BO0V_VRTKZ 9 WHEN '2'.
2526 BRAX 00
Fine dell'analisi err. run-time
Help me.
Thank youHello Maurizio,
Thre screen field EBAN-MENGE is unable to handle a sign along with the value.
Regards,
Ammey Kesarkar -
How to change object background color on java run time
Hi,
I create object loading program. my problem is run time i change object background color using color picker. i select any one color of color picker than submit. The selecting color not assign object background.
pls help me? How to run time change object background color?
here follwing code
import com.sun.j3d.loaders.objectfile.ObjectFile;
import com.sun.j3d.loaders.ParsingErrorException;
import com.sun.j3d.loaders.IncorrectFormatException;
import com.sun.j3d.loaders.Scene;
import java.applet.Applet;
import java.awt.*;
import java.awt.event.*;
import com.sun.j3d.utils.applet.MainFrame;
import com.sun.j3d.utils.universe.*;
import javax.media.j3d.*;
import javax.vecmath.*;
import java.io.*;
import com.sun.j3d.utils.behaviors.vp.*;
import java.net.URL;
import java.net.MalformedURLException;
import java.awt.Graphics ;
import javax.swing.*;
public class ObjLoad1 extends Applet implements ActionListener
private boolean spin = false;
private boolean noTriangulate = false;
private boolean noStripify = false;
private double creaseAngle = 60.0;
private URL filename = null;
private SimpleUniverse u;
private BoundingSphere bounds;
private Panel cardPanel;
private Button Tit,sub;
private CardLayout ourLayout;
private BorderLayout bl;
Background bgNode;
BranchGroup objRoot;
List thelist;
Label l1;
public BranchGroup createSceneGraph()
BranchGroup objRoot = new BranchGroup();
TransformGroup objScale = new TransformGroup();
Transform3D t3d = new Transform3D();
t3d.setScale(0.7);
objScale.setTransform(t3d);
objRoot.addChild(objScale);
TransformGroup objTrans = new TransformGroup();
objTrans.setCapability(TransformGroup.ALLOW_TRANSFORM_WRITE);
objTrans.setCapability(TransformGroup.ALLOW_TRANSFORM_READ);
objScale.addChild(objTrans);
int flags = ObjectFile.RESIZE;
if (!noTriangulate) flags |= ObjectFile.TRIANGULATE;
if (!noStripify) flags |= ObjectFile.STRIPIFY;
ObjectFile f = new ObjectFile(flags,(float)(creaseAngle * Math.PI / 180.0));
Scene s = null;
try {
s = f.load(filename);
catch (FileNotFoundException e) {
System.err.println(e);
System.exit(1);
catch (ParsingErrorException e) {
System.err.println(e);
System.exit(1);
catch (IncorrectFormatException e) {
System.err.println(e);
System.exit(1);
objTrans.addChild(s.getSceneGroup());
bounds = new BoundingSphere(new Point3d(0.0,0.0,0.0), 100.0);
if (spin) {
Transform3D yAxis = new Transform3D();
Alpha rotationAlpha = new Alpha(-1, Alpha.INCREASING_ENABLE,0,0,4000,0,0,0,0,0);
RotationInterpolator rotator = new RotationInterpolator(rotationAlpha,objTrans,yAxis,0.0f,(float) Math.PI*2.0f);
rotator.setSchedulingBounds(bounds);
objTrans.addChild(rotator);
//Background color setting
Color3f bgColor = new Color3f(100,200,230);
bgNode = new Background(bgColor);
bgNode.setApplicationBounds(bounds);
objRoot.addChild(bgNode);
return objRoot;
private void usage()
System.out.println("Usage: java ObjLoad1 [-s] [-n] [-t] [-c degrees] <.obj file>");
System.out.println("-s Spin (no user interaction)");
System.out.println("-n No triangulation");
System.out.println("-t No stripification");
System.out.println("-c Set crease angle for normal generation (default is 60 without");
System.out.println("smoothing group info, otherwise 180 within smoothing groups)");
System.exit(0);
} // End of usage
public void init() {
if (filename == null) {
try {
URL path = getCodeBase();
filename = new URL(path.toString() + "./galleon.obj");
catch (MalformedURLException e) {
System.err.println(e);
System.exit(1);
//setLayout(new BorderLayout());
//setLayout(new GridLayout(5,0));
//setLayout(new CardLayout());
//setLayout(new FlowLayout(FlowLayout.LEFT, 5, 5));
GraphicsConfiguration config = SimpleUniverse.getPreferredConfiguration();
Canvas3D c = new Canvas3D(config);
add(c);
BranchGroup scene = createSceneGraph();
u = new SimpleUniverse(c);
ViewingPlatform viewingPlatform = u.getViewingPlatform();
PlatformGeometry pg = new PlatformGeometry();
Color3f ambientColor = new Color3f(45,27,15);
AmbientLight ambientLightNode = new AmbientLight(ambientColor);
ambientLightNode.setInfluencingBounds(bounds);
pg.addChild(ambientLightNode);
Color3f light1Color = new Color3f(111,222,222);
Vector3f light1Direction = new Vector3f(1.0f, 1.0f, 1.0f);
Color3f light2Color = new Color3f(1.0f, 1.0f, 1.0f);
Vector3f light2Direction = new Vector3f(-1.0f, -1.0f, -1.0f);
DirectionalLight light1 = new DirectionalLight(light1Color, light1Direction);
light1.setInfluencingBounds(bounds);
pg.addChild(light1);
DirectionalLight light2 = new DirectionalLight(light2Color, light2Direction);
light2.setInfluencingBounds(bounds);
pg.addChild(light2);
viewingPlatform.setPlatformGeometry(pg);
viewingPlatform.setNominalViewingTransform();
if (!spin) {
OrbitBehavior orbit = new OrbitBehavior(c,OrbitBehavior.REVERSE_ALL);
BoundingSphere bounds = new BoundingSphere(new Point3d(0.0, 0.0, 0.0), 100.0);
orbit.setSchedulingBounds(bounds);
viewingPlatform.setViewPlatformBehavior(orbit);
u.addBranchGraph(scene);
public ObjLoad1(String[] args) {
if (args.length != 0) {
for (int i = 0 ; i < args.length ; i++) {
if (args.startsWith("-")) {
if (args[i].equals("-s")) {
spin = true;
} else if (args[i].equals("-n")) {
noTriangulate = true;
} else if (args[i].equals("-t")) {
noStripify = true;
} else if (args[i].equals("-c")) {
if (i < args.length - 1) {
creaseAngle = (new Double(args[++i])).doubleValue();
} else usage();
} else {
usage();
} else {
try {
if ((args[i].indexOf("file:") == 0) ||
(args[i].indexOf("http") == 0)) {
filename = new URL(args[i]);
else if (args[i].charAt(0) != '/') {
filename = new URL("file:./" + args[i]);
else {
filename = new URL("file:" + args[i]);
catch (MalformedURLException e) {
System.err.println(e);
System.exit(1);
public void actionPerformed(ActionEvent e)
if (e.getSource() == Tit)
//Color Picker tool
Color c1 = JColorChooser.showDialog(((Component)e.getSource()).getParent(),"Zaxis Color Picker", Color.blue);
cardPanel.setBackground(c1);
objRoot.removeChild(bgNode);
int a = c1.getRed();
int b = c1.getBlue();
int c = c1.getBlue();
System.out.println(a);
System.out.println(b);
System.out.println(c);
Color3f ccc = new Color3f(a,b,c);
bgNode.setApplicationBounds(bounds);
objRoot.addChild(bgNode);
else
System.out.println("mathi");
public ObjLoad1()
Tit = new Button("BG Color");
sub = new Button("Object Color");
cardPanel = new Panel();
cardPanel.add(Tit);
cardPanel.add(sub);
//cardPanel.add(l1);
//cardPanel.add(thelist);
sub.addActionListener(this);
Tit.addActionListener(this);
// thelist.addActionListener(this);
//setLayout for applet to be BorderLayout
this.setLayout(new BorderLayout());
//button Panel goes South, card panels go Center
this.add(cardPanel, BorderLayout.SOUTH);
//this.add(cardPanel, BorderLayout.CENTER);
this.setVisible(true);
public void destroy() {
public static void main(String[] args) {
new MainFrame(new ObjLoad1(args),400, 400);hi,
i am using setColor(Color3f color) method
like
if (e.getSource() == Tit)
Color c1 = JColorChooser.showDialog(((Component)e.getSource()).getParent(),"Zaxis Color Picker", Color.blue);
bgColor = new Color3f(c1);
System.out.println(bgColor.get());
bgNode.setColor(bgColor);
bgNode.setApplicationBounds(bounds);
objRoot.addChild(bgNode);
but error will be displayed
like
javax.media.j3d.CapabilityNotSetException: Background: no capability to set color
at javax.media.j3d.Background.setColor(Background.java:307)
at ObjLoad1.actionPerformed(ObjLoad1.java:230)
at java.awt.Button.processActionEvent(Unknown Source)
at java.awt.Button.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
pls help me
Maybe you are looking for
-
Main VI stops fucntioning after i open and close a subvi from an event structrue.
Hi, I am trying to open a pop up vi from an event. I have been struggling with this for a while now. When i open a pop up vi and close it, the main vi stops running properly. I have narrowed it down to the fact that the event which calls the subvi ne
-
Unable to create OSB project in OEPE 11.1.1.6.1
Hi, I have installed weblogic server 10.3.4 with OEPE 11.1.1.6.1 (wls1034_oepe111161_win32.exe) on Windows XP machine. There after I installed Oracle Service Bus 11.1.1.4.0 (ofm_osb_generic_11.1.1.4.0_disk1_1of1.zip). When I open OEPE I do not find t
-
I've created a simple PDF form and an interface for it. I've binded the context to a few text fields and everything seems to work as intended. The problem I'm having at the moment is that I would be requiring the short description of the data value,
-
Why do songs leave my iTunes library?
Here's an example of what I run into all too frequently. I want to know why it happens, and how I can prevent it. A repairman had never heard of The Inkspots. Amazing as it is to me, I've run into this before from people who should know better. Anywa
-
Declined work repository connection
Hello Everyone, We installed a new ODI instance but the repositories were same. Now we want a separate repository of the new ODI. We have a valid/active database in Oracle which I want to use as the new repository. I went ahead adding that database a