AutoHotkey Community

Notify() gives blank notify with the tekst Notify()
Notify("Test") gives notify with the tekst Test
Notify(QuickTekst) doesn't show
gui, add, text,,%QuickTest%
gui, Show
The above 2 lines show a blank window

_________________
Before asking a question try to read the manual
Always use the code sections when you paste some code

Then your variable isnt assigned to anything
Try
MsgBox, %QuickTekst%

When that works, Notify(QuickTekst) should

_________________
Notify() | Compile() | Instance() | LV_Group()
EitherMouse
Recommended: AHK_L (don't forget its a superset of _Basic)

hope you got that working...

quick update, I've finally tried the switch to AHK_L and this function appears to be working fine... i did have an extended ascii character in there so it needs to be saved as UTF-8 for unicode... but otherwise all seems well at first look

i've been putting this off as i have an application we use at the shop every day that i maintain and constantly add features too, so i couldn't risk breaking any functioning part (its a simple ERP system for tracking jobs)

i didn't have to change too much to get it to work with _L, so thats nice... and this function seems fine, good luck

if anyone is using _Basic and speaks up, I'll continue to support it... otherwise I'll probably break compatibility by taking advantage of the new (for me) features of _L (the obvious being the gui number)

_________________
Notify() | Compile() | Instance() | LV_Group()
EitherMouse
Recommended: AHK_L (don't forget its a superset of _Basic)

I suggest to not even use a Gui Name/Number at all, and instead use Gui, New. This way, even if the user is crazy enough to name their Gui "Notify_gwarble_4712389" (which is possible if the Gui's are dynamically created), it still won't "collide" with the Notify() function.

[documentation]

_________________
Autofire, AutoClick, Toggle, Spam • Window Control Tools
Recommended: AutoHotkey_L

Sweet, i havent really even started to explore the new features i can take advantage of in _L, but i guess i need to drop _Basic or have two versions

_________________
Notify() | Compile() | Instance() | LV_Group()
EitherMouse
Recommended: AHK_L (don't forget its a superset of _Basic)

@gwarble: this might be useful background info re gui new http://www.autohotkey.com/forum/topic81775.html

thanks for the info... so this is the clear first benefit to take advantage of, and although the poster there recommends not using it, in function form the hWnd can be used for all further reference i think so it seems the way to go

i'd like to not affect the LastFoundWindow, is there any changes in _L that will accomodate that?

also about an hour ago i started playing with GDIP (thanks tic), this is the preferred method with _L? it wasn't added natively or anything like COM was, right??

_________________
Notify() | Compile() | Instance() | LV_Group()
EitherMouse
Recommended: AHK_L (don't forget its a superset of _Basic)

Nope, GDI+ is not built-in so you will have to use tics' library.

yeah i thought so, kind of a tongue in cheek question... while i was a late adopter of AHK, i grew to love it instantly and was blown away by the possibilities... while i think major improvements are needed and being addressed by _L (and the only possibility with Chris' lack of support recently (no disrepect, he did an awesome thing while he could))

but...

i think its caused a lot of confusion to newcomers and medium-timers like me... breaking scripts, versions to download/differentiate... too many examples on this forum... and in my case i have a little application with thousands of lines of unoptomized code that i wrote while learning and learned by writing, that has little problems and rewrites throughout it and i won't be able to just compile in _L and distribute throughout my shop (a dozen or so computers) without some major testing...

blah, rant much... sorry but even reading the forums figuring out GDIP has brought up half the results about version this and deprecated that... seems like if we all can automate everything else we'd be able to automate ahk


anyway, i should obviously be in bed by now, but for the function, better to be dependant on GDIP? have two versions? forget GDIP? still support _Basic(gdip or not)? what do you think? then there's object syntax as a possibility as someone suggested...

i've got more to learn and lots of work to implement GDIP fully, but seems like the natural/proper way to do this kind of thing? (or is a custom control the "proper" way to do this kind of thing)

_________________
Notify() | Compile() | Instance() | LV_Group()
EitherMouse
Recommended: AHK_L (don't forget its a superset of _Basic)

My opinion: if you want to experiment with a GDI version fine, but keep Notify working out of the box so use Gui. You could (perhaps too much work) develop two versions one Gui (Notify.ahk) and using GDI (GNotify.ahk?), but I personally would stick with the Gui version, it does exactly what it says on the tin (and does it very well) and users don't have to use another library to make basic examples work when they want to try it (I don't have the gdi lib installed for example).

(re basic, _l, v2 there might be some changes to the website, forum to help overcome the issues you mention see http://www.autohotkey.com/forum/topic81753.html)

Thanks hugov, you gave me great feedback and help back when i was creating this function and was saddened to see your handle change to "So Long..."

I still also like the no dependancies rule, and could see conditional support if available and gui use if not, or a gdip version in parallel... Simple scripts could stay simple and complex apps could benefit from gdip if so desired... Otherwise CreateWindow (or RoundRect) windows features would be good to learn to prevent using two guis per notify


_L is a good "dependancy" in you opinion though? (thanks for that link, i hope major clarity/unification changes are made to preserve the future of A++ (what i think _L v1.2 should be called with full support for bad _b code and self management of unicode/ansi/32,64bit issues)

- gwarble

_________________
Notify() | Compile() | Instance() | LV_Group()
EitherMouse
Recommended: AHK_L (don't forget its a superset of _Basic)

I think GDI is a well-enough known library to allow for dependancy for it, and I also think making the transition to AHK_L won't hurt. I've said it before and I will say it again: AHK_L has no real disadvantages to AHK "Basic", and it is the de facto standard.

while i think you're right, its taking some work to switch... coming from someone who started with _Basic before _L was mainstream... script "bugs" most likely that were ignored before (like and h%emptyvar% in a gui show command, for example, or COM library use now thats its native) are now failing... no big deal in a small script but in a large application its just going to take time to fix things)

and for new users, things are not clear... either _B or _L installed will make a large portion of scripts on the forum not work in one case, and things like:

cause newcomers to still start with _Basic...

i'm all for the improvements _L yeilds, but i'm worried its coming at the expense of a disjoined community and difficulties for newcomers

_________________
Notify() | Compile() | Instance() | LV_Group()
EitherMouse
Recommended: AHK_L (don't forget its a superset of _Basic)

I wouldnt break compatibility.

I'd simply start a Notify v2, using whatever new features you wanted to add.

And that GDIP think looks really nice. Very simple, and aesthetically pleasing.

Yup i agree... If i ever go that route i'll make another version to take advantage of gdi+

It does look pretty slick and that was easy to implement with gdip()

One compatibility change i've been considering is swapping static_ and one-time options_... anyone opposed? since some dont have a static option it means you have to remember which are

_________________
Notify() | Compile() | Instance() | LV_Group()
EitherMouse
Recommended: AHK_L (don't forget its a superset of _Basic)