PureBasic Forums - English

Fast, smooth and very efficient on system resources, good one Chris, cant wait to do some testing.

That looks nice.

I did notice on the right-edge of the expandable border, there is some visible artifacting (appears as aliasing) I'm assuming has to do with the expanding/shrinking process.. It looks fine if you find the "native" size but outside of that is pretty apparent.

electrochrisso wrote: Fast, smooth and very efficient on system resources, good one Chris, cant wait to do some testing.

Thanks Chris, I'm glad it's running well! You can also try different border images by replacing the border35__.png image in the icons folder. A Google images search is a good resource of test borders but you must make sure the border image is hollow in the middle (transparent, have an alpha channel) otherwise the auto-border algorithm won't know how to chop up the image.

Zach wrote:That looks nice.

I did notice on the right-edge of the expandable border, there is some visible artifacting (appears as aliasing) I'm assuming has to do with the expanding/shrinking process.. It looks fine if you find the "native" size but outside of that is pretty apparent.

Thanks Zach, yes I'm using "poor man's anti-aliasing" which blurs the merged part slightly. Unfortunately there has to be a compromise between quality and speed/cpu but I should be able to get it looking better with some more tweaking hopefully.

Hi PrincieD

I'm getting various errors when trying to compile ProGUI examples :
POLINK: error: ...
Constant not found ...

should it work with PureBasic 5.11 version or not ?

Thanks.

PureBasic 5.11, Windows 8 x64 ..

There hasn't been a 5.11 compiled release yet, as far as I know..

I think you have to drop back down to the last official 4.x version.

It would probably be good to include the compiled version in the release notes/readme, etc.. If its not there already (who reads those things? lulz inorite)

Maybe it will be possible in the future to put a version check into the binaries? So then if you call it on something it hasn't been compiled for it errors out and tells you.


I think you should be OK if you use the DLL version. Just avoid the User Library

ruslanx: yes Zach is right, I haven't compiled the user library version yet with the latest version of PB which will give you the polink errors (some of the internals of PB must have changed quite a bit) but as Zach said, the DLL version will work fine for the time being. When I get a bit of spare time I'll see if Tailbite works with the latest PB and if so I'll re-compile the user lib.

Cheers!

Chris.

PrincieD wrote:

electrochrisso wrote: Fast, smooth and very efficient on system resources, good one Chris, cant wait to do some testing.

Thanks Chris, I'm glad it's running well! You can also try different border images by replacing the border35__.png image in the icons folder. A Google images search is a good resource of test borders but you must make sure the border image is hollow in the middle (transparent, have an alpha channel) otherwise the auto-border algorithm won't know how to chop up the image.

I tested this out with several borders of different sizes and got great results, this will be great for creating sliding borders. With a bit of planning no one will even notice the poor man's anti-aliasing, and appreciate the smooth effect.

electrochrisso wrote:I tested this out with several borders of different sizes and got great results, this will be great for creating sliding borders. With a bit of planning no one will even notice the poor man's anti-aliasing, and appreciate the smooth effect.

hehe thanks mate yes it will look better when it's animating, hmm maybe I can make it switch between high-quality for low frame-rate/still and "poor man's anti-aliasing" for high frame-rate

Chris.

PrincieD wrote:hehe thanks mate yes it will look better when it's animating, hmm maybe I can make it switch between high-quality for low frame-rate/still and "poor man's anti-aliasing" for high frame-rate

Chris.

Yes that would offer flexibility, so it could be possible to animate in high frame rate, and when the animation has finished switch to low frame/still.

electrochrisso wrote:Yes that would offer flexibility, so it could be possible to animate in high frame rate, and when the animation has finished switch to low frame/still.

Precisely! hopefully the eye won't notice when it's moving and animating but gives the illusion of high fidelity without hitting performance

Chris.

Any news?

Sveinung

Hey Sveinung,

Sorry for the delay in replying, I moved down to Norwich last week for a contract programming job.
It's been pretty hectic but I'll hopefully be able to start work on ProGUI again once I'm a bit more settled!

Cheers!

Chris.

I'm back on Windows (once you go free you should never have to go back >.<) for a small project, I needed proGUI to work on 5.11 and I don't like DLL.
So, new unofficial version of proGUI, I hereby dub thee 1.38b!

Changelog:

• _PB 5.11 compliant : just a few fixes with the new packer system, BriefLZ is now being used.
  _A new attribute for splitter gadget: #SPLITTEREX_LOCK: When the SplitterEx gadget is resized, the selected gadget will keep its size (much like PureBasic Splitter #PB_Splitter_FirstFixed and #PB_Splitter_SecondFixed ). Usage:
  • SetSplitterExAttribute(ID.i,#SPLITTEREX_LOCK,#SPLITTEREX_FIRST) : When the SplitterEx gadget is resized, the first gadget will keep its size
    SetSplitterExAttribute(ID.i,#SPLITTEREX_LOCK,#SPLITTEREX_SECOND): When the SplitterEx gadget is resized, the second gadget will keep its size
    SetSplitterExAttribute(ID.i,#SPLITTEREX_LOCK,#Null): When the SplitterEx gadget is resized, both gadgets will be resized by ratio (default mode)
    Keep in mind that min and max for each gadget are still used, so your gadget might be resized even though they are locked.

Since I can't release a dll or a tailbyte library (without breaking the user identification system), I have created a diff patch for the source version, download it here.
It's quite easy to apply: put your UNMODIFIED proGUI.pb (1.38 version) in the folder and run Patch proGUI.bat.

The patcher I'm using can be found here (binaries and sources): http://gnuwin32.sourceforge.net/packages/patch.htm

Poshu wrote:I'm back on Windows (once you go free you should never have to go back >.<) for a small project, I needed proGUI to work on 5.11 and I don't like DLL.
So, new unofficial version of proGUI, I hereby dub thee 1.38b!

Changelog:

• _PB 5.11 compliant : just a few fixes with the new packer system, BriefLZ is now being used.
  _A new attribute for splitter gadget: #SPLITTEREX_LOCK: When the SplitterEx gadget is resized, the selected gadget will keep its size (much like PureBasic Splitter #PB_Splitter_FirstFixed and #PB_Splitter_SecondFixed ). Usage:
  • SetSplitterExAttribute(ID.i,#SPLITTEREX_LOCK,#SPLITTEREX_FIRST) : When the SplitterEx gadget is resized, the first gadget will keep its size
    SetSplitterExAttribute(ID.i,#SPLITTEREX_LOCK,#SPLITTEREX_SECOND): When the SplitterEx gadget is resized, the second gadget will keep its size
    SetSplitterExAttribute(ID.i,#SPLITTEREX_LOCK,#Null): When the SplitterEx gadget is resized, both gadgets will be resized by ratio (default mode)
    Keep in mind that min and max for each gadget are still used, so your gadget might be resized even though they are locked.

Since I can't release a dll or a tailbyte library (without breaking the user identification system), I have created a diff patch for the source version, download it here.
It's quite easy to apply: put your UNMODIFIED proGUI.pb (1.38 version) in the folder, run Patch proGUI.bat, when asked, press Y and enter.

The patcher I'm using can be found here (binaries and sources): http://gnuwin32.sourceforge.net/packages/patch.htm

I'm also in the same situation in needing ProGUI to work with 5.11, but I ran into a problem running your patch.
When I run the patch I get "Reversed (or previously applied) patch detected! Assume -R? [n]".
I'm using the source file that was sent to me unmodified. I listed my checksums below.

CRC32: 8FEE1C65
MD5: 5696B855E89622ECE2412B0C9760CC66
SHA-1: AACDB4BD3DCFE53862AAAA2FCCAF1AE2F86319A0

Thanks for all your effort.

just press Y and return when you get the message, should work like a charm.
(I did not check the crc, cause I suspect progui's source to be watermarked, but it should not be a problem with the diff patch)

*Edit*
I uploaded a new version, you don't even need to press Y and return anymore (Winmerge give me reversed diff file somehow...). Just run Patch proGUI.bat and there you go