so have to store the value in program setting so in both cases how will it be defined
state is initalized --------------> store in program setting
item voided
set initalized state to null
it cancel void
set null to its initalized state
how to proceed?
PS if i dont work this out it wont effect anything its just an enhancment
It would need to be linked to ticket ID I would think. So probably store it on Ticket Closed. You could store the Ticket ID and the State. The Program Setting could be called the same as the State if you want.
Im thinking the Ticket ID because if you do multiple ticketsā¦ So maybe the setting Name can be dynamic as well and make the name the Ticket ID. You could easily pull up that setting from within that ticket by using that ticket ID and since the setting would be named the same it would pull up the right ID everytime.
So Setting Name would be TIcket ID. Value would be the State.
hmmm in such caseā¦ if i dont work this out it wont effect anything its just an enhancment 
Only problem I could see is if you have multiple items in same ticket using that same stateā¦
The other states, are they ever put into receipt?
yes they are put in the receipt
Perhaps you should rethink the flow then. Maybe use Ticket Tags instead?
EDIT: Nevermind if I remember right I suggested the States because you had problems with Ticket Tags working correctly. for what you wanted to do.
I am sure we can figure something out that works.
i have for time being its working fine if in future get problem then use ticket close and program setting
and ofcourse with your help
BTW This may be off topic but I wanted to ask you something. Take your time and give a good honest answer if you wish to answer it.
Of any feature that is currently not available or there has not been a solution yetā¦ what would be the one feature you would want in SambaPOS that is not currently available that you know of?
I am just curious because I am looking for some interesting projects and looking for inspiration for my own system,
there was one to remove service charge from product and update accounts if i remember some thing else will update you
Ok so really what your asking is you would like to see a Order Based Calculation in addition to the Ticket Calculation?
I remember the discussion. It is possible using the tools we have now. But I think having an Order Based Calculation option similar to the Ticket Calculations would be a simpler approach. Maybe @emre could look into this some day.
yeah in that discusssion i was suggested to use a far complex scenarion which i think a simple user wont be able to do.
the other i would suggest to have link for big picture for each product since we can use tablet for order taking we can show picture of product to customers
should have option to sort order tags and tags should be listed as they have been entered on screen
stock should be able to handle in inventory currently @QMcKay has suggested an external php workout
custom reports should be more flexible formatting wise and design
request for allowing default reports to be edited like dont want to show order tag modifer used
one more thing when we backup database we should be able to add few text to know which new functionality its referring so reversing become easier