Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
10486
Web Server - Ask For Help / Re: Strange PR 25 behavior
« on: December 23, 2008, 09:28:18 PM »
Hi John,
Perhaps it's just a case of the bad install. Try deleting the netweb.inc and netweb.clw and netweb.tpw from the clarion6\libsrc and \clarion6\3rdparty\libsrc folders, and re-installing.
Regarding the header - for the "page header" procedure the idea is to tick the "this is a header" option ON.
Keep us posted on your progress regarding the \> error.
Cheers
Bruce
Perhaps it's just a case of the bad install. Try deleting the netweb.inc and netweb.clw and netweb.tpw from the clarion6\libsrc and \clarion6\3rdparty\libsrc folders, and re-installing.
Regarding the header - for the "page header" procedure the idea is to tick the "this is a header" option ON.
Keep us posted on your progress regarding the \> error.
Cheers
Bruce
10487
News And Views / Re: Version 4.31 PR 25 uploaded
« on: December 22, 2008, 08:08:26 PM »
more minor fixes.
http://www.capesoft.com/ftp/public/prerelease/index.htm
Thanks to all you guys who are reporting the various issues. I appreciate it.
The reports are getting fairly esoteric now, which is a good thing. So if you haven't updated then please do - I'd like to release this as 4.32 by the end of the week.
Cheers
Bruce
http://www.capesoft.com/ftp/public/prerelease/index.htm
Thanks to all you guys who are reporting the various issues. I appreciate it.
The reports are getting fairly esoteric now, which is a good thing. So if you haven't updated then please do - I'd like to release this as 4.32 by the end of the week.
Cheers
Bruce
10488
Web Server - Ask For Help / Re: 2 Browses. 1 Form. Doesn't work anymore.
« on: December 21, 2008, 10:06:53 PM »
Thanks Bryan,
sorted for today's build. (PR25)
Cheer
Bruce
sorted for today's build. (PR25)
Cheer
Bruce
10489
Web Server - Ask For Help / Re: Tooltip not displaying on Dropdown!
« on: December 21, 2008, 10:26:40 AM »
Hi Zoltan,
sorry mate - it's working for me in IE and FF. Can you duplicate the problem in an example, and maybe attach it here?
Anyone else having a problem?
Cheers
Bruce
sorry mate - it's working for me in IE and FF. Can you duplicate the problem in an example, and maybe attach it here?
Anyone else having a problem?
Cheers
Bruce
10490
Web Server - Ask For Help / Re: Content Disposition
« on: December 21, 2008, 10:21:45 AM »
Hi Alberto,
What you've done is the same as me. You've just replaced a variable with a constant string.
I copied your code to Example 40, and put it right under the line that's already there - and it worked perfectly. So I think perhaps your problem is a bit different.
Feel free to post your modified example 40 here if you like.
Cheers
Bruce
What you've done is the same as me. You've just replaced a variable with a constant string.
I copied your code to Example 40, and put it right under the line that's already there - and it worked perfectly. So I think perhaps your problem is a bit different.
Feel free to post your modified example 40 here if you like.
Cheers
Bruce
10491
Web Server - Ask For Help / Re: XHTML Tags Automatically Closed
« on: December 21, 2008, 10:18:17 AM »
Hi John / Adam,
In this example you are putting your header, and footer code inside the NetTalk web border extension.
This is already wrapping the header in 2 divs - if you browse to a page, and then right-click source, you'll see..
<div id="oPageHeaderTag2" class="headingouter">
<div id="iPageHeaderTag2" class="headinginner">
<div id="wrap">
<div id="header">
<h1>Example App Header</h1>
</div>
</div>
</div>
since your code contains an unmatched <div> there's gonna be a problem.
So I guess you should probably not use the "web border" extension, but rather move your html to the plain xHtml tab.
Cheers
Bruce
In this example you are putting your header, and footer code inside the NetTalk web border extension.
This is already wrapping the header in 2 divs - if you browse to a page, and then right-click source, you'll see..
<div id="oPageHeaderTag2" class="headingouter">
<div id="iPageHeaderTag2" class="headinginner">
<div id="wrap">
<div id="header">
<h1>Example App Header</h1>
</div>
</div>
</div>
since your code contains an unmatched <div> there's gonna be a problem.
So I guess you should probably not use the "web border" extension, but rather move your html to the plain xHtml tab.
Cheers
Bruce
10492
Web Server - Ask For Help / Re: XHTML Tags Automatically Closed
« on: December 18, 2008, 10:28:41 PM »
Hi Adam,
I appreciate the detailed info, but can't you rather just send me a small app example? It takes time to re-create an app from the description below, and there's no guarantee I'll do it exactly the way you did. If I then _don't_ get the same effect as you, then I'm left wondering if the bug is fixed, or I've done it differently...
Cheers
Bruce
I appreciate the detailed info, but can't you rather just send me a small app example? It takes time to re-create an app from the description below, and there's no guarantee I'll do it exactly the way you did. If I then _don't_ get the same effect as you, then I'm left wondering if the bug is fixed, or I've done it differently...
Cheers
Bruce
10493
Web Server - Ask For Help / Re: 2 Browses. 1 Form. Doesn't work anymore.
« on: December 17, 2008, 11:40:41 PM »
Hi Bryan,
I'll look into this.
I presume you're referring to a change button _under_ the browse. I would expect an "inline" change button probably works ok - and that might be the best work-around for you in the short term.
Cheers
Bruce
I'll look into this.
I presume you're referring to a change button _under_ the browse. I would expect an "inline" change button probably works ok - and that might be the best work-around for you in the short term.
Cheers
Bruce
10494
Web Server - Ask For Help / Re: XHTML Tags Automatically Closed
« on: December 17, 2008, 11:36:55 PM »
Hi Adam,
I think you'll need to post a small example, If you are adding your own open-div then it certainly wouldn't "automatically" close it for you.
Cheers
Bruce
I think you'll need to post a small example, If you are adding your own open-div then it certainly wouldn't "automatically" close it for you.
Cheers
Bruce
10495
Web Server - Ask For Help / Re: Running NetSimple in a Source module (Not a Window)
« on: December 16, 2008, 10:43:55 PM »
Hi Devan,
correct, you need the ACCEPT loop to listen for the incoming packets - and hence you need a Window structure.
But you can hide the window
window{prop:hide} = 1
immediately after the window opens.
In the ErrorTrap, and .Process (when done)
Post(event:closeWindow)
A good example of this approach is the "Send Email in a Process" example. Although the NetTalk object is on a window (the window that actually sends the email) that window is completely invisible to the user.
Cheers
Bruce
correct, you need the ACCEPT loop to listen for the incoming packets - and hence you need a Window structure.
But you can hide the window
window{prop:hide} = 1
immediately after the window opens.
In the ErrorTrap, and .Process (when done)
Post(event:closeWindow)
A good example of this approach is the "Send Email in a Process" example. Although the NetTalk object is on a window (the window that actually sends the email) that window is completely invisible to the user.
Cheers
Bruce
10496
Web Server - Ask For Help / Re: Force an user to use save or cancel.
« on: December 16, 2008, 10:39:19 PM »
Hi Wilco,
Ok, so let's accept for the moment that ghost records can be created. There's no way to prevent that (if the auto-inc is up-front). So then the solution is simply to have a periodic background process that scans the file and removes these records.
>> We are using the autoinc on the key. This causes that topspeed creates a record when hitting insert and when hitting save the record gets updated.
Well no, it's not Topspeed doing this - it's the Clarion template. NetTalk is a bit smarter than that.
However you don't necessarily _have_ to do the auto-inc up front. In fact the NetTalk WebServer Form does not do it up front unless it thinks it has to. (It typically has to if you have a child browse on the form.) So if your insert form is "simple" then the autoinc will only happen when the user clicks on save.
You can override the NetTalk "cleverness" using options on the advanced tab of the form template settings.
Cheers
Bruce
Ok, so let's accept for the moment that ghost records can be created. There's no way to prevent that (if the auto-inc is up-front). So then the solution is simply to have a periodic background process that scans the file and removes these records.
>> We are using the autoinc on the key. This causes that topspeed creates a record when hitting insert and when hitting save the record gets updated.
Well no, it's not Topspeed doing this - it's the Clarion template. NetTalk is a bit smarter than that.
However you don't necessarily _have_ to do the auto-inc up front. In fact the NetTalk WebServer Form does not do it up front unless it thinks it has to. (It typically has to if you have a child browse on the form.) So if your insert form is "simple" then the autoinc will only happen when the user clicks on save.
You can override the NetTalk "cleverness" using options on the advanced tab of the form template settings.
Cheers
Bruce
10497
News And Views / Re: Version 4.31 PR 24 uploaded
« on: December 16, 2008, 04:21:51 AM »
PR 24 is up. This is pretty much the gold release I think.
Includes some minor fixes, and a .Mobile property.
Bruce
Includes some minor fixes, and a .Mobile property.
Bruce
10498
Web Server - Ask For Help / Re: PR22: Drop lists stopped working
« on: December 15, 2008, 09:49:53 PM »
Hi Bryan,
work-around: On the Validation tab for the field, set "Validate Immediately" to "NO".
I've done this automatically for PR 24.
Cheers
Bruce
work-around: On the Validation tab for the field, set "Validate Immediately" to "NO".
I've done this automatically for PR 24.
Cheers
Bruce
10499
Web Server - Ask For Help / Re: Tooltip not displaying on Dropdown!
« on: December 15, 2008, 09:45:36 PM »
Hi Zoltan,
I've tested here with example 3, by putting a tooltip on the drop-down on the "AliasFormControl" procedure.
Unfortunately it seems to be working though. (At least for me.) So I thought it might be the "width" paramater which affects it, but no, it seems to work then as well.
So check out example 3, add a tip to the drop-down, and see what happens on your side. If it works there, then I guess I need an example from you where it's not working.
Cheers
Bruce
Ps - I'm testing with PR24, but nothing has changed with drop-downs for a while, so I don't think that's the issue.
I've tested here with example 3, by putting a tooltip on the drop-down on the "AliasFormControl" procedure.
Unfortunately it seems to be working though. (At least for me.) So I thought it might be the "width" paramater which affects it, but no, it seems to work then as well.
So check out example 3, add a tip to the drop-down, and see what happens on your side. If it works there, then I guess I need an example from you where it's not working.
Cheers
Bruce
Ps - I'm testing with PR24, but nothing has changed with drop-downs for a while, so I don't think that's the issue.
10500
Web Server - Ask For Help / Re: Force an user to use save or cancel.
« on: December 15, 2008, 09:28:41 PM »
Wilco,
As Kevin says, there's no real way to "force" them to press either button.
They could;
a) close the browser
b) just ignore the page (which at the very least would cause the session to timeout eventually)
c) type a different address in their Address bar of their browser
d) select something from their favorites list,
and so on.
So whatever you do, you'll never "force" them to press a button.
So instead of hiding menu items (which is possible) perhaps there's some other approach you can take. Tell us more about why it's so important for them to press Save or Cancel and perhaps we can offer some advice on another way to do it.
Cheers
Bruce
As Kevin says, there's no real way to "force" them to press either button.
They could;
a) close the browser
b) just ignore the page (which at the very least would cause the session to timeout eventually)
c) type a different address in their Address bar of their browser
d) select something from their favorites list,
and so on.
So whatever you do, you'll never "force" them to press a button.
So instead of hiding menu items (which is possible) perhaps there's some other approach you can take. Tell us more about why it's so important for them to press Save or Cancel and perhaps we can offer some advice on another way to do it.
Cheers
Bruce