|
Thread Rules
1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution.
2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20)
3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible.
4. Use [code] tags to format code blocks. |
Zurich15366 Posts
On November 29 2012 01:24 AmericanUmlaut wrote:Show nested quote +On November 28 2012 22:38 zatic wrote:On November 22 2012 20:56 zatic wrote:
Thanks guys. "Change" should be enough, I won't need to keep entered but unfinished text elements before they change focus.
AmericanUmlaut: Yeah what I am afraid is that their UI uses tons of Javascript already and might do some of the changes to form elements programmatically. I'll know more when I am onsite. The change() thing wasn't really feasible because the form already had all sorts of event handlers on every element that interfered with what I was trying to do. I ended up extending the JS function that submits the form to include the timestamp I needed. + Show Spoiler +
var zsendSubmit = sendSubmit;
(function () {
sendSubmit = function () {
$("input[name='lastconfigchange']" .val($.now());
zsendSubmit();
}
})();
Reminded me how much fun coding is and how much fun Javascript is. Also how much unfun MSIE is  Yeah, when I teach my daughter to code, I'm going to tell her bedtime stories about IE6. I'm so glad I'm working on projects that don't have to support IE<9 any more. I'm curious why you wrapped the redefinition of sendSubmit in a self-executing anonymous function? As far as I can tell, there's no difference between doing that and just putting the same block of code into global namespace. You don't have any variables in there that will expire when the context created by the function dies. Did you intend to declare zsendSubmit inside the function?
That was what I did first, but then zsendSubmit ended up referencing the new sendSubmit and not the old one and the browser was stuck in endless recursion. It was a bit unsuspected for me as well, but at least the fix was easy enough.
|
I'm looking for a Java programmer who is familiar with Linked lists/network/threads. I prefer to contact him & share code via PM because my code will be checked for plagiarism later, and I don't want it to be found on any website.
My problem is specifically about adding a user to a linked list. The list is always empty, and I don't know how to fix it.
|
I was working with image animation in Javascript and ran into a problem.
I can't figure out what the logic would be for animating 9 images forward and then backwards.
function changePin()
{
if(curImage == 9)
{
curImage=0;
}
else
{
++curImage;
}
document.images[0].src = imageArray[curImage].src;
}
This is to go forward but it just resets @ 0 every time, and i need it to go from 9 to 8 to 7 ect. after going upwards.
Can someone help me with this please?
|
Hyrule19257 Posts
You first if is the reset. The simplest way to animate would be to have image 10 be image 8, image 11 be image 7, and so forth, and then reset at the final image.
|
cool thanks, that works out.
just another thing dealing with images, i want to display a smaller image of a pin and then a larger image of the pin.
i made a link under the image that i should be able to click on and changes the image.
function changeImage()
{
if(document.getElementByTag("img").src == "pin_small.jpg")
{
document.getElementByTag("img").src = "pin_large.jpg";
}
else
{
document.getElementByTag("img").src = "pin_small.jpg";
}
}
It's not changing the image however and im not sure as to what is wrong.
HTML:
<img src="pin_small.jpg" id="pinImage" alt="Pin Picture" height="69" width="105" /><br />
<a href="" id="changeImage" onclick="changeImage();return false;">View larger image</a>
?
|
On November 29 2012 06:46 zatic wrote:Show nested quote +On November 29 2012 01:24 AmericanUmlaut wrote:On November 28 2012 22:38 zatic wrote:On November 22 2012 20:56 zatic wrote:
Thanks guys. "Change" should be enough, I won't need to keep entered but unfinished text elements before they change focus.
AmericanUmlaut: Yeah what I am afraid is that their UI uses tons of Javascript already and might do some of the changes to form elements programmatically. I'll know more when I am onsite. The change() thing wasn't really feasible because the form already had all sorts of event handlers on every element that interfered with what I was trying to do. I ended up extending the JS function that submits the form to include the timestamp I needed. + Show Spoiler +
var zsendSubmit = sendSubmit;
(function () {
sendSubmit = function () {
$("input[name='lastconfigchange']").val($.now());
zsendSubmit();
}
})();
Reminded me how much fun coding is and how much fun Javascript is. Also how much unfun MSIE is Yeah, when I teach my daughter to code, I'm going to tell her bedtime stories about IE6. I'm so glad I'm working on projects that don't have to support IE<9 any more. I'm curious why you wrapped the redefinition of sendSubmit in a self-executing anonymous function? As far as I can tell, there's no difference between doing that and just putting the same block of code into global namespace. You don't have any variables in there that will expire when the context created by the function dies. Did you intend to declare zsendSubmit inside the function? That was what I did first, but then zsendSubmit ended up referencing the new sendSubmit and not the old one and the browser was stuck in endless recursion. It was a bit unsuspected for me as well, but at least the fix was easy enough.
There's gotta be something else going on there then, that's weird :O Also, I'd recommend you be explicit about using a global there, IE:
window.sendSubmit = function() {
...
}
If you aren't then your code will cause linter warnings (and if you don't use JSHint on your stuff already, you should!). It also makes it more clear that you're expecting the variable to be declared somewhere else and not just forgetting a var.
|
I agree with tec about the window.myVar notation. I learned embarassingly late about the difference between globally and locally scoped variable declarations in Javascript, but now I really find it much better to explicity say "I want this to be global" so that no one has to wonder. What I find even better, though, is just declaring a global namespace object and then making all of my "global" values and functions properties of that object. It prevents weird collisions that can be hard to debug, and if you have a good editor, it gives you a nicely organized structure for code completion.
@zatic: I'm thinking about what might be going on with your function. I've debugged through some mocked-up versions of your code (I usually do some brain teaser I find on stackoverflow to get warmed up, but this works, too  ) and I can't see any difference at all between the behavior of the reassignment with or without the wrapper function. Either way, I get recursion if the code runs twice, and not if it only runs once. Is the place where the function is defined getting run multiple times? Then you can do something like this to guarantee that you only run the block once:
if(!window.zsendSubmit) {
window.zsendSubmit = sendSubmit;
sendSubmit = function () {
$("input[name='lastconfigchange']").val($.now());
zsendSubmit();
}
}
If that's not the problem, then I'm utterly perplexed and very curious to hear more if you learn more about what's going on there.
|
On November 29 2012 12:26 RMonkeyF wrote:
function changeImage()
{
if(document.getElementByTag("img").src == "pin_small.jpg")
{
document.getElementByTag("img").src = "pin_large.jpg";
}
else
{
document.getElementByTag("img").src = "pin_small.jpg";
}
}
First, use code tags! They make everything better!
This is the sort of problem that you should be able to debug very easily without any help:
function changeImage()
{
//This is better stylistically: Don't navigate your DOM over and over again getting the same element
var elem = document.getElementByTag("img");
var src = elem.src;
/* debug */
alert(src);
/* end debug */
if(src == "pin_small.jpg")
{
elem.src = "pin_large.jpg";
}
else
{
elem.src = "pin_small.jpg";
}
}
What's in your alert output? It should be a full URL (at least it is in FireFox), so it's not going to exactly match the string you're comparing it to. A simple solution would be to use the indexOf() function, which returns -1 if it doesn't find the passed string in the calling string:
function changeImage()
{
var elem = document.getElementByTag("img");
elem.src = (elem.src.indexOf("pin_small.jpg") == -1 ? "pin_large.jpg" : "pin_small.jpg");
}
------
OOH OOH OOH! And I have such a clever idea for the animation problem that I just have to share it:
function changePin()
{
if(curImage == 9)
{
curImage = -8;
}
else
{
++curImage;
}
document.images[0].src = imageArray[Math.abs(curImage)].src;
}
Then you don't have to map any extra values to your array.
|
Zurich15366 Posts
Well I just did the same thing again and it worked here too. Did not on the customer system though.
Keep in mind it is all a big mess of JS and VBscript, I must not change any legacy code and pure IE7 was my only debugging tool. There is little point in over optimization.
|
Anyone know how to make Javascript control if a form should be sent or not without having to deal with the onClick attribute?
I have a input element within my form with the id attribute equal to btnSubmit and the type attribute equal to submit. When i click it i want a javascript to control that data have been entered as it should (in this case more then 0 letters). If one of the input elements isn't filled in i want it not to submit and if them all are filled in it will be submited.
this is the code i produced so far but i cant find a solution to achive what i want without adding a onClick attribute to my input sumbit button element.
I know how to control the element data it's just that i dont know how to stop the form from being sent.
function start(){
document.getElementById("btnSubmit").addEventListener("click", controlInput, false);
}
function controlInput(){
alert('I dont want to send the damn form :(');
}
window.addEventListener("load", start, false);
|
I think you probably want to use jQuery.submit(). (Or the equivalent native Javascript event, which is "submit").
$('#myForm').submit(function() {
return isValid();
});
or
document.getElementById("myForm").addEventHandler("submit", function(){...});
Returning FALSE blocks the form from being submitted in the case of the jQuery version. I think you have to manually prevent the default behavior in the pure Javascript version, but I use pure Javascript to bind events pretty rarely, so I'm not entirely sure.
|
On November 29 2012 22:53 TheSwedishFan wrote:Anyone know how to make Javascript control if a form should be sent or not without having to deal with the onClick attribute? I have a input element within my form with the id attribute equal to btnSubmit and the type attribute equal to submit. When i click it i want a javascript to control that data have been entered as it should (in this case more then 0 letters). If one of the input elements isn't filled in i want it not to submit and if them all are filled in it will be submited. this is the code i produced so far but i cant find a solution to achive what i want without adding a onClick attribute to my input sumbit button element. I know how to control the element data it's just that i dont know how to stop the form from being sent. function start(){
document.getElementById("btnSubmit").addEventListener("click", controlInput, false);
}
function controlInput(){
alert('I dont want to send the damn form :(');
}
window.addEventListener("load", start, false);
Don't really understand what it is you're going for, but if the problem is that you can't send the form without using a click() event, remember that you can use document.forms["theForm"].submit();. Obviously, there's no way to get away from using a click() event if you need something to happen on a click event though.
|
Turns out id didn't work. Time for some experementing. I'll post again if i find a solution.
|
On November 29 2012 07:15 darkness wrote:
I'm looking for a Java programmer who is familiar with Linked lists/network/threads. I prefer to contact him & share code via PM because my code will be checked for plagiarism later, and I don't want it to be found on any website.
My problem is specifically about adding a user to a linked list. The list is always empty, and I don't know how to fix it.
That's a pretty vague question. If you just need to add an entry to a linked list, it works the same way as any other list:
User user = blah;
List<User> list = Lists.newLinkedList();
list.add(user);
That's not exactly threadsafe though, can you describe in general terms what you're trying to do?
|
On November 29 2012 07:15 darkness wrote:
I'm looking for a Java programmer who is familiar with Linked lists/network/threads. I prefer to contact him & share code via PM because my code will be checked for plagiarism later, and I don't want it to be found on any website.
My problem is specifically about adding a user to a linked list. The list is always empty, and I don't know how to fix it.
Maybe you are screwing up variable scope?
|
On November 30 2012 06:10 fabiano wrote:Show nested quote +On November 29 2012 07:15 darkness wrote:
I'm looking for a Java programmer who is familiar with Linked lists/network/threads. I prefer to contact him & share code via PM because my code will be checked for plagiarism later, and I don't want it to be found on any website.
My problem is specifically about adding a user to a linked list. The list is always empty, and I don't know how to fix it. Maybe you are screwing up variable scope?
Fixed. Actually, my instance had to be 'static'. I guess the link list was recreated which shouldn't happen, so it was always null.
|
I'm sorry guys but this is kind of a homework problem and got stuck.
im not really good in Java but how do you fix this problem?
+ Show Spoiler +
the scanner totally skips the 'Enter Student Name' part and directly proceeds to the Enter Student Id.
Did I do something wrong?
the x = null; part is just a hunch coz i thought x wasn't initialized properly.
+ Show Spoiler +import java.util.Scanner;
public class Driver {
public static void main(String[] args) {
int choice, numberCourses, y;
String x;
Scanner input = new Scanner(System.in);
boolean loop = true;
while(loop == true){
System.out.println("Student Record Menu");
System.out.println("[1] New Record");
System.out.println("[2] Display Records");
System.out.println("[3] Quit");
choice = input.nextInt();
switch(choice) {
case 1:
System.out.println("New Record:");
Record record = new Record();
record.createStudent();
System.out.println("Enter Student Name:");
x = null;
x = input.nextLine();
record.setName(x);
System.out.println("Enter Student ID:");
x = input.nextLine();
record.setId(x);
System.out.println("Enter Course:");
x = input.nextLine();
record.setCourse(x);
System.out.println("Enter number of Subjects:");
numberCourses = input.nextInt();
for (int i = 1; i < numberCourses; i++) {
Course course = new Course();
System.out.println("For Subject " + i);
System.out.println("Enter Subject Code:");
x = input.nextLine();
course.setCode(x);
System.out.println("Enter Description:");
x = input.nextLine();
course.setDesc(x);
System.out.println("Enter Subject Units:");
y = input.nextInt();
course.setUnits(y);
System.out.println("Enter Grade:");
y = input.nextInt();
course.setGrade(y);
record.addCourse(course);
}
System.out.println("Done Adding...");
case 2:
case 3:
loop = false;
}
}
}
}
the entire Driver code.
|
I can't notice what causes your problem, but a piece of advice:
1. You can use while (boolean) instead of while (boolean == true). It does the same job, but I guess it's more readable in your case.
2. Always put break; after each case.
E.g.
case 1:
//some job
break;
case 2:
......
|
On November 30 2012 21:31 darkness wrote:I can't notice what causes your problem, but a piece of advice: 1. You can use while (boolean) instead of while (boolean == true). It does the same job, but I guess it's more readable in your case. 2. Always put break; after each case. E.g.
case 1:
//some job
break;
case 2:
......
yeah i already did that i just wanted to test the code in the middle of coding. I actually finished everything but i can't test it because of my problem =/
|
On November 30 2012 20:49 icystorage wrote:I'm sorry guys but this is kind of a homework problem and got stuck. im not really good in Java but how do you fix this problem? + Show Spoiler +the scanner totally skips the 'Enter Student Name' part and directly proceeds to the Enter Student Id. Did I do something wrong? the x = null; part is just a hunch coz i thought x wasn't initialized properly. + Show Spoiler +import java.util.Scanner;
public class Driver {
public static void main(String[] args) {
int choice, numberCourses, y;
String x;
Scanner input = new Scanner(System.in);
boolean loop = true;
while(loop == true){
System.out.println("Student Record Menu");
System.out.println("[1] New Record");
System.out.println("[2] Display Records");
System.out.println("[3] Quit");
choice = input.nextInt();
switch(choice) {
case 1:
System.out.println("New Record:");
Record record = new Record();
record.createStudent();
System.out.println("Enter Student Name:");
x = null;
x = input.nextLine();
record.setName(x);
System.out.println("Enter Student ID:");
x = input.nextLine();
record.setId(x);
System.out.println("Enter Course:");
x = input.nextLine();
record.setCourse(x);
System.out.println("Enter number of Subjects:");
numberCourses = input.nextInt();
for (int i = 1; i < numberCourses; i++) {
Course course = new Course();
System.out.println("For Subject " + i);
System.out.println("Enter Subject Code:");
x = input.nextLine();
course.setCode(x);
System.out.println("Enter Description:");
x = input.nextLine();
course.setDesc(x);
System.out.println("Enter Subject Units:");
y = input.nextInt();
course.setUnits(y);
System.out.println("Enter Grade:");
y = input.nextInt();
course.setGrade(y);
record.addCourse(course);
}
System.out.println("Done Adding...");
case 2:
case 3:
loop = false;
}
}
}
}
the entire Driver code.
A simple google search for "java nextLine skips" gave me the correct solution so i suggest next time you'll just try googling it first.
As opposed to what you might expect from a method called "nextLine", it doesn't return the whole line but only the part until the EOL characters (basically the enter key). You have to call another input.nextLine() after reading each line, i.e.:
System.out.println("Enter Subject Code:");
x = input.nextLine();
course.setCode(x);
input.nextLine(); // <-- don't need to store output
...
|
|
|
|
|
|
EPT![[image loading]](http://i.imgur.com/bHp4M.png)
