Page 1 of 1

Enhancement of Gadget/Window libs

Posted: Mon Apr 16, 2007 5:05 pm
by CSAUER
Here is my actual wishlist for the next version:

- Compiler-Variable: XP-Skin activated
- Flag for coloring background of Panel-Gadgets as well as for coloring tab's background
- Flag for turning off ListView header
- Handling / Command for Z-Order of Gadgets (display z-order as well as catching events of overlaying gadgets)
- Platform independed Drag and Drop functionality (like BlitzMax)
- Gadget-Events "MouseOver", "MouseDownLeft", "MouseDownRight", "MouseWheelUp", "MouseWheelDown", "MouseWheelClick"
- Native autocomplete flag for entering list value into combo gadget
- Editable list icon gadget (with flag for column sorting)
- Native support (without ODBC) for SQLite commands (all platforms), maybe just a flag on "OpenDatabase" command

Hopefully I can see most of the stuff within next versions (on all platforms).

Re: Enhancement of Gadget lib

Posted: Mon Apr 16, 2007 5:36 pm
by byo
CSAUER wrote:- Compiler-Variable: XP-Skin activated
- Flag for coloring background of Panel-Gadgets as well as for coloring tab's background

- Native support (without ODBC) for SQLite commands (all platforms), maybe just a flag on "OpenDatabase" command.
The first two can be done in the current version, right? Or have I misundertood your request?

You can use SQLite3 natively with the PBOSL userlib. I'm making a program that uses it and it works like a charm. ;)

Posted: Mon Apr 16, 2007 6:02 pm
by netmaestro
No, they aren't available currently. He's referring to a constant testable via CompilerIF, #PB_Compiler_Themes or such. For now, you have to test for it thus:

Code: Select all

Procedure ThemesEnabled()
  dlv.DLLVERSIONINFO
  dlv\cbsize=SizeOf(DLLVERSIONINFO) 
  lib=OpenLibrary(#PB_Any,"comctl32.dll") 
  If lib 
    CallFunction(lib,"DllGetVersion",@dlv) 
    DLLVersion = dlv\dwMajorVersion 
    CloseLibrary(lib) 
  EndIf 
  If DLLVersion = 6
    ProcedureReturn 1
  Else
    ProcedureReturn 0
  EndIf
EndProcedure

Debug ThemesEnabled()
which is considerably more effort. I second this, it's a good idea.

Posted: Mon Apr 16, 2007 6:13 pm
by ts-soft
The Sourcecode by netmaestro is usefull, but a compilerdirective is not
usefull. XP-Style should always enabled, in all windows applications!

Why test on compiletime. Only on runtime makes sense.

Posted: Mon Apr 16, 2007 6:18 pm
by netmaestro
You make a good point, but it's main use would be for those creating userlibs, where it isn't known if the coder is going to be enabling themes or not.

Posted: Mon Apr 16, 2007 6:31 pm
by ts-soft
UserLibs a compiled code, compilerdirectives works only on compiletime of
the lib. Only a runtime-function should work

Posted: Mon Apr 16, 2007 6:42 pm
by netmaestro
*.pbi :wink: