1. Deluxe Slide Show Attn. Al
I have given up on trying to access a WinModem with Ubuntu. It's to difficult or
complicated. Unless someone has a how to?
So back to the Slide Show.
Three improvements,
1.) Don't let the 2 windows open on start up (SSWindow--really the directory
window-- and the SettingsWindow).
2.) Make it so that that the mouse buttons do the same as the '<' '>' buttons
after RightClick to Slide Show is selected.
3.) Make RightClick to Slide Show accessable again after completing scrolling
thru Slide show with mouse (as explained in step 2). This is going to be tuff to
do.
Any ideas?
Don Cole
2. Re: Deluxe Slide Show Attn. Al
don cole wrote:
>
> I have given up on trying to access a WinModem with Ubuntu. It's to difficult
> or complicated. Unless someone has a how to?
>
> So back to the Slide Show.
>
> Three improvements,
>
> 1.) Don't let the 2 windows open on start up (SSWindow--really the directory
> window-- and the SettingsWindow).
>
> 2.) Make it so that that the mouse buttons do the same as the '<' '>' buttons
> after RightClick to Slide Show is selected.
>
> 3.) Make RightClick to Slide Show accessable again after completing scrolling
> thru Slide show with mouse (as explained in step 2). This is going to be tuff
> to do.
>
> Any ideas?
>
> Don Cole
Hi there Don,
On #1:
Did you find out how to create a window leaving out the WS_VISIBLE style?
Didnt i post something like that a little while back?
If not just let me know i'll look it up again. It's not hard really,
but it's easier if you already have an example.
On #2:
This shouldnt be too hard. Look for the place where the slide show
enable flag is located and see if you can detect that in an if/then
statement like:
(inside the event function where the mouse right click is handled)
if ssflag and not(SS_Done) then
call ss mouse handler
else
call regular mouse button handler
end if
return 0
end function
On #3:
Im not clear on what you mean here. Do you mean you want to somehow
make the mouse buttons return to normal operation after the slide
show is done? If so, then when would you consider the slide show to be
done? Perhaps set a flag when done and use in above event?
Does all this sound ok to you?
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
From "Black Knight":
"I can live with losing the good fight,
but i can not live without fighting it".
"Well on second thought, maybe not."
3. Re: Deluxe Slide Show Attn. Al
Hello Al,
Al Getz wrote:
>
> don cole wrote:
> >
> > I have given up on trying to access a WinModem with Ubuntu. It's to
> > difficult
> > or complicated. Unless someone has a how to?
> >
> > So back to the Slide Show.
> >
> > Three improvements,
> >
> > 1.) Don't let the 2 windows open on start up (SSWindow--really the directory
> > window-- and the SettingsWindow).
> >
> > 2.) Make it so that that the mouse buttons do the same as the '<' '>'
> > buttons
> > after RightClick to Slide Show is selected.
> >
> > 3.) Make RightClick to Slide Show accessable again after completing
> > scrolling
> > thru Slide show with mouse (as explained in step 2). This is going to be
> > tuff
> > to do.
> >
> > Any ideas?
> >
> > Don Cole
>
>
> Hi there Don,
>
> On #1:
> Did you find out how to create a window leaving out the WS_VISIBLE style?
No I never got it to work.
> Didnt i post something like that a little while back?
Yes you did but I tried it in style and styleEx and couldn't get I to work
either or both ways.
> If not just let me know i'll look it up again. It's not hard really,
> but it's easier if you already have an example.
>
> On #2:
> This shouldnt be too hard. Look for the place where the slide show
> enable flag is located and see if you can detect that in an if/then
> statement like:
>
> (inside the event function where the mouse right click is handled)
I was thinking about the same thing with a slideshow_sw veriable.
> if ssflag and not(SS_Done) then
> call ss mouse handler
> else
> call regular mouse button handler
> end if
> return 0
> end function
>
> On #3:
> Im not clear on what you mean here. Do you mean you want to somehow
> make the mouse buttons return to normal operation after the slide
> show is done? Yes.
> If so, then when would you consider the slide show to be done? That's a good
> question. I've been thinking about it . I you ha a three button mouse (I don't)
> you could switch back and forth with the middle button. If not maybe [F4]to
> change the mouse key usage. Is there a way to detect what kind of mouse one has.
> I have to look into the mouse commands and see what can be done.
I'll get back when I figure which way to go.
Perhaps set a flag when done and use in above event?
>
>
> Does all this sound ok to you?
>
>
> Al
>
>
> My bumper sticker: "I brake for LED's"
>
> From "Black Knight":
> "I can live with losing the good fight,
> but i can not live without fighting it".
> "Well on second thought, maybe not."
Don Cole
4. Re: Deluxe Slide Show Attn. Al
Hello Al,
Correction I should have said MouseWheel rather than third mouse button.
getWheelScrollLines() perhaps?
Don Cole
5. Re: Deluxe Slide Show Attn. Al
don cole wrote:
>
> Hello Al,
>
> Al Getz wrote:
> >
> > don cole wrote:
> > >
> > > I have given up on trying to access a WinModem with Ubuntu. It's to
> > > difficult
> > > or complicated. Unless someone has a how to?
> > >
> > > So back to the Slide Show.
> > >
> > > Three improvements,
> > >
> > > 1.) Don't let the 2 windows open on start up (SSWindow--really the
> > > directory
> > > window-- and the SettingsWindow).
> > >
> > > 2.) Make it so that that the mouse buttons do the same as the '<' '>'
> > > buttons
> > > after RightClick to Slide Show is selected.
> > >
> > > 3.) Make RightClick to Slide Show accessable again after completing
> > > scrolling
> > > thru Slide show with mouse (as explained in step 2). This is going to be
> > > tuff
> > > to do.
> > >
> > > Any ideas?
> > >
> > > Don Cole
> >
> >
> > Hi there Don,
> >
> > On #1:
> > Did you find out how to create a window leaving out the WS_VISIBLE style?
> No I never got it to work.
> > Didnt i post something like that a little while back?
> Yes you did but I tried it in style and styleEx and couldn't get I to work
> either or both ways.
> > If not just let me know i'll look it up again. It's not hard really,
> > but it's easier if you already have an example.
> >
> > On #2:
> > This shouldnt be too hard. Look for the place where the slide show
> > enable flag is located and see if you can detect that in an if/then
> > statement like:
> >
> > (inside the event function where the mouse right click is handled)
> I was thinking about the same thing with a slideshow_sw veriable.
> > if ssflag and not(SS_Done) then
> > call ss mouse handler
> > else
> > call regular mouse button handler
> > end if
> > return 0
> > end function
> >
> > On #3:
> > Im not clear on what you mean here. Do you mean you want to somehow
> > make the mouse buttons return to normal operation after the slide
> > show is done? Yes.
> > If so, then when would you consider the slide show to
> be done? That's a good question. I've been thinking about it . I you ha a
> three button
> mouse (I don't) you could switch back and forth with the middle button. If not
> maybe
> [F4]to change the mouse key usage. Is there a way to detect what kind of mouse
> one
> has. I have to look into the mouse commands and see what can be
> done.</font></i>
>
> I'll get back when I figure which way to go.
>
> Perhaps set a flag when done and use in above event?
> >
> >
> > Does all this sound ok to you?
> >
> >
> > Al
> >
> >
> > My bumper sticker: "I brake for LED's"
> >
> > From "Black Knight":
> > "I can live with losing the good fight,
> > but i can not live without fighting it".
> > "Well on second thought, maybe not."
>
>
> Don Cole
Hi Don,
Here's an example of creating a window without the visible style
from another program:
ButtonEditWindow=
EzWindow:Create(
0,--atom StyleFlagsEx,
WS_DLGFRAME,--atom StyleFlags,
#F09080,--atom BackColor,
"Button Edit",--sequence Caption,
40,--integer xpos,
40,--integer ypos,
600,--integer width,
400,--integer height,
parentid,--atom parentID,
0 ) --object events
The only thing different about this is the WS_DLGFRAME style.
Since there is no WS_VISIBLE style the window doesnt show up
until it's opened.
As a side note, the newest upload of WinClass includes a special
service class called "Drag Window Body", which includes (like
many other classes) a 'Create()' function that allows a window
to use the "drag window body service", which does all the work for
getting a window to be dragable with the mouse while the
positioning cursor shows for the user. The nice thing is this
service allows a window to be moved around by simply dragging the
window itself, without having to use the caption bar. This means
it works with windows with no caption bar too. You can still have
the window go full screen and still be able to move it around.
Of course it's easy to use too, by specifying the window id:
include DragWindowBody.ew as DragWindowBody
atom dwb
dwb=DragWindowBody:Create(window_id)
And the window who's window id is window_id can be dragged around
from anywhere within the window.
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
From "Black Knight":
"I can live with losing the good fight,
but i can not live without fighting it".
"Well on second thought, maybe not."
6. Re: Deluxe Slide Show Attn. Al
don cole wrote:
>
> Hello Al,
>
> Correction I should have said MouseWheel rather than third mouse button.
>
> getWheelScrollLines() perhaps?
>
> Don Cole
Not sure what you mean here Don. What did you want to do here?
BTW, perhaps just turning off the scroll control when you reach the
end of the directory would work...then just detect if the scroll is
on or off, in order to determine how to handle the mouse buttons.
Hey, maybe a double click could revert the mouse buttons back to
normal use? For this just declare a double click function and add
the event for the main window.
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
From "Black Knight":
"I can live with losing the good fight,
but i can not live without fighting it".
"Well on second thought, maybe not."
7. Re: Deluxe Slide Show Attn. Al
Hello Al,
--create a slide show window:this really the directory window
global constant SSWindow=
EzWindow:Create(
0, --atom styleFlagsEx
WS_DLGFRAME, --atom styleFlag--
#E9E9E9, --background color
"Slide Show Window", --caption
28, 32, --xpos, ypos
520, 268, --width, height
0,-- MainAppWindow, --parent ID
--this was my mistake it should have been:
MainAppWindow, --parent ID
0)
It still Blinks but you can hardly notice it.
Thanks Al, I’m still working it in my mind how to do the other part.
Don Cole
Don Cole
8. Re: Deluxe Slide Show Attn. Al
Al Getz wrote:
>
> don cole wrote:
> >
> > Hello Al,
> >
> > Correction I should have said MouseWheel rather than third mouse button.
> >
> > getWheelScrollLines() perhaps?
> >
> > Don Cole
>
>
> Not sure what you mean here Don. What did you want to do here?
I was thinking about determing what kind of mouse the user had.
But I changed my mind on that.
Don Cole
9. Re: Deluxe Slide Show Attn. Al
don cole wrote:
>
> Hello Al,
> }}}
<eucode>
> --create a slide show window:this really the directory window
> global constant SSWindow=
> EzWindow:Create(
> 0, --atom styleFlagsEx
> WS_DLGFRAME, --atom styleFlag--
> #E9E9E9, --background color
> "Slide Show Window", --caption
> 28, 32, --xpos, ypos
> 520, 268, --width, height
> 0,-- MainAppWindow, --parent ID
> --this was my mistake it should have been:
> MainAppWindow, --parent ID
> 0)
> </eucode>
{{{
> It still Blinks but you can hardly notice it.
>
> Thanks Al, I’m still working it in my mind how to do the other part.
>
> Don Cole
>
>
> Don Cole
Hi Don,
Ok, i found that you have to do the other sub windows too or they blink too.
Also, "Close(windowid)" has to be removed for every window.
Also, i found that WS_DLGFRAME style isnt the best choice after all
because there is no way to close the window once it opens.
Here's what worked (no blinking):
(note all three windows were changed)
constant SettingsWindow=EzWindow:Create(
WS_EX_CLIENTEDGE, --style Ex
OR({WS_OVERLAPPED,WS_SYSMENU}),--WS_DLGFRAME --style
#F0C0A0, --background color
"SettingsWindow", --caption
10, 10, --xpos, ypos
300, 200, --width, height
0,--MainAppWindow, --parent ID
0) --events (none yet)
--Close(SettingsWindow)
--create a slide show window:
global constant SSWindow=EzWindow:Create(
WS_EX_CLIENTEDGE, --style Ex
OR({WS_OVERLAPPED,WS_SYSMENU}), --style
#E9E9E9, --background color
"Slide Show Window", --caption
28, 32, --xpos, ypos
520, 268, --width, height
0,--MainAppWindow, --parent ID
0)
--Close(SSWindow)
--create a Help window:
global constant helpWindow=EzWindow:Create(
WS_EX_CLIENTEDGE, --style Ex
OR({WS_OVERLAPPED,WS_SYSMENU}), --style
#E9E9E9, --background color
"Keyboard Help", --caption
28, 32, --xpos, ypos
520, 300, --width, height
0,--MainAppWindow, --parent ID
0)
--Close(helpWindow)
Please also note that for all three of these windows "Close()" was
remmed out. Close() causes the window to blink quick even when it's
not visible so remming these out helps too.
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
From "Black Knight":
"I can live with losing the good fight,
but i can not live without fighting it".
"Well on second thought, maybe not."
10. Re: Deluxe Slide Show Attn. Al
Hello Al,
--create a settings window:
constant SettingsWindow=EzWindow:Create(
WS_EX_CLIENTEDGE, --style Ex
OR({WS_OVERLAPPED,WS_SYSMENU}), --style
#F0C0A0, --background color
"SettingsWindow", --caption
10, 10, --xpos, ypos
300, 200, --width, height
MainAppWindow, --parent ID
0) --events (none yet)
--- Close(SettingsWindow)
--create a slide show window:this really the directory window
global constant SSWindow =
EzWindow:Create(--a missnomer should be -- DIRECRORTY SELECT WINDOW
--
WS_EX_CLIENTEDGE, --style Ex
OR({WS_OVERLAPPED,WS_SYSMENU}), --style
#E9E9E9, --background color
"DIRECTORY SELECT", --caption
28, 32, --xpos, ypos
520, 268, --width, height
0, --parent ID
0)
--create a Help window:
global constant helpWindow=
EzWindow:Create(
WS_EX_CLIENTEDGE, --style Ex --styleFlag Ex
OR({WS_OVERLAPPED,WS_SYSMENU}), --style
#E9E9E9, --background color
"Keyboard Help", --caption
28, 32, --xpos, ypos
520, 300, --width, height
MainAppWindow, --parent ID
0)
-- Close(helpWindow
This is what I got now.
I don't see blinking anymore.
I'm thinking deleting the SettingsWindow Because it's
not needed anymore.
WS_EX_CLIENTEDGE, --style Ex --styleFlag Ex
OR({WS_OVERLAPPED,WS_SYSMENU}), --style
What does OR mean here ?
Don Cole
11. Re: Deluxe Slide Show Attn. Al
don cole wrote:
>
> Hello Al,
>
>
> }}}
<eucode>
>
> --create a settings window:
> constant SettingsWindow=EzWindow:Create(
> WS_EX_CLIENTEDGE, --style Ex
> OR({WS_OVERLAPPED,WS_SYSMENU}), --style
> #F0C0A0, --background color
> "SettingsWindow", --caption
> 10, 10, --xpos, ypos
> 300, 200, --width, height
> MainAppWindow, --parent ID
> 0) --events (none yet)
> --- Close(SettingsWindow)
>
>
> --create a slide show window:this really the directory window
> global constant SSWindow =
> EzWindow:Create(--a missnomer should be -- DIRECRORTY SELECT WINDOW
> --
> WS_EX_CLIENTEDGE, --style Ex
> OR({WS_OVERLAPPED,WS_SYSMENU}), --style
> #E9E9E9, --background color
> "DIRECTORY SELECT", --caption
> 28, 32, --xpos, ypos
> 520, 268, --width, height
> 0, --parent ID
> 0)
>
> --create a Help window:
> global constant helpWindow=
> EzWindow:Create(
> WS_EX_CLIENTEDGE, --style Ex --styleFlag Ex
> OR({WS_OVERLAPPED,WS_SYSMENU}), --style
> #E9E9E9, --background color
> "Keyboard Help", --caption
> 28, 32, --xpos, ypos
> 520, 300, --width, height
> MainAppWindow, --parent ID
> 0)
> -- Close(helpWindow
> </eucode>
{{{
> This is what I got now.
> I don't see blinking anymore.
> I'm thinking deleting the SettingsWindow Because it's
> not needed anymore.
>
>
> WS_EX_CLIENTEDGE, --style Ex --styleFlag Ex
> OR({WS_OVERLAPPED,WS_SYSMENU}), --style
>
> What does OR mean here ?
>
> Don Cole
Hi Don,
Oh i guess it's working then.
'OR' means to logically 'or' all of the flags together:
x=OR({1,2,4})
--now x would equal (1 or 2 or 4) which comes out to 7.
This is almost the same as adding them:
x=1+2+4
except if one flag contains the same bits as another flag adding wont
work, while OR() will still work ok. That's why OR is better.
BTW, 'OR' is the same as 'or_all' in WinLib, if it's still called that :)
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
From "Black Knight":
"I can live with losing the good fight,
but i can not live without fighting it".
"Well on second thought, maybe not."
12. Re: Deluxe Slide Show Attn. Al
- Posted by don cole <doncole at pacbell.net>
Mar 24, 2006
-
Last edited Mar 25, 2006
Al Getz wrote:
>
> 'OR' means to logically 'or' all of the flags together:
> x=OR({1,2,4})
> --now x would equal (1 or 2 or 4) which comes out to 7.
>
> This is almost the same as adding them:
> x=1+2+4
> except if one flag contains the same bits as another flag adding wont
> work, while OR() will still work ok. That's why OR is better.
>
> BTW, 'OR' is the same as 'or_all' in WinLib, if it's still called that :)
>
>
> Al
>
O.k. in this case we are telling the window which style to be.
So your saying it could be WS_OVERLAPPED, OR WS_SYSMENU, we don't care
which? That doesn't make much sense. Why not just one or the other?
Don Cole
13. Re: Deluxe Slide Show Attn. Al
- Posted by Jason Gade <jaygade at yahoo.com>
Mar 24, 2006
-
Last edited Mar 25, 2006
don cole wrote:
>
> Al Getz wrote:
>
> >
> > 'OR' means to logically 'or' all of the flags together:
> > x=OR({1,2,4})
> > --now x would equal (1 or 2 or 4) which comes out to 7.
> >
> > This is almost the same as adding them:
> > x=1+2+4
> > except if one flag contains the same bits as another flag adding wont
> > work, while OR() will still work ok. That's why OR is better.
> >
> > BTW, 'OR' is the same as 'or_all' in WinLib, if it's still called that :)
> >
> >
> > Al
> >
>
> O.k. in this case we are telling the window which style to be.
>
> So your saying it could be WS_OVERLAPPED, OR WS_SYSMENU, we don't care
>
> which? That doesn't make much sense. Why not just one or the other?
>
>
> Don Cole
No, it's a bitwise OR.
Say you have the following two binary numbers:
1001
1011
You OR them together and you get
1011
Because in the second place from the right, 1 OR 0 = 1. It's a way of setting
bits in a number.
Using AND usually masks off bits:
1001 AND
1011
You get 1001.
See Wikipedia: http://en.wikipedia.org/wiki/Bitwise_OR
--
"Any programming problem can be solved by adding a level of indirection."
--anonymous
"Any performance problem can be solved by removing a level of indirection."
--M. Haertel
"Premature optimization is the root of all evil in programming."
--C.A.R. Hoare
j.
14. Re: Deluxe Slide Show Attn. Al
<SNIP>
Is it just me, or does anyone else just wish Don & Al actually knew
each other's e-mail address?
I really am sorry to ask this, but this topic just really has gone on
too long, too far, at least for me. Don't get me wrong, new releases
should be announced, and "I don't know", "Neither do I" /should/ be
quickly followed by EUForum posts. But, please, learn when a quiet
1-to-1 is appropriate.
No offense intended,
Pete
15. Re: Deluxe Slide Show Attn. Al
Pete Lomax wrote:
> <SNIP>
> Is it just me, or does anyone else just wish Don & Al actually knew
> each other's e-mail address?
>
> I really am sorry to ask this, but this topic just really has gone on
> too long, too far, at least for me. Don't get me wrong, new releases
> should be announced, and "I don't know", "Neither do I" /should/ be
> quickly followed by EUForum posts. But, please, learn when a quiet
> 1-to-1 is appropriate.
>
> No offense intended,
> Pete
*LOL*
I think it was the day before yesterday, when I thought: "I'm curious
whether the discussion about 'Deluxe Slide Show Attn. Al' will ever
come to an end." 
And when your post, Pete, arrived on my PC, i.e. a message with this
subject, but the sender was neither Don nor Al, I was so surprised, that
I had to look at the monitor three times, until I could believe it.
( Jason's recent message arrived later here. )
So I think I'm understanding you. However, for me personally it doesn't
matter.
Regards,
Juergen
--
Have you read a good program lately?
16. Re: Deluxe Slide Show Attn. Al
Juergen Luethje wrote:
>
> Pete Lomax wrote:
>
> > <SNIP>
> > Is it just me, or does anyone else just wish Don & Al actually knew
> > each other's e-mail address?
> >
> > I really am sorry to ask this, but this topic just really has gone on
> > too long, too far, at least for me. Don't get me wrong, new releases
> > should be announced, and "I don't know", "Neither do I" /should/ be
> > quickly followed by EUForum posts. But, please, learn when a quiet
> > 1-to-1 is appropriate.
> >
> > No offense intended,
> > Pete
>
> *LOL*
> I think it was the day before yesterday, when I thought: "I'm curious
> whether the discussion about 'Deluxe Slide Show Attn. Al' will ever
> come to an end."
> And when your post, Pete, arrived on my PC, i.e. a message with this
> subject, but the sender was neither Don nor Al, I was so surprised, that
> I had to look at the monitor three times, until I could believe it.
> ( Jason's recent message arrived later here. )
> So I think I'm understanding you. However, for me personally it doesn't
> matter.
>
> Regards,
> Juergen
>
> --
> Have you read a good program lately?
Hee hee
Once in a while we talk about the viewer, but geeze, it's not
that much! Once we settle some small problems it's done.
Nobody minds talking about 'their' project, so i say let Don
say what he wants too. How often has WinLib been brought up
on here? And Edita? See, everyone talks about their projects
and i think it's good to do that when that project is universal.
Perhaps Pete is planning his own viewer he he he.
Not only that, but the chat had turned to what logical or'ing is,
which is very universal and of general interest.
If we stop talking about 'everything', this forum will go bye bye.
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
From "Black Knight":
"I can live with losing the good fight,
but i can not live without fighting it".
"Well on second thought, maybe not."
17. Re: Deluxe Slide Show Attn. Al
Al Getz wrote:
> Juergen Luethje wrote:
>>
>> Pete Lomax wrote:
>>
>>> <SNIP>
>>> Is it just me, or does anyone else just wish Don & Al actually knew
>>> each other's e-mail address?
>>>
>>> I really am sorry to ask this, but this topic just really has gone on
>>> too long, too far, at least for me. Don't get me wrong, new releases
>>> should be announced, and "I don't know", "Neither do I" /should/ be
>>> quickly followed by EUForum posts. But, please, learn when a quiet
>>> 1-to-1 is appropriate.
>>>
>>> No offense intended,
>>> Pete
>>
>> *LOL*
>> I think it was the day before yesterday, when I thought: "I'm curious
>> whether the discussion about 'Deluxe Slide Show Attn. Al' will ever
>> come to an end."
>> And when your post, Pete, arrived on my PC, i.e. a message with this
>> subject, but the sender was neither Don nor Al, I was so surprised, that
>> I had to look at the monitor three times, until I could believe it.
>> ( Jason's recent message arrived later here. )
>> So I think I'm understanding you. However, for me personally it doesn't
>> matter.
>>
>> Regards,
>> Juergen
>
>
> Hee hee
>
> Once in a while we talk about the viewer, but geeze, it's not
> that much! Once we settle some small problems it's done.
> Nobody minds talking about 'their' project, so i say let Don
> say what he wants too. How often has WinLib been brought up
> on here? And Edita? See, everyone talks about their projects
> and i think it's good to do that when that project is universal.
> Perhaps Pete is planning his own viewer he he he.
> Not only that, but the chat had turned to what logical or'ing is,
> which is very universal and of general interest.
> If we stop talking about 'everything', this forum will go bye bye.
>
>
> Al
Hi Al,
I hope you didn't get me wrong. For me personally, everything is OK.
Regards, Juergen
