Page 75 of 103
Posted: Sat May 30, 2009 8:04 am
by gnozal
Thanks.
In build 370, I added a trackbar to change the Integrator's height.
@kurzer : as more data is saved (and a bit differently), you may have to adjust your settings once more.
Example :
Code: Select all
...
[Windows]
...
Window_Integrator_H_Min = 442
Window_Integrator_X = 0
Window_Integrator_Y = 261
Window_Integrator_H = 710
...
Window_Integrator_H_Min -> Integrator minimum height [Min button] ; new default is 442.
Window_Integrator_X, Window_Integrator_Y, Window_Integrator_H -> Integrator coordinates [Window_Integrator_H must be >= Window_Integrator_H_Min].
Posted: Sat May 30, 2009 4:32 pm
by Kurzer
Thanks again, gnozal. It works great here on my "lillte white beauty"
Well, today I used your PureCOLOR userlib for the first time and I stumbled over a minor issue.
One can legitimately change the background colour of a button and let the textcolour unchanged using your PureCOLOR lib.
Here is an examplecode (PB 4.30):
Code: Select all
OpenWindow(0, 100, 100, 80, 80, "PureCOLOR button test", #PB_Window_ScreenCentered | #PB_Window_SystemMenu)
ButtonGadget(1, 10, 30, 80, 20, "Test it")
PureCOLOR_SetButtonColor(1, #PureCOLOR_SystemColor, RGB(255,0,0), #PureCOLOR_SystemColor, RGB(255,255,0))
Repeat
Until WaitWindowEvent() = #PB_Event_CloseWindow
End
If you try to set own background colors in PureFORM you will get wrong code. PureFORM will suppress the last two parameters:
Sorry for my activity.

Posted: Tue Jun 02, 2009 8:44 am
by gnozal
kurzer wrote:... If you try to set own background colors in PureFORM you will get wrong code. PureFORM will suppress the last two parameters
Should be fixed in build 371.
Posted: Fri Jun 05, 2009 11:13 am
by gnozal
Update (build 372)
Changes :
- 'Save as code' requester now remembers last chosen filename. This information is also saved in the project file [.pbf].
Posted: Fri Jun 05, 2009 2:30 pm
by Kurzer
Hello Gnozal,
my example two post above does't run with PureFORM 371, PureBasic 4.31final and your current PureCOLOR lib.
The Purebasic Compiler report this message:
"Constant not found! - #PureCOLOR_SystemColor" Error
I installed the lib again because after installing PB 4.31 I copied the PureCOLOR files manueally, but same result.
Posted: Fri Jun 05, 2009 2:43 pm
by gnozal
kurzer wrote:Hello Gnozal,
my example two post above does't run with PureFORM 371, PureBasic 4.31final and your current PureCOLOR lib.
The Purebasic Compiler report this message:
"Constant not found! - #PureCOLOR_SystemColor" Error
I installed the lib again because after installing PB 4.31 I copied the PureCOLOR files manueally, but same result.
You mean this code ?
Code: Select all
OpenWindow(0, 100, 100, 80, 80, "PureCOLOR button test", #PB_Window_ScreenCentered | #PB_Window_SystemMenu)
ButtonGadget(1, 10, 30, 80, 20, "Test it")
PureCOLOR_SetButtonColor(1, #PureCOLOR_SystemColor, RGB(255,0,0), #PureCOLOR_SystemColor, RGB(255,255,0))
Repeat
Until WaitWindowEvent() = #PB_Event_CloseWindow
End
I runs just fine here using PB4.31 and jaPBe or PB IDE. From PureFORM as well.
I can compile a form with a colored button using #PureCOLOR_SystemColor without errors.
Seems like the resident PureCOLOR.res is missing in %purebasic%\Residents ?
I checked PureCOLOR-PB430-Installer.exe in PureCOLOR_430.zip : the resident is present !?
Anyway, #PureCOLOR_SystemColor = -1.
Posted: Fri Jun 05, 2009 3:44 pm
by Kurzer
Seems like the resident PureCOLOR.res is missing in %purebasic%\Residents ?
Ya, thanks man! Thats was the real cause. But it was also a chain reaction of unfortunate events.
I use a portable installation of PB.
To test/install a new PB version I do the following steps:
- Running the PB Installer on a
testpartition and install PB there.
- Then I copy all libs and tools from my previous PB folder manually to the new PB folder and fit the path-entries of PBs *.prefs files and Pureforms .ini file.
- After checking the new installation I copy the whole PB folder to my normal working partition and put the folder into the "C:\Program file" folder. So far so good.
I guess you are right and I forgot to copy the residents. :roll:
But before I wrote my post I already re-installed your lib (running the LibInstaller.exe). Hmm, the result was the same.
Okay, to cut a long story short: I restarted the PB IDE and now all runs without any failure. I only had to restart the IDE before stampede me (and you)
Okay, but "wo ich gerade hier bin" (sorry don't know the english term), what do you think about this small suggestion for PureFORM? :roll:
A new property for Windows - a checkbox called [x] SmartWindowRefresh
This should generate a "SmartWindowRefresh(#WindowID, 1)" into the code if selected.
Posted: Fri Jun 05, 2009 3:51 pm
by gnozal
kurzer wrote:Okay, to cut a long story short: I restarted the PB IDE and now all runs without any failure. I only had to restart the IDE before stampede me (and you)

Yep, the compiler loads the residents at startup.
kurzer wrote:A new property for Windows - a checkbox called [x] SmartWindowRefresh.
This should generate a "SmartWindowRefresh(#WindowID, 1)" into the code if selected.
Good idea, done.
Posted: Sat Jun 06, 2009 7:49 am
by gnozal
Update
Changes :
- added 'Use SmartWindowRefresh()' option in window properties as suggested by kurzer.
Posted: Sat Jun 06, 2009 10:57 pm
by Kurzer

Wow, amazing fast! Thanks man. *thumbup*
Posted: Thu Jun 11, 2009 10:52 pm
by Kurzer
Hi Gnozal, it me again.
Today with another suggestion regarding the tab order of gadgets.
What do you think about an 'auto-order' function which scans the window gadgets from top left to bottom right (zig-zag) and set the tab order of every gadget according to its position in the window?
Now it is a bit time-consuming to re-order a window with many gadgets.
Using the "tab order-window" you have to click on the arrow-butttons, then on the next gadget entry, then again on the arrow buttons, the gadget entry... etc.
Maybe you could insert two sort algorithms
- from top to bottom, scanning each 'line' from left to right (like the example)
- from left to right, scanning each 'row' from top to bottom
Here is an example:
I think for bigger projekts this would be a substantial feature.
National characters from Text Gadget disappears and bug...
Posted: Wed Jun 17, 2009 4:27 pm
by zxtunes.com
National characters from Text Gadget disappears/removed to slash.
Pure Visual Designer works correctly.
It characters "я" (Я) have code 255 in WIN1251 code table.
Posted: Mon Jun 22, 2009 1:15 pm
by gnozal
kurzer wrote:Today with another suggestion regarding the tab order of gadgets.
What do you think about an 'auto-order' function which scans the window gadgets from top left to bottom right (zig-zag) and set the tab order of every gadget according to its position in the window?
I will think about it.
This time, not so fast !
Re: National characters from Text Gadget disappears and bug.
Posted: Mon Jun 22, 2009 1:22 pm
by gnozal
zxtunes.com wrote:
National characters from Text Gadget disappears/removed to slash.
Pure Visual Designer works correctly.
It characters "я" (Я) have code 255 in WIN1251 code table.
Some characters are not allowed as there are used as separators : on my french keyboard -> '¶·¸' ANSI = (182, 183, 184).
No problem with ANSI CHAR 255 here.
Posted: Mon Jun 22, 2009 9:19 pm
by Kurzer
gnozal wrote:I will think about it.
This time, not so fast !
Hey, I'm not a slavedriver - I have probably just too many ideas.
Take all the time you need and especially... do it only if you want it to do (or if you find it useful).
You have already done great things by publishing PureFORM for free. *thumbsup*