Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: 1 [2]
16
Programming / Re: Strange behaviour reading ctl value
« on: August 09, 2018, 04:20:16 AM »
Thank you for the reply! I will get it updated.
17
Wish List / Complete black ED+ layout
« on: August 08, 2018, 09:17:33 AM »
At the moment it's possible to choose a colour layout in ED+. This is a great feature which can replace the white background for an 'easy on the eyes' black background. The other colours in the pallet also work in creating a less 'eye-stress heavy' editor window.
These settings only apply to the actual coding area, the surrounding ED+ window stays the same white+red. Could it be possible to change the background colour of the rest of the GUI as well?
These settings only apply to the actual coding area, the surrounding ED+ window stays the same white+red. Could it be possible to change the background colour of the rest of the GUI as well?
18
Wish List / ED+ tab enhancement
« on: August 08, 2018, 08:58:15 AM »
In the ED+ editor there is a left menu that show the available labels in the program. In the original IT you also had the choice to expand or collapse these labels, which made it more clear where to look for a certain label/variable and you didn't need to scroll so much to find what you were looking for.
Could this also be implemented into ED+?
--
Also, variables and methods no longer show up in the left side-menu in ED+. Could they be shown as well in the ED+ bookmarks section somehow?
Could this also be implemented into ED+?
--
Also, variables and methods no longer show up in the left side-menu in ED+. Could they be shown as well in the ED+ bookmarks section somehow?
19
Wish List / More controls on Nomads panels
« on: August 08, 2018, 08:37:39 AM »
At the moment there is an object control cap at 200 items. This is 200 items total on the screen, weither or not they are on folders or not. If you place more controls you start getting errors while starting up the panel.
With the increase in screen resolution Nomads screens keep getting bigger, and we have had to split up a couple of dashboards screens unfortunately because we couldn't place the desired amount of controls.
It would be appreciated if you could let us place more controls.
With the increase in screen resolution Nomads screens keep getting bigger, and we have had to split up a couple of dashboards screens unfortunately because we couldn't place the desired amount of controls.
It would be appreciated if you could let us place more controls.
20
Wish List / Ability to search on grid column names with GRID FIND
« on: August 08, 2018, 08:07:59 AM »
It is possible to use a Grid Find command to get data from a grid; GRID FIND ctl_id,col,row,var$[,ERR=stmtref]
However, the fact you can't use the actual name of the column (grid.ctl'column$). GRID FIND would be more flexible if you would be able to use it like this:
GRID FIND ctl_id,(col or col$),row,var$[,ERR=stmtref]
This way, when a grid column needs to be added in between, the code will always keep working like intended. The other upside is that the code gets more readable, the name of a gridcolumn is far more understandable than a number.
It would be very helpful if you could add the ability to search on grid column names with GRID FIND.
However, the fact you can't use the actual name of the column (grid.ctl'column$). GRID FIND would be more flexible if you would be able to use it like this:
GRID FIND ctl_id,(col or col$),row,var$[,ERR=stmtref]
This way, when a grid column needs to be added in between, the code will always keep working like intended. The other upside is that the code gets more readable, the name of a gridcolumn is far more understandable than a number.
It would be very helpful if you could add the ability to search on grid column names with GRID FIND.
21
Programming / Strange behaviour reading ctl value
« on: August 03, 2018, 04:43:46 AM »
If you are in a WindX session on Unix and you run the following program:
0005 PRINT 'CS'
0006 BEGIN
0010 MULTI_LINE 131,@(13,2.3,6,1),FNT="Arial,.75,B"
0020 BUTTON 1,@(13,22,10,2)="F1"
0030 SET_FOCUS 131
0040 INPUT *
0050 PRINT CTL
0060 GOTO 0040
When you press the F1 key you get the following result:
- 131
- 1
When you run this program in a non-Unix environment it only gives back the ctl 1, which is what it should do.
Could this be looked into please?
0005 PRINT 'CS'
0006 BEGIN
0010 MULTI_LINE 131,@(13,2.3,6,1),FNT="Arial,.75,B"
0020 BUTTON 1,@(13,22,10,2)="F1"
0030 SET_FOCUS 131
0040 INPUT *
0050 PRINT CTL
0060 GOTO 0040
When you press the F1 key you get the following result:
- 131
- 1
When you run this program in a non-Unix environment it only gives back the ctl 1, which is what it should do.
Could this be looked into please?
22
Programming / Re: PxPlus 2018 closing when trying to use key number 17
« on: August 02, 2018, 02:37:03 AM »
I am using a PxPlus EFF database. It's also not he key itself, I have removed a couple of keys for testing
Because of the attachments restrictions on this forum I can't give you a screencapture of what happens.
The process just dies without any error message from windows or PxPlus 2018.
While using PxPlus 2017 the program performs fine and as intended.
*Edit--------------------
I filed the ticket under #849795. I attached a screen capture of the behavior of the program and an image of the keydef.
Because of the attachments restrictions on this forum I can't give you a screencapture of what happens.
The process just dies without any error message from windows or PxPlus 2018.
While using PxPlus 2017 the program performs fine and as intended.
*Edit--------------------
I filed the ticket under #849795. I attached a screen capture of the behavior of the program and an image of the keydef.
23
Programming / PxPlus 2018 closing when trying to use key number 17
« on: August 01, 2018, 07:47:04 AM »
I have a database file with 17 keys. If I try to go through a select --> next record with the 17th key PxPlus 2018 just closes down without a single message. If I try the same code on PxPlus 2017 then the program runs fine ...
Is there some parameter I need to set in order for it to work with PxPlus 2018?
Is there some parameter I need to set in order for it to work with PxPlus 2018?
Pages: 1 [2]