AndyGable wrote: ↑Thu Mar 13, 2025 11:09 am
In 3.19.5 it works fine But now in 3.20.2 it disables the menu form but will not show the frmQuestionBO (do I need to bring it to the front or something)
and this seems to be ONLY when the code is run from the development environment
I have no idea what is going on but there where some changes from 3.19 to 3.20 in workspace:
Code: Select all
Workspace
Disable menu shortcuts in design mode.
Select is a new event that is raised when the user clicks on a tab button, even if it is the current one.
Find() is a new method that returns the position of a specific Workspace window.
The second argument of Add() is now the position where the new window must be inserted. If not specified, the window is inserted at the end.
Adding a window at a specific position should work better now.
Update Italian translation.
Update Dutch translation.
Update documentation.
See:
https://gambaswiki.org/wiki/doc/release/3.20.0#t113
And if you develop your POS system for company environments, why go with latest gambas. Develop on a certain version and keep your IMB's at that version (of both debian and gambas3) for a, by you, determined period (like until the POS software is feature finished for example), so you don't get into this trouble.
I, for example, have migrated a complete suite of software I wrote (running on XP), from a mix of vb/vba/ms access to gambas3/mysql later mariadb. I had Gambas 3.6.2 running at that time (2013) on Mint Mate 17 clients and my re coding of all was feature finished somewhere in 2017. So, yes I stayed on same Gambas version for 4 years, before even looking at upgrading to a higher version and I did backport a feature to Gambas 3.6.2 from a later release that I really needed. The headless servers at that time, run Debian 7 or 8 (don't remeber exactly) and run Gambas 3.6.2 daemons as well. Before the debian servers, I run a Windows 2003 server with Active Directory.
I currently run gambas 3.18.4 (since dec '23) on Debian 12 Mate clients (bye bye to first Ubuntu and now even the Ubuntu based OSes with their crap). The servers have been upgraded a few times and are on debian11 ATM, this all in a company. I plan to stay there for a about a year or 3 ( so till somewhere in 2026 when debian 13 will be out for about a year and has been proven stable long enough) before going to a newer version of Gambas3 and Debian. So, no surprises there when gambas has an update as it doesn't affect my running software in company environment. Stability over the latest and greatest when it comes to work situations is my strategy to keep me from wasting my time. My software runs 24/7 and I can't afford it breaking because of some changes to gambas3 (no need to go out late night to solve some unneeded shit because of an update).
I do test most of the company software against a newer release now and then. Somewhere in 2026 I will do a distribution upgrade and a gambas upgrade but not before having it all tested. I run my own repository with gambas3 and if there are fixes to problems in gambas3 that I need, I simply backport them to my 3.18.4 version, so I do not miss out on what I really need.
So, in short: Ensuring yourself that you are in control of the environment you run your software in saves you a lot of trouble, time and work.
My 2 cents,
