Backspace non funziona in Genexus Win JAVA

Salve a tutti!
Io sono Cloud e collaboro anch'io a questo Blog.

Ieri ho riscontrato un piccolo difetto in un'applicazione di Genexus di tipo win su piattaforma JAVA:
In tutti i text edit (ovvero quei controlli che permettono l'immissione di testo da tastiera) il tasto "backspace" non ha alcun effetto, quindi per poter cancellare del testo errato è necessario utilizzare il tasto "canc" (o "del").
Qualcun'altro di voi ha riscontrato lo stesso problema?
Ma soprattutto, qualcuno di voi l'ha risolto?

Un saluto a tutti da Cloud............

Js Cook Menu rel. 2.02

JsCookMenu 2.02

Overview

* Different Menu Orientations
* Different Themes in One Page
* Applying Background Images
* Animation
* Custom Actions
* Custom Actions without Closing Menu Automatically
* Click to Open Submenus
* Build Menu Using HTML
* JavaScript Function Link

Different Menu Orientations
Not all themes support all the orientations. Please check each individual's documentation.

* 'hbr'
Scripts Download Forums SourceForge
JSCookMenu
JSCookTree
* 'hbl'
Scripts Download Forums SourceForge
JSCookMenu
JSCookTree
* 'hur'
Scripts Download Forums SourceForge
JSCookMenu
JSCookTree
* 'hul'
Scripts Download Forums SourceForge
JSCookMenu
JSCookTree
* 'vbr'
Scripts
Download
Forums
SourceForge
JSCookMenu
JSCookTree
* 'vbl'
Scripts
Download
Forums
SourceForge
JSCookMenu
JSCookTree
* 'vur'
Scripts
Download
Forums
SourceForge
JSCookMenu
JSCookTree
* 'vul'
Scripts
Download
Forums
SourceForge
JSCookMenu
JSCookTree

Different Themes

Here is just a brief overview of themes available.

* Office XP
Scripts Download Forums SourceForge
JSCookMenu
JSCookTree
* Internet Explorer
Scripts Download Forums SourceForge
JSCookMenu
JSCookTree
* Panel (background color has been changed to images in this demo)
Scripts
Download
Forums
SourceForge
JSCookMenu
JSCookTree
* MiniBlack
Scripts Download Forums SourceForge
JSCookMenu
JSCookTree

Applying Background Images

Well, you are aleady looking at it. The panel at left uses the Panel theme and I changed the background of submenu and made main menu, main menu items and sub menu items transparent. One doesn't have to change the style sheet, since in CSS, rules specified later can override previous settings. So, this is a quick way of modifying themes.
Toggle Code Display
Animation

It is possible to do animation with JSCookMenu as well, as the following example showing:
12
Toggle Code Display

Custom Action inside Menu

To create a custom menu item that doesn't use the default actions. One would do the following intead of the usual menu item node:

[_cmNoAction, 'HTML code']

In place of the HTML code, one needs to specify the complete TABLE cell/row information. There are three cases:

1. If it is used inside a horizontal main menu, the code is inside a table cell .
2. If it is used inside a vertical main menu, it must contain or codes that handle 3 table cells.
3. If it is used inside a submenu, it must contain or codes that handle 3 table cells.

Here is one example, having a palette selector inside a sub menu. The palette selector looks like:


Toggle Code Display

Now put the table inside the menu:
File Palette
Open
Save
Options




Toggle Code Display

Custom Actions without Closing Menu Automatically

The demo above has one limitation in that the menu mouse listener is automatically called to close the menu. Sometimes, such effects may not be desired, for instance in search boxes. Below are two demos how _cmNoClick instead of _cmNoAction can be used.

Here is a simple search box:
Toggle Code Display

Now put this search box inside a menu.
Search

Toggle Code Display

Usually the search result will change the content of this window, so it is not necessary to consider the closing of the menu. If needed, you can call "cmHideMenuTime ()" to close the current menu as the following example illustrates.
Search

Toggle Code Display

Click to Open Submenus

JSCookMenu 1.4 introduced a new feature that requires clicking to open sub menus, as per requests by many people. Currently, there are several behaviors possible for opening sub menus.

* 0: use default behavior specified in JSCookMenu.js
* 1: hover open in all cases (default in JSCookMenu.js)
* 2: click on main, hover on sub. In 2.0 and later, once a sub menu is opened, starts to open main sub menu with hover.
* 3: click open in all cases

You can either directly modify JSCookMenu.js and instantly make all your existing old theme properties to behave not like the default, or you can modify individual theme properties.
Heng Yuan's home
All Projects
Contact
YooLex
YooParse
CookMail
CookScript
CookSwing
JSCookTree
JSCookMenu
Threaded Mud Client
ChDay Chinese Web Counter
Bin2Obj
CXTerm
JavaScript Function Link

This demo is added because I am pretty much sick of being asked if this is possible or someone who do not know much about JavaScript or JSCookMenu claiming it could not be done.

The demo basically sets the windows status bar text. If you are using browsers like FireFox, you may not be able to see this text since by default it prevents JavaScripts from manipulating status bar text. The purpose is to prevent link spoofing.
Begin
Action
Toggle Code Display

Aggiornamento di Emule Pro 3

Dopo la notizia di Emule Pro Ultra 2 è uscita un nuova versione di Emule Pro Ultra 3 che noi sconsigliamo di installarla perchè è una leecher mod ovvero una versione di eMule modificata illegalmente che permette di scaricare senza condividere. Queste mod sono la rovina del mulo, dato che se le usassero tutti, nessuno scaricherebbe. Se continuate a ricevere messaggi di spam sul mulo che consigliano di scaricare Emule Pro Ultra 3 da parte di altri utenti potete usare il filtro anti spam.
Per filtrare i messaggi io uso questa riga:Your client has an infinite queueYour client is connecting toofastfastest download speedZambor 2eMule FXDI-Emule V.2.0l33cherinyour townultra2HyperMuleUltra3mod leecherDa copiare/incollare sotto opzioni, messaggi e commenti, Filtra messaggicontenenti..
Quindi lasciate perdere queste versioni e passate alla versione normale, che settata bene puo dare ottimi risultati!

Nuovo E-Mule Pro

E nata una nuova versione del mulo: Emule Pro Ultra 2 questa versione sembra gia dal nome destinata ad avere una nuova velocita con una nuova grafica, in effetti qualche cosa è cambitato anche se noi di freedomtech abbiamo provato questa versione e il nostro verdetto è:
lasciate perdere e tornate alla versione normale,meno problemi piu affidabilità, poi se volete un mulo diverso allora scaricate la mod morphXT 9.6(che uso anche io con la versione di eMule v0.47c e va benissimo) oppure la xtreme 5.4 …avrete comunque un mulo diverso graficamente ma nello stesso tempo un mulo funzionante.

XVI International GeneXus Meeting

In rete i materiali del Meeting che si trova questi giorni presso Artech sulla nuova release di GeneXus 9.0, la ROCHA.
Per il download dei materiali il link è:
http://www.gxtechnical.com/main/hevprgprogram.aspx?8,60,581,19

Il Primo SW per Debug in GeneXus

GeneXus "DebuGX Console" option.

As shown in the picture, the Console is divided in several sections: - Main Menu: It unfolds the available options. - Toolbar: The toolbar is below the Main Menu and it is has the following buttons (from left to right): Open, Save, Delete all the captured steps, Refresh the workspace, Step back, Step forward, Pause, Execute until the following breakpoint, Searcher, Delete all the breakpoints, Enable or disable all the breakpoints. - Objects browser: It shows all the objects specified by the DebuGX Specifier. - Properties: It shows the attribute / variable properties selected in the Objects browser. - Source code browser: It shows the selected object GeneXus code. - Watch list: It shows the selected attributes / variable values in execution. - Alerts: It shows the defined alerts. - Steps: It Shows the number of executed code lines with the possibility of moving backwards or forward.

Breakpoints and Alerts
--------------------------------------------------------------------------------------------
Breakpoint
--------------------------------------------------------------------------------------------
A breakpoint is a stop point in the execution. To insert a breakpoint, either double click on code line in "Source code browser", or right click on the line, and select the "Insert Breakpoint" option.

In case the line has already a breakpoint, the effect is to delete that line´s Breakpoint. All breakpoints may be disable / enable or clear through the button in the "Toolbar" or with the "Debug" menu option.

--------------------------------------------------------------------------------------------

Alerts

--------------------------------------------------------------------------------------------

Are another kind of stops in the execution. These are conditional stops, that is, breakpoints depending on a condition fulfillment for the execution stop. In the "Alerts" section it needs to be typed a logic condition. When that condition is correct, it would be indicated by an icon on the left.

If the execution stops because of an alert, the same icon will indicate that the running alert.

To disable an alert comment the line with "//"

Note: The attribute or variable names in an alert must be placed before with the object´s name. The object´s name must be written with the letter assigned by GeneXus (i.e: R: Report, W: Work Panel, etc.).

--------------------------------------------------------------------------------------------
DebuGX in a Report / Procedure

--------------------------------------------------------------------------------------------

When the object to debug obtains the execution, the code line to be executed may be seen in the "Object Browser". Besides lines appear on the left lower margin indicating that the application is in execution.

From that moment, DebuGX controls the execution. In case the "Automatic Pause when start" option is selected in the "Options" menu, the execution will pause in the first code line. Otherwise, the execution will continue until the first Breakpoint.

The existing execution controls are the following:

- Step Forward: This option / button allows to move forward one line in the execution. - Step Back: This option / button allows to move backwards one line in the execution. - Run until the next Breakpoint: This option / button allows to move the execution forward until the next Breakpoint. - Pause Execution: This option / button allows to pause the execution in the line ongoing. - The "Steps" Bar allows to move, back and forth, through the executed code lines .

Place the mouse over any attribute or variable, and all the attributes and variables values in that code line will appear.

To monitor any attribute and / or variable include them on the "Watch List". There are two ways:

1. On GeneXus code, right click on the attribute or variable line. Then, choose "Add To Watch List" option and select the attribute/ variable from the list.

2. Look for the attribute / variable in the "Objects Browser" and double click on its name. If the attribute / variable belongs to a Structured Data Type (SDT) or a Business Component (BC), it will apperar on a new window:

Every time you up date a value or add an item to the collection, this window will refresh, that is, the tree expands and shows the SDT or BC content. To activate or desactivate that function, click on the option "Auto Expand SDT tree" from the "Option" menu.

Selecting an attribute / variable in the "Objects Browser", the "Properties" window will show the defined properties for that attribute / variable.

Char, numeric and date variable values can be change in execution from the DebuGX console. Right click on GeneXus source in the variable line and go to "Change Values" option then select the variable from the list.

Once you select the variable, the following window will appear:

You could see the modified value once it has been determined.

Note: Remember the indicator () shows the GeneXus source line to be executed so for the code to execute, the indicator must move to the following line first.

--------------------------------------------------------------------------------------------
DebuGX in a Work Panel / Web Panel

--------------------------------------------------------------------------------------------
The main characteristic of the events objet's is the possibility to go directly to its definition or to some subroutine. For that, right click on mouse over the "Source code Browser" and go to "Goto Event/Sub" option.

When a Work Panel / Web Panel with Base table doesn´t have defined the "Load" event, DebuGX defines one called "Implicit Load Event". This allows to visualize the attributes values obtained from the Table. (If there is a subfile, this event will be executed for every loaded line) The "Options Automatic Pause when start" menu option (Shown in DebuGX in Report / Procedure) in Work Panel / Web Panel will only work if the "Start" event is defined, otherwise, enter a breakpoint in the desired place.

--------------------------------------------------------------------------------------------
DebuGX in a Transaction ( Debugging Rules ! )

--------------------------------------------------------------------------------------------

In the transactions, the execution rules may be seen.

- All rules with explicit condition have two execution moments:

1. Before the condition evaluation. On the DebuGX console this moment is showed with the execution indicator () in the corresponding rule line and with an indicator in the condition that will be evaluated.

2. Before the rule triggers (this moment will only exist if the condition evaluation was genuine). In this moment, the DebuGX´s Console preserves the execution indicator in the corresponding rule line and shows an indicator in the rule that will be triggered.

- In the rules without explicit condition, the execution indicator () will be seen in the corresponding rule line and an indicator is shown in the rule that will be shooted. In this way, you are able to see every rule moment and obtain the attributes and / or variables values before each one. If the "Always Pause on Rules" option is selected in the "Options" menu the execution will pause in each rule before being evaluated and / or before being shooted, depending on the case. If not, the execution will continue until the first breakpoint.

In "Rules" section there may be differences with the ones defined in GeneXus . This happens because of the following:

Particular Rules:
There are rules that are turned into equivalents by the specification.

Examples:

1. The rule "Serial(att1 , att2 , step);" will be turned into the following rules: att2 = old(att2 ) step IF insert AND level( att1 ); att1 = att2 IF insert;

2. The rule "Default(att &var , expression);" will be transformed into: att &var = expression IF insert AND null( att &var ) AND &GxBScreen = 0;

Formula attributes Some formulas are solved through rules.

Example:

1. The InvoiceTotal? attribute (an Invoice total) defined as a formula: SUM (InvoiceLinetotal) (vertical Sum) is solved by the following rules: InvoiceTotal? = old(InvoiceTotal) InvoiceLineTotal? IF insert; InvoiceTotal? = old(InvoiceTotal) InvoiceLineTotal? - old(InvoiceLineTotal) IF update; InvoiceTotal? = old(InvoiceTotal) - old(InvoiceLineTotal) IF delete;

Attributes with value range The attribute validity ranks are solved by rules.

Example:

1. The InvoiceLineQty? attribute (item amount) defined with the following rank: 1:20; is solved by the following rule: Error( 'Field Quantity is out of range' ) IF NOT ( ( InvoiceLineQty? >= 1 AND InvoiceLineQty? <= 20]] The GeneXus Specifier makes these transformations and they are seen in the detailed navigation.

--------------------------------------------------------------------------------------------
Remote DebuGX
--------------------------------------------------------------------------------------------

DebuGX Specifier

Once the GeneXus specification objects is finished, they have to be specified with DebuGX.
For that the "Specify with DebuGX" option is located in the "Tools" menu.

Once that option is selected the DebuGX Specifier will unfold, in which the objects specified by GeneXus and pending of generation, are shown.

Select the object / s that will be debugged (for a multiple selection the press Ctrl key and select objects with the mouse). Press "Advanced" and the following option unfolds:

Indicate the IP address of the PC where the object is being executed ("remote PC"). In a Stand Alone execution, enter "localhost" or "127.0.0.1". A window indicating the specification process of DebuGX Specifier will be shown by pressing the "OK" key.

Send new version

Once you get the object wih the DebuGX information, send to the "remote PC" both the object and a file located in the Debugx 2.0 Installation folder (the default directory is "c:Program filesDebuGX 2.0") called "RemoteDebuGX? .exe".

Execute Remote DebuGX

Execute in "remote PC" the sent file ("RemoteDebuGX? .exe"). Then this window appear:

Execution

Execute the application from your usual start point and wait for the object to debug execution. At the beginning of the object execution, you will see on the inferior left margin in remote DebuGX a legend that indicates the execution is taking place.

Once the execution has finished, click on "Stop & Save". A window indicating the name and location of the file to be saved will unfold.

DebuGX Console

To execute the console, go to the DebuGX Console option in the "Tools" menu. Then, go to the "Open" option in the "File" menu and click on the "Remote Debug Execution".

Execution procedure in the console is like an online execution.

SCARICATELO QUI -

http://www.debugx.com.ar/site/hgxpp001.aspx?10,1,8,O,S,0,MNU;E;1;3;MNU;,

Primo Libro della Rocha direttamente On-Line

http://www.genexus.com/rocha/GeneXus_Rocha_Book-Episode_One.pdf