Hi again Paddy, From what I've become to understand is, there's no method to write to your database directly. As in no way in a script to write to any target column on products or other, with the exception of a products property which on ticket close writes to ticketlines.ATTRIBUTES for the product line. Can be useful.
Hi again Paddy, From what I've become to comprehend is, there's no method to write to your database directly. As in no way in a script to write to any target column on products or other, with the exception of a products property which on ticket close writes to ticketlines.ATTRIBUTES for the product line. Can be useful.
Don't think there's anything wrong with it.
It's a jungle out there...
Paddy, You can post code within '~~~' after new line. You can even describe it with '::java' after the '~~~' start on new line. You can post different code types like that ::python or ::batch just add new or two line before start and finish with '~~~'. Like: ~~~ ::java Code code code code and more code ~~~ import com.openbravo.format.Formats; import com.openbravo.pos.ticket.TicketLineInfo; import com.openbravo.pos.ticket.TicketProductInfo; discountrate = sales.getInputValue() / 100.0; multiply =...
Paddy, You can post code within '~~~' after new line. You can even describe it with '::java' after the '~~~' start on new line. You can post different code types like that ::python or ::batch just add new or two line before start and finish with '~~~'. import com.openbravo.format.Formats; import com.openbravo.pos.ticket.TicketLineInfo; import com.openbravo.pos.ticket.TicketProductInfo; discountrate = sales.getInputValue() / 100.0; multiply = 1; index = sales.getSelectedIndex(); if (index >= 0) {...
Don't need source code change with that. - Do need to edit resource Ticket.Buttons... and Enable ticket.change by uncommenting the line, set event.change as code target. - Make new text resource called event.change, paste code, save. Be warned though, the above code should be only used with testing. It's not ideal.
Don't need source code change with that. - Do need to edit resource Ticket.Buttons... and Enable ticket.change by uncommenting the line, set event.change as code target. - Make new text resource called event.change, paste code, save. Be warned though, the above code should be only used with testing. It's not ideal. It does use last scanned item, so if price change previous match, it'll overwrite it.
Don't need source code change with that. - Do need to edit resource Ticket.Buttons... and Enable event.change by uncommenting the line - Make new text resource called event.change, paste code, save. Be warned though, the above code should be only used with testing. It's not ideal. It does use last scanned item, so if price change previous match, it'll overwrite it.
UniCenta v4.6.1 does not have that option built in. If you look at my recent posts you'll find one that tries to have the last scanned line as selected after being consolidated. There's an issue with removing a line on the event.change when it's a variable priced product. You can still do line consolidation on event.change script. Need to enable ticket.change (<event key="ticket.change" code="event.change"/) in Ticket.Buttons on resources and add the script (found from RickyO https://sourceforge.net/p/unicentaopos/discussion/1126901/thread/3f7bd3fdf1/#2207)...
UniCenta v4.6.1 does not have that option built in. If you look at my recent posts you'll find one that tries to have the last scanned line as selected after being consolidated. There's an issue with removing a line on the event.change when it's a variable priced product. You can still do line consolidation on event.change script. Need to enable ticket.change (<event key="ticket.change" code="event.change">) in Ticket.Buttons on resources and add the script (found from RickyO https://sourceforge.net/p/unicentaopos/discussion/1126901/thread/3f7bd3fdf1/#2207)...
UniCenta v4.6.1 does not have that option built in. If you look at my recent posts you'll find one that tries to have the last scanned line as selected after being consolidated. There's an issue with removing a line on the event.change when it's a variable priced product. You can still do line consolidation on event.change scripted event.change Need to enable ticket.change in ticket.buttons on resources and add the script (found from RickyO https://sourceforge.net/p/unicentaopos/discussion/1126901/thread/3f7bd3fdf1/#2207)...
Found a way. Simply ditch source code change. Edited the script to work the consolidation in reverse so that it leaves the product you last add instead of the first found on loop. Simplified even more... Edit: ATTENTION - needs more work. Variable priced products issue and possibly another. // ticket.change // --- Start of "Scripted Screen Consolidate" --------------------------------- // + Now checks for matching Product Names (31/03/15) // + Now product added will be selected as default. No source...
Even though I'm not using unicode extended characters and uniCenta does not recognise or use them (at least v3.8x versions) decided to flick the switch for future use... How to alter your MySQL database to complete full UTF8 unicode support: WARNING: Doing this may require reversal to utf on utf8_gerneral_ci in the event you need to upgrade uniCenta .1. Backup your database .2. Execute: For each database: ALTER DATABASE database_name CHARACTER SET = utf8mb4 COLLATE = utf8mb4_unicode_ci; .........................................................................................
Even though I'm not using unicode extended characters and uniCenta does not recognise or use them (at least v3.8x versions) decided to flick the switch for future use... How to alter your MySQL database to complete full UTF8 unicode support: WARNING: Doing this may require reversal to utf on utf8_gerneral_ci in the event you upgrade uniCenta .1. Backup your database .2. Execute: For each database: ALTER DATABASE database_name CHARACTER SET = utf8mb4 COLLATE = utf8mb4_unicode_ci; .........................................................................................
Even though I'm not using unicode extended characters and uniCenta does not recognise or use them (at least v3.8x versions) decided to flick the switch for future use... How to alter your MySQL database to complete full UTF8 unicode support: WARNING: Doing this may require reversal to utf on utf8_gerneral_ci in the future .1. Backup your database .2. Execute: For each database: ALTER DATABASE database_name CHARACTER SET = utf8mb4 COLLATE = utf8mb4_unicode_ci; .........................................................................................
.
At a crossroads. Don't have the time to work out a method of variable price edits on the event.ticket with uniCenta. Chromis x64 0.94.5 is a failed build (current beta isn't anywhere near useable and Chromis seems rather dead without any development), rather questionable. Chromis x32 0.95.4 is promising, yet still attempting some migration from a modified version of uniCenta 3.81. Chromis does allow the variable line manipulation. I even tried earlier versions of uniCenta and Java versions. That...
At a crossroads. Don't have the time to work out a method of variable price edits on the event.ticket with uniCenta. Chromis x64 0.94.5 is a failed build, rather questionable. Chromis x32 0.95.4 is promising, yet still attempting some migration from a modified version of uniCenta 3.81. Chromis does allow the variable line manipulation. I even tried earlier versions of uniCenta and Java versions. That said, I'm not entirely impressed by Chromis. Really wanted uniCenta on an upgrade. Respect to Jack...
I've determined an issue to be with variable price products. Can't remove a variable priced line the line via ticket.change script. Just bogs. Can't copy the line either Don't know if this is 4.6.1 issue alone? There is the code I used to find issue... // -- the added product line added_ticketline = ticket.getLine(ticket.getLinesCount() - 1); added_qty = added_ticketline.getMultiply(); // -- find any first matching ProductID line... for (int number = 0; number < ticket.getLinesCount() -1; number++)...
I've determined an issue to be with variable price products. Can't remove a variable priced line the line via ticket.change script. Just bogs. Can't copy the line either Don't know if this is 4.6.1 issue alone? There is the code I used to find issue... // -- the added product line info added_ticketline = ticket.getLine(ticket.getLinesCount() - 1); added_qty = added_ticketline.getMultiply(); // -- find any first matching ProductID line... for (int number = 0; number < ticket.getLinesCount() -1; number++)...
I've determined an issue to be with variable price products. Can't remove a variable priced line the line via ticket.change script. Just bogs. Can't copy the Don't know if this is 4.6.1 issue alone? There is the code I used to find issue... // -- the added product line info added_ticketline = ticket.getLine(ticket.getLinesCount() - 1); added_qty = added_ticketline.getMultiply(); // -- find any first matching ProductID line... for (int number = 0; number < ticket.getLinesCount() -1; number++) { line...
Found a way. Simply ditch source code change. Edited the script to work the consolidation in reverse so that it leaves the product you last add instead of the first found on loop. Simplified even more... Edit: ATTENTION - needs more work. Variable priced products issue and possibly another. // ticket.change // --- Start of "Scripted Screen Consolidate" --------------------------------- // + Now checks for matching Product Names (31/03/15) // + Now product added will be selected as default. No source...
Found a way. Simply ditch source code change. Edited the script to work the consolidation in reverse so that it leaves the product you last add instead of the first found on loop. Simplified even more... // ticket.change // --- Start of "Scripted Screen Consolidate" --------------------------------- // + Now checks for matching Product Names (31/03/15) // + Now product added will be selected as default. No source code change needed. (18/03/21) // Remove duplicate item entries and sets counted quantity...
Found a way. Simply ditch source code change. Edited the script to work the consolidation in reverse so that it leaves the product you last add instead of the first found on loop. Simplified even more... // ticket.change // --- Start of "Scripted Screen Consolidate" --------------------------------- // + Now checks for matching Product Names (31/03/15) // + Now product added will be selected as default. No source code change needed. (18/03/21) // Remove duplicate item entries and sets counted quantity...
Found a way. Simply ditch source code change. Edited the script to work the consolidation in reverse so that it leaves the product you last add instead of the first found on loop. // ticket.change (event.change) import com.openbravo.format.Formats; import com.openbravo.pos.ticket.TicketLineInfo; import com.openbravo.pos.ticket.TicketInfo; import com.openbravo.pos.ticket.TicketProductInfo; import java.util.Properties; // --- Start of "Scripted Screen Consolidate" ---------------------------------...
I've been trying all sorts. Can't work this one out. So, is there a way to move a ticket line index position via ticket.change script? To move the edited line to last line position, so it will be naturally selected?
I've been trying all sorts. Can't work this one out. So, it there a way to move a ticket line index position? To move the edited line to last line position, so it will be naturally selected?
It's interesting to note this. I'm a hack sort of bloke. I reckon we could ping the server to keep alive or something like that. Not going to 'solve' it right now. Think an entire background tool for checking network connectivity on keep alive would be a go.
Here's a snippet of what I'm trying to achieve with uniCenta v4.6.1. https://streamable.com/ddk8wi
Here's a snippet of what I'm trying to acheive with uniCenta v4.6.1. https://streamable.com/ddk8wi
Here's a snippet of what I'm trying to acheive with uniCenta v4.6.1. <iframe src="https://streamable.com/e/ddk8wi?loop=0" width="560" height="315" frameborder="0" allowfullscreen=""></iframe>